cu-mkp / gr8975 Goto Github PK
View Code? Open in Web Editor NEWRepository for "What is a Book in the 21st Century" GR8975, Spring 2017
Repository for "What is a Book in the 21st Century" GR8975, Spring 2017
Is it a problem to have multiple URLs in the "image_url" field? Separate by semicolon? Or separate into fresh columns?
one of my recipes calls for "gum or glue". Should both be listed as ingredients? Just one? Do we want to track the relationship between ingredients (in this case, that one can be substituted for the other)?
Some materials don't easily fit into either of these categories.
For instance, fol. 102r_2 ("For the furnace") calls for "turnipseed oil for the lamps to heat the furnace". Turnipseed oil isn't an ingredient per se, since it doesn't go into any final product. But calling oil a tool doesn't really make sense either.
Do we want to use
Example: the titles of the recipes have the spelling 'moulds' while the text of the recipes usually follow the spelling 'mold'. I am writing them down according to how it is spelled on Github. But may be we need to discuss spelling compatibility to fix these differences.
I could not find folio 161r on github, but it is there on the pdf English translation with the identifier p161r_1 and heading 'preparing sand for box molds' .
The main problem is the ingredients of the recipe. In the folios in Google Drive, the materials in the recipes just marked by the “m” code which I assume to be materials. The instruments in the recipe are not marked as the same. However, some marked materials seems ambiguous concerning its status in the recipes. They are not ingredients, and also can not count into instruments. For example the water for soaking (p074v_2), marble used to put materials on when burnishing (p075r_2, p078v_1,p078v_4), charcoal or manual or dung used for heating (p074r_3, p076r_1, p078r_3), paper or cards used when crushing (p077r_a4), wood or tooth used, for burnishing (p074v_3, p078v_1, p078v_2).
see google spreadsheet
quantities, tools, measurement terms; processes; etc
In the "folio_files" directory, I don't see a .txt file for folio 3v (should be "tl_p003v.txt"). This folio DOES exist in the Ms.
Please advise.
I can't find how to enable plain text in google sheets. According to HELP, I can add a ' as in '001 to keep it from reverting to 1. seems to work...
@VarshaMaragi I've added the translation txt files to the folio_files directory. Could you remove all the xml tags (i.e., anything matching the patter '<.+>') from the files?
The main problem is the ingredients of the recipe. In the folios in Google Drive, the materials in the recipes just marked by the “m” code which I assume to be materials. The instruments in the recipe are not marked as the same. However, some marked materials seems ambiguous concerning its status in the recipes. They are not ingredients, and also can not count into instruments. For example the water for soaking (p074v_2), marble used to put materials on when burnishing (p075r_2, p078v_1,p078v_4), charcoal or manual or dung used for heating (p074r_3, p076r_1, p078r_3), paper or cards used when crushing (p077r_a4), wood or tooth used, for burnishing (p074v_3, p078v_1, p078v_2).
Concerning the problem above, is it necessary to change the ingredients to materials, or add another category as instruments?
When it come to the recipes on mechanism (p080r_3), and preparing sand, earth, plaster for casting(p081r), it seem that the techniques and instruments are more important than “ingredients”. “Ingredient” in each of these recipes always just include one or two, while it need to be beaten by something, soaked by water, dried by some kind of fire. These should be more important information (though not perfect fit in to the category of “instrument”) in such kinds of recipes.
When the ingredients in the recipe mention an alternative, should we count it as one or two?
How specificity should the final products be describe, the titles of the recipes sometimes indicate the final products as yellow varnish, red gum, green wood, etc. Should we just categorize them as varnish, or should we make the final products as specific as possible?
The end products of some medical recipes is hard to describe, like the case in p077r_a1 (wearing a lead cap or mask), p079v_2 (take something in front when working with hazardous metals).
@jwayno is updating all syllabi in GD, but we need to then update the GitHub version. The master syllabus version is the GD student, so each week by the time of the lab, the GitHub version needs to be updated to reflect the changes in the GD master student file.
Jeffrey - no action is needed
Mehul - for you to do weekly
Let me know if this is confusing or needs clarification.
what do we mean by "read" in a digital environment?
The syllabus here is out of date: https://github.com/cu-mkp/GR8975/blob/master/README.md
We need to keep it up to date.
Compare existing solutions, also check Google StackDriver. Get back to Terry and Naomi.
Should we use:
Smith metadata sheet, fols. 1r-3r (shareable link):
https://drive.google.com/open?id=1GleRmCdEWOD7ZcfzhcE3wVRsXlC-AJoZSHqUWaASSB8
When listing ingredients in a recipe, how restrictive should I be?
One of my recipes includes:
folio files have format # tl_.txt# but some files are named #tl_.docx.txt#
does this need fixing?
Should we agree on a delimited list of generic-category words for "activity"?
What about the more specific descriptions? Should those also be from a finite (or controlled) list?
I need more permissions to edit GR8975 - change settings and add github pages.
in folio_images directory
I keep coming across ridiculously specific tools in my recipes (e.g., marble slabs, teeth for burnishing, etc.). These seem important to track
See also #50 : When it come to the recipes on mechanism (p080r_3), and preparing sand, earth, plaster for casting(p081r), it seem that the techniques and instruments are more important than “ingredients”. “Ingredient” in each of these recipes always just include one or two, while it need to be beaten by something, soaked by water, dried by some kind of fire. These should be more important information (though not perfect fit in to the category of “instrument”) in such kinds of recipes.
For many of the recipes in my folios, there don't appear to be any corresponding annotations. Do we just leave these fields blank on the metadata template?
If my recipe calls for "good chalk, quite white" and "half-burned saffron," are the ingredients "chalk" and "saffron" OR does "half-burned saffron" constitute a new ingredient? That is, when does an adjective (or other modifier) qualify an ingredient to such an extent that it should be an ingredient of its own?
This problem keeps coming up. Is "burnished silver" enough of its own thing, or is it just "silver"?
Did we decide not to include marginalia? So, where does all that data fit into the metadata sheet? It has no header, so it is not a recipe. It includes additional ingredients, but they are not necessarily integral to the recipe. Additionally, marginalia includes location on the page.
Add Alex's visit to student syllabus on markdown day
When the ingredients in the recipe mention an alternative, should we count it as one or two?
I have the following cases, which I think merit tracking:
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.