checklist_for_publishing_corpora
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
checklist_for_publishing_corpora [2016/12/07 14:17] – admin | checklist_for_publishing_corpora [2024/01/12 09:04] (current) – admin | ||
---|---|---|---|
Line 10: | Line 10: | ||
===2. Add/correct metadata on new documents=== | ===2. Add/correct metadata on new documents=== | ||
* Confirm metadata all conforms to standards on [[annotation_layer_names|layer annotation documentation]]. | * Confirm metadata all conforms to standards on [[annotation_layer_names|layer annotation documentation]]. | ||
- | * Pay close attention to names of annotators, version number, and version date for documents. We now use the SAME version # and date on new documents as on corpus metadata. | + | * Pay close attention to names of annotators, version number, and version date for documents. We now use the SAME version # and date on new documents as on corpus metadata; this version # corresponds with our corpus release # on Github. |
===3. Check the Issues list for each corpus to be released (whether new or revised versions of documents) on GitHub.=== | ===3. Check the Issues list for each corpus to be released (whether new or revised versions of documents) on GitHub.=== | ||
Line 19: | Line 19: | ||
* Pay close attention to names of annotators, version number, and version date for documents. Versioning: | * Pay close attention to names of annotators, version number, and version date for documents. Versioning: | ||
We now use the SAME version # and date on revised documents as on corpora. | We now use the SAME version # and date on revised documents as on corpora. | ||
- | Note: an annotator may have made a minor change a while back and changed the version # and version date, even though the revised document has not yet been published. | + | Note: an annotator may have made a minor change a while back and changed the version # and version date, even though the revised document has not yet been published. |
===5. Add/correct the corpus metadata.=== | ===5. Add/correct the corpus metadata.=== | ||
+ | **Note: the information in this section describes the workflow before we migrated to Gitdox. This section needs to be updated.** | ||
Corpus metadata appears on the first document in a corpus. | Corpus metadata appears on the first document in a corpus. | ||
* Confirm metadata all conforms to standards on [[annotation_layer_names|layer annotation documentation]]. | * Confirm metadata all conforms to standards on [[annotation_layer_names|layer annotation documentation]]. | ||
* Pay close attention to names of annotators: | * Pay close attention to names of annotators: | ||
* Version date should be the date of re-release. | * Version date should be the date of re-release. | ||
- | * Version #: | + | * Version # corresponds to the version of the Github release: |
===6. Validate the file.=== | ===6. Validate the file.=== | ||
- | * Use the [[https:// | + | * Gitdox: Use the " |
+ | * Excel: | ||
- | ===7. Convert to relANNIS and publish on SCRIPTORIUM ANNIS server.=== | + | ===7. Convert to TEI and PAULA and relANNIS and publish on SCRIPTORIUM ANNIS server.=== |
Typically performed by AZ. | Typically performed by AZ. | ||
Line 46: | Line 48: | ||
* Re-convert to TEI XML after editing, check validation, update versioning; repeat as necessary. | * Re-convert to TEI XML after editing, check validation, update versioning; repeat as necessary. | ||
- | ===10. Convert to relANNIS and publish on ANNIS server === | + | ===10. Convert to PAULA & relANNIS and publish on ANNIS server === |
Typically performed by AZ. | Typically performed by AZ. | ||
- | ==+10. Convert to PAULA XML format.=== | + | ===11. Post TEI, relANNIS and PAULA files to GitHub public repository in their respective directories=== |
- | Typically performed by AZ. | + | |
- | + | ||
- | ===11. Post TEI, relANNIS and PAULA files to GitHub public repository in their respective directories==+ | + | |
E.g., https:// | E.g., https:// | ||
- | ===12. Create a new release of the GitHub corpora repository, posting information about the latest changes in the release.=== | + | ===12. Create new meta.json file for linked data applications (with PATHS) and post in corpora repository |
+ | |||
+ | ===13. Create a new release of the GitHub corpora repository, posting information about the latest changes in the release.=== | ||
At https:// | At https:// | ||
- | ===13. New ingest at data.copticscriptorium.org to account for new data.=== | + | ===14. Update the urn mapping file.=== |
+ | https:// | ||
+ | |||
+ | ===15. New ingest at data.copticscriptorium.org to account for new data.=== | ||
Create new corpora, visualizations, | Create new corpora, visualizations, | ||
+ | |||
+ |
checklist_for_publishing_corpora.1481145446.txt.gz · Last modified: 2016/12/07 14:17 by admin