User Tools

Site Tools


gitdox_workflow

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
gitdox_workflow [2018/04/20 23:20] – working on updates about GitDox eplattegitdox_workflow [2020/08/03 17:49] (current) – [Tips for working with the online spreadsheet] admin
Line 31: Line 31:
  
 ===== Transcribing ===== ===== Transcribing =====
-Follow our [[https://github.com/CopticScriptorium/tagger-part-of-speech/blob/master/scriptorium-transcription-guidelines.pdf|diplomatic transcription guidelines]]. Enter text in a unicode Coptic character set (SCRIPTORIUM uses the Antinoou font and keyboard.) Be sure there is a space between each Coptic bound group. You do not need to segment all the morphemes. We follow Layton's conventions for segmenting bound groups. For example ⲁϥⲟⲩⲱϣⲃ ⲛⲁϥ, not ⲁ ϥ ⲟⲩⲱϣⲃ ⲛⲁ ϥ, nor ⲁϥⲟⲩⲱϣⲃⲛⲁϥ.+Follow our [[https://github.com/CopticScriptorium/tagger-part-of-speech/blob/master/scriptorium-transcription-guidelines.pdf|diplomatic transcription guidelines]]. Enter text in a unicode Coptic character set (SCRIPTORIUM uses the Antinoou font and keyboard.) Be sure there is a space or an underscore between each Coptic bound group. You do not need to segment all the morphemes. We follow Layton's conventions for segmenting bound groups. For example ⲁϥⲟⲩⲱϣⲃ ⲛⲁϥ, not ⲁ ϥ ⲟⲩⲱϣⲃ ⲛⲁ ϥ, nor ⲁϥⲟⲩⲱϣⲃⲛⲁϥ. Carriage returns result in line breaks in transcribed texts, though the schema also allows line break tags.
  
 GitDox features syntax highlighting and suggestions. When you open an angle bracket, GitDox suggests tags that are currently available. GitDox will also suggest attributes for tags. Improperly closed tags and other errors are highlighted in red. GitDox features syntax highlighting and suggestions. When you open an angle bracket, GitDox suggests tags that are currently available. GitDox will also suggest attributes for tags. Improperly closed tags and other errors are highlighted in red.
  
-===== Adding metadata ===== +===== Validation ===== 
-Use the button at the bottom of the page to add metadata. A new window will open. You may select metadata fields from the drop-down menu by hovering the mouse over the meta key text box and clicking on the arrow. Note that this drop-down menu will not work in Safari. You can also begin to type the name the metadata you want to enter in the meta key text box, which will bring up a set of suggestionsEnter the value into the meta value text box.  +GitDox features validation for xml and spreadsheet modes as well as for metadata. Click the validate button on the upper right, and validation errors will appear in the text box belowFor errors where the cell or value does not match the patternhover over the text of the error message to get more information about the expected patternBe sure to validate the xml before processing your text using the NLP to avoid errors.
- +
-Please reference our [[annotation_layer_names#metadata|documentation on metadata fields]] when entering metadata in GitDox.   +
- +
-After you click submit, the metadata will appear in a chart on the bottom of the pageYou can't edit metadata you've already submitted, but you can delete the entry from the list and re-enter the correct field and information.+
  
 ===== Tokenizing ===== ===== Tokenizing =====
-Click the tokenize button under the transcription box to automatically tokenize your transcribed text. Correct the tokenization in GitDox.+If you wish to tokenize your text, you may click the tokenize button under the transcription box to automatically tokenize your transcribed text. You can then correct the tokenization in GitDox. Remember to commit your changes.
  
 +//Note to veteran GitDox users: As of 2020 you no longer need to check tokenization before running the rest of the NLP tools.  Run the whole tool suite together.//
 ===== Processing using the NLP ===== ===== Processing using the NLP =====
-After correcting the tokenization in the transcription editor of GitDox, click the NLP button under the transcription box to automatically process your text and send it to the spreadsheet editor.+After validating your text transcription in GitDox, click the NLP button under the transcription box to automatically process your text and send it to the spreadsheet editor.
  
 ===== Editing annotations in the online spreadsheet ===== ===== Editing annotations in the online spreadsheet =====
  
 Follow the steps in the [[basic_annotation_workflow|Basic Annotation Workflow]] starting at "Rename existing layers...." The online spreadsheet automatically saves all work.  Follow the steps in the [[basic_annotation_workflow|Basic Annotation Workflow]] starting at "Rename existing layers...." The online spreadsheet automatically saves all work. 
- 
-===== Tips for working with the online spreadsheet ===== 
- 
-In progress 
  
  
 +===== Adding metadata =====
 +Use the button at the bottom of the page to add metadata. A new window will open. You may select metadata fields from the drop-down menu by hovering the mouse over the meta key text box and clicking on the arrow. Note that this drop-down menu will not work in Safari. You can also begin to type the name the metadata you want to enter in the meta key text box, which will bring up a set of suggestions. Enter the value into the meta value text box. 
  
 +Please reference our [[annotation_layer_names#metadata|documentation on metadata fields]] when entering metadata in GitDox.  
  
 +After you click submit, the metadata will appear in a chart on the bottom of the page. You can't edit metadata you've already submitted, but you can delete the entry from the list and re-enter the correct field and information.
  
 +Corpus metadata can be added or edited in any document in the corpus; changes will affect all documents. See the [[corpus_metadata|corpus metadata]] page for information on fields and values.
gitdox_workflow.1524288034.txt.gz · Last modified: 2018/04/20 23:20 by eplatte