Coptic SCRIPTORIUM Wiki

User Tools

Site Tools

Trace:
annotation_layer_names

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
annotation_layer_names [2021/03/22 09:37] – NOT columns amirzeldesannotation_layer_names [2025/05/28 11:45] (current) – added facsimile_graphic_url admin
Line 16: Line 16:
 |lemma | lemma (dictionary head word); annotates on the normalized words ("norm" layer) | |lemma | lemma (dictionary head word); annotates on the normalized words ("norm" layer) |
 |note | notes that normally would go in a TEI XML <note note="xxx"> tag | |note | notes that normally would go in a TEI XML <note note="xxx"> tag |
-|hi@rend | text renderings (see http://www.copticscriptorium.org/download/tools/SCRIPTORIUMDiplTranscriptionGuidelines.pdf sections 4.2 & 5). Use spaces not commas between elements (e.g., red large not red, large); to render spaces, be sure to place underscores in the phrase (e.g., 1_space_right not 1 space right); validates to TEI XML only if there are five or fewer elements |+|hi@rend | usually appears as hi_rend in the column name in spreadsheet mode; for text renderings (see http://www.copticscriptorium.org/download/tools/SCRIPTORIUMDiplTranscriptionGuidelines.pdf sections 4.2 & 5). Use spaces not commas between elements (e.g., red large not red, large); to render spaces, be sure to place underscores in the phrase (e.g., 1_space_right not 1 space right); validates to TEI XML only if there are five or fewer elements |
 |gap | Annotates for lacunae. Corresponds to the EpiDoc TEI-XML element gap. Uses attributes such as @reason, @unit, @quantity, and @extent. With attributes, each element+attribute annotation generates a new layer in the multi-layer data model | |gap | Annotates for lacunae. Corresponds to the EpiDoc TEI-XML element gap. Uses attributes such as @reason, @unit, @quantity, and @extent. With attributes, each element+attribute annotation generates a new layer in the multi-layer data model |
 |supplied | Annotates for supplied text where text is missing from the original for a variety of reasons. Corresponds to the EpiDoc TEI-XML element supplied. Uses attributes such as @evidence and @reason. With attributes, each element+attribute annotation generates a new layer in the multi-layer data model. | |supplied | Annotates for supplied text where text is missing from the original for a variety of reasons. Corresponds to the EpiDoc TEI-XML element supplied. Uses attributes such as @evidence and @reason. With attributes, each element+attribute annotation generates a new layer in the multi-layer data model. |
-|lb@n | line breaks -- numbered according to the original manuscript | +|lb@n | usually appears as lb_n in column header in spreadsheet mode; line breaks -- numbered according to the original manuscript | 
-|cb@n | column breaks -- numbered according to the original manuscript |+|cb@n | usually appears as cb_n in column header in spreadsheet mode; column breaks -- numbered according to the original manuscript |
 |pb_xml_id | Page numbers of original manuscript (not the current repository numbering); be sure column label does not include a colon (e.g. pb_xml_id not pb_xml:id); be sure page numbers do not include spaces (e.g. EG202 not EG 202) (TEI XML <pb xml:id="xxx">) | |pb_xml_id | Page numbers of original manuscript (not the current repository numbering); be sure column label does not include a colon (e.g. pb_xml_id not pb_xml:id); be sure page numbers do not include spaces (e.g. EG202 not EG 202) (TEI XML <pb xml:id="xxx">) |
 |ignore:note | notes that will NOT be imported into ANNIS or exported as TEI or PAULA XML; private notations from annotators/encoders/editors | |ignore:note | notes that will NOT be imported into ANNIS or exported as TEI or PAULA XML; private notations from annotators/encoders/editors |
Line 40: Line 40:
 |entity | one of the ten entity types (e.g. person, place) see [[https://github.com/CopticScriptorium/entity-tagging/raw/master/coptic_scriptorium_entity_guidelines.pdf|entity guidelines]]. Note that there can be multiple entity columns due to nested entities. These columns are typically not edited manually in the spreadsheet, but are added by the graphical entity editing interface in entities mode.| |entity | one of the ten entity types (e.g. person, place) see [[https://github.com/CopticScriptorium/entity-tagging/raw/master/coptic_scriptorium_entity_guidelines.pdf|entity guidelines]]. Note that there can be multiple entity columns due to nested entities. These columns are typically not edited manually in the spreadsheet, but are added by the graphical entity editing interface in entities mode.|
 |identity | this annotation stores linked entry identifiers for named entities; it is populated automatically during export by GitDox if named entities have been added using the entity annotation interface. Annotators do not need to manually add this column| |identity | this annotation stores linked entry identifiers for named entities; it is populated automatically during export by GitDox if named entities have been added using the entity annotation interface. Annotators do not need to manually add this column|
 +|arabic | Arabic translation. Spans should follow translation and verse layers |
  
 === NOT columns in the spreadsheet === === NOT columns in the spreadsheet ===
Line 53: Line 54:
 (Note: see also the [[corpus_metadata|corpus-level metadata]] documentation for adding metadata for the entire corpus.) (Note: see also the [[corpus_metadata|corpus-level metadata]] documentation for adding metadata for the entire corpus.)
  
-[[https://github.com/CopticScriptorium/misc-development/raw/master/metadata-checklist-Dec2019.pdf|Download a checklist of the following fields]]+[[https://github.com/CopticScriptorium/misc-development/raw/master/metadata-checklist-Dec2019.pdf|Download a checklist of the following fields]] (does not yet include arabic_translation and possibly other newer fields; the list below is the most accurate)
  
 |annotation | names of annotators (transcribers, editors, annotators) in comma delimited sequence |  |annotation | names of annotators (transcribers, editors, annotators) in comma delimited sequence | 
 +|arabic_translation | names of people who translated the text into Arabic in comma-delimited sequence |
 |attributed_author | optional. attributed author of a conceptual work who may or may not be the historical author | |attributed_author | optional. attributed author of a conceptual work who may or may not be the historical author |
 |author | author of the conceptual work |  |author | author of the conceptual work | 
Line 66: Line 68:
 |endnote        | contains a note about the document that will appear in the HTML visualizations at the bottom of the visualization; optional|   |endnote        | contains a note about the document that will appear in the HTML visualizations at the bottom of the visualization; optional|  
 |entities| describes whether entity annotation has been reviewed. Available values are automatic, checked, or gold; required|   |entities| describes whether entity annotation has been reviewed. Available values are automatic, checked, or gold; required|  
 +|facsimile_graphic_url | optional. url of manuscript images (if available) |
 |Greek_source | optional, information about the Greek version of the text if it exists (e.g., Greek Alphabetical or Systematic Apophthegmata Patrum) |  |Greek_source | optional, information about the Greek version of the text if it exists (e.g., Greek Alphabetical or Systematic Apophthegmata Patrum) | 
 |identities| describes whether named entity linking has been reviewed. Available values are automatic, checked, or gold; required|   |identities| describes whether named entity linking has been reviewed. Available values are automatic, checked, or gold; required|  
Line 78: Line 81:
 |note           | optional |   |note           | optional |  
 |objectType     | codex, papyrus, ostracon, etc; optional|   |objectType     | codex, papyrus, ostracon, etc; optional|  
 +|ocr         | used only for documents that are OCR'd from print editions; use gold/checked/automatic|
 |order       | contains a number that orders the documents in a list, with the preferred first document numbered 01. For this project, the list should begin by corresponding to the same order dictated by the next and previous metadata fields.  After this list of documents (which almost always contains only non-redundant documents—see the "redundant" metadatum above), the redundant parallel witness documents appear (if any).  These redundant parallel witnesses also should be numbered according to the order of the running text of the conceptual work(s), for ease of reading and search.; optional|    |order       | contains a number that orders the documents in a list, with the preferred first document numbered 01. For this project, the list should begin by corresponding to the same order dictated by the next and previous metadata fields.  After this list of documents (which almost always contains only non-redundant documents—see the "redundant" metadatum above), the redundant parallel witness documents appear (if any).  These redundant parallel witnesses also should be numbered according to the order of the running text of the conceptual work(s), for ease of reading and search.; optional|   
 |origDate       | prose about the date of the text object (e.g.Between 900 and 1200 C.E.); optional|   |origDate       | prose about the date of the text object (e.g.Between 900 and 1200 C.E.); optional|  
annotation_layer_names.1616427445.txt.gz · Last modified: 2021/03/22 09:37 by amirzeldes