Coptic SCRIPTORIUM Wiki

• Check questions from annotators in the document and/or pull request
• read through the document
• use Google Refine to see if errors in tokenization, pos-tagging, lang-tagging, morph annotation, and normalization pop out
• ensure sure layer names conform to standards (see layer annotation documentation).
• use the validation add-in (when available) to confirm normalized annotation spans cover the same spans as the original column spans, group layer spans are the same size, etc.

• Confirm metadata all conforms to standards on layer annotation documentation.
• Pay close attention to names of annotators, version number, and version date for documents. Typically a newly published document will have v. 1.0.0. If you wish to publish a document and use the visualizations to help correct and proofread, you may release as 0.1.0 (or a number lower than 1.0.0).

Each corpus may have a list of errors noticed by users or team members. (E.g., https://github.com/CopticScriptorium/ap-dev/issues/35). Make corrections, and note on the issues list that the corrections have been made.

• Confirm metadata all conforms to standards on layer annotation documentation.
• Pay close attention to names of annotators, version number, and version date for documents. Versioning: +1.0.0 for major change to data and/or structure (entirely new layer annotation, entirely new tokenization method applied, etc.); +0.1.0 for significant edits but still structurally compatible with previous versions; +.0.0.1 for minor edits, e.g. fixing reported errors in transcription or pos-tags). Note: an annotator may have made a minor change a while back and changed the version # and version date accordingly, even though the revised document has not yet been published. We do not republish a corpus every time we make a minor revision to one document. You may wish to check the document's version # against the number in ANNIS.

Corpus metadata appears on the first document in a corpus.

• Confirm metadata all conforms to standards on layer annotation documentation.
• Pay close attention to names of annotators: the names of all annotators of all documents in a corpus should be in the corpus metadata; if someone has edited one document, be sure that person's name appears in the corpus metadata.
• Version date should be the date of re-release.
• Version #: +1.0.0 for major change to data and/or structure (entirely new layer annotation, entirely new tokenization method applied, etc.); +0.1.0 for significant edits but still structurally compatible with previous versions; +.0.0.1 for minor edits, e.g. fixing reported errors in transcription or pos-tags).

• Use the validation Excel add-in with the correct schema for your document to validate your Excel file.

• Each document in the corpus will be converted to TEI XML using the converter program developed by Amir Zeldes. (AZ typically does this step.)
• Confirm that the document validates against the EpiDoc TEI schema. http://www.stoa.org/epidoc/schema/latest/tei-epidoc.rng (Edit if necessary if problems with validation.)

Typically performed by AZ.

E.g., https://github.com/CopticScriptorium/corpora/tree/master/AP/apophthegmata.patrum_PAULA for the PAULA XML files of the Apophthegmata Patrum (AP) corpus

At https://github.com/CopticScriptorium/corpora/releases, click “Draft New Release.” Give it a new version number (Typically + 0.0.1 for minor edits/bug fixes; +0.1.0 for new documents/corpora added or minor changes to metadata model, etc.; +1.0.0 for entirely new features, new data models, etc.). Describe the corpus and changes/ additions in the description.

Create new corpora, visualizations, etc., if necessary; see documentation in wiki for this application)