Coptic SCRIPTORIUM Wiki

User Tools

Site Tools

Trace:
basic_annotation_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
Last revisionBoth sides next revision
basic_annotation_workflow [2016/03/02 14:48] – adminbasic_annotation_workflow [2020/08/03 16:56] – admin
Line 1: Line 1:
 ==== Basic Annotation Workflow ==== ==== Basic Annotation Workflow ====
  
-[[transcribe_a_text|Text file]]+=== Transcribe your text === 
 + 
 +Transcribe your text in [[gitdox_workflow|GitDox]]. Alternatively, transcribe your text into a [[transcribe_a_text|text file]]. Be sure the transcription divides the text into bound groups
  
 At this point, you may follow one of two paths: At this point, you may follow one of two paths:
Line 11: Line 13:
 === NLP Service Online Workflow === === NLP Service Online Workflow ===
  
-Copy your transcribed text into [[https://corpling.uis.georgetown.edu/coptic-nlp/|NLP Service]].  This service provides SGML output of your text in a format that is tokenized, normalized, and tagged for part-of-speech, lemma, and language of origin+[[natural_language_processing_service_online|Run the NLP Service]] on your transcribed text in GitDox.   
 +  * If your text is in a text file, copy and paste it into the GitDox text editor. (See the [[gitdox_workflow|GitDox]] page for more information on using the GitDox text editor.) 
 +  * If your text is already transcribed into the GitDox text editor and validated (see [[gitdox_workflow|GitDox]]), you're ready for the NLP tools. 
 + 
 +You will see an NLP button below the text window. Click it. 
 + 
 +//Note for veteran GitDox users: you do not need to proofread tokenization as part of the NLP Service process. The NLP service works better, now, without tokenizing first.//
  
 [[import_macro|Import the SGML into a spreadsheet.]] [[import_macro|Import the SGML into a spreadsheet.]]
Line 17: Line 25:
 Rename the existing layers according to the [[annotation_layer_names|Annotation layer names guidelines]]. (Not all layers in the guidelines will exist in your file at this point.) Rename the existing layers according to the [[annotation_layer_names|Annotation layer names guidelines]]. (Not all layers in the guidelines will exist in your file at this point.)
  
-Proofread the tokenization of the bound groups.   +Remove any redundant columns. These may be hi (keep hi@rend); supplied (keep supplied@reason etc.); gap (keep gap@reason etc.).
-  * Add or delete rows if necessary to create additional tokens.  +
-  * You may wish to use [[Google Refine]] if working with a large file. +
-  * WARNING: Since the spreadsheet now contains many annotation layers, be careful when adding or deleting rows:   +
-      * Make sure that the spans of the tok, norm, and at least one of the group layers are all accurately aligned. +
-      * Make sure that any annotation layers (e.g., hi@rend, gap@, etc.) still annotate the correct token(s) +
-      * Make sure that the pos, lemma, and lang layers are accurately aligned+
  
-Note:  the following steps are a guide to the kinds of work you will be doing.  It is organized around the principle of editing one annotation layer at a time.  Some people who use the NLP pipeline to annotate everything at once then find it easier to correct all annotation layers for one row at the same time and to go through the file row by row.+Add missing information to existing layers. For instance, replace lb and cb placeholders in lb@n and cb@n columns with line and column numbers from original manuscript. 
 + 
 +Note:  the following steps are a guide to the kinds of work you will be doing.  It is organized around the principle of editing one annotation layer at a time.  When using the NLP pipeline to annotate everything at once, some editors, however, prefer to correct all annotation layers for one row at the same time and to go through the file row by row.
  
 [[create_a_normalized_bound_group_layer|Create an original text ("orig") layer]] (You may do this last; you may even find it easier to do this last.) [[create_a_normalized_bound_group_layer|Create an original text ("orig") layer]] (You may do this last; you may even find it easier to do this last.)
Line 37: Line 41:
 [[create_a_normalized_bound_group_layer|Reconstruct the norm_group layer]]. [[create_a_normalized_bound_group_layer|Reconstruct the norm_group layer]].
  
-Proofread the part of speech (pos) and lemma (lemma) layers. +Proofread the part of speech (pos), lemma (lemma), and morpheme (morph) layers. Part of speech and lemma are annotated on the norm level.
- +
-[[annotating_sub-word_morphemes|Annotate for sub-word morphemes and create a morph layer]].+
  
 Proofread the language of origin (lang) layer. Proofread the language of origin (lang) layer.
Line 45: Line 47:
   * Coptic SCRIPTORIUM annotates for language of origin on the **morph** level not the **word (norm)** level.  Be sure the language of origin tags align with the content and span in the morph layer rather than the norm layer.   * Coptic SCRIPTORIUM annotates for language of origin on the **morph** level not the **word (norm)** level.  Be sure the language of origin tags align with the content and span in the morph layer rather than the norm layer.
  
-Add [[Metadata]]+Add translation, paragraph, and other layers as necessary following the [[annotation_layer_names|annotation layer names guidelines]]. 
 + 
 +Add [[Metadata]].
  
 Validate the file using the [[https://github.com/CopticScriptorium/XLAddIns|validation Excel Add-in]]. Validate the file using the [[https://github.com/CopticScriptorium/XLAddIns|validation Excel Add-in]].
basic_annotation_workflow.txt · Last modified: 2020/08/03 18:08 by admin