Git Product home page Git Product logo

gr8975's People

Contributors

atif93 avatar bnhiebert avatar caro27 avatar joshualijiayi avatar jwayno avatar ludotzp avatar modernalcibiades avatar nikhil-ramachandran avatar njr2128 avatar ps2270 avatar sohini-c avatar tcatapano avatar thuchacz avatar varshamaragi avatar xl2668 avatar zhaowenrui avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

gr8975's Issues

add field for ingredient?

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.

punctuation to separate fields with hierarchical values

Do we want to use

  1. Library of Congress standards (e.g., molding--crayfish)
  2. semicolon separated syntax (e.g., molding; molding crayfish) — and what of redundancy?
  3. separate fields (e.g., "Generic Activity: molding" ; "Specific Activity: crayfish")

spelling compatibility

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.

Is a folio missing on github?

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' .

what is an ingredient?

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).

no plain text in google sheets?

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...

Some questions concerning the metadata template

  1. 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).

  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.

  3. When the ingredients in the recipe mention an alternative, should we count it as one or two?

  4. 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?

  5. 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).

Update GitHub syllabus

@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.

Scope of metadata collection

When listing ingredients in a recipe, how restrictive should I be?
One of my recipes includes:

  1. a recipe for varnish with 2 ingredients, which I have included in my spreadsheet
  2. commentary on the effectiveness of that varnish compared to other varnishes. The main/defining ingredient in those 'rival' varnishes is listed. Should I include ingredients in the metadata spreadsheet that are not strictly used in the recipe itself?

Inconsistent file names

folio files have format # tl_.txt# but some files are named #tl_.docx.txt#
does this need fixing?

metadata: standardized header words?

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?

New metadata field suggestion: Tools

I keep coming across ridiculously specific tools in my recipes (e.g., marble slabs, teeth for burnishing, etc.). These seem important to track

Instruments as significant entity of interest

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.

Lacking annotations

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?

Difference between ingredients proper and qualified ingredients

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"?

Marginalia

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.

Alternative ingredients

When the ingredients in the recipe mention an alternative, should we count it as one or two?

Feature request: Relationship between distinct recipes, sub-recipes, double recipes

I have the following cases, which I think merit tracking:

  1. A recipe that includes a "sub-recipe" describing the process of making one of the ingredients of the "main recipe"
  2. A recipe that ends by referring to the next step, which is—in fact—the next recipe (so there is a relationship between the two: the second recipe relies on the first)
  3. A recipe that has a header indicating two types of product (in this case, glue) and then a recipe for each kind within the same "body text" of the recipe

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.