Coptic SCRIPTORIUM Wiki

administrative_interface

Anonymous (anonymous@undisclosed.example.com) — 2015-09-09T14:28:43+00:00

Web Application for URN Resolver and Repository: the Administrative Interface Logging In To access the administrative interface of the URN Resolver, navigate to the path /admin following the domain where the URN Resolver application is set up. For instance, if the URN Resolver application is set up at data.copticscriptorium.org, navigate to data.copticscriptorium.org/admin.

annotating_sub-word_morphemes

Anonymous (anonymous@undisclosed.example.com) — 2015-10-14T18:11:08+00:00

Create a morph layer There are multiple ways of creating a morph layer. Follow these steps if you have no morph layer at all Duplicate the norm layer. Name the new layer “ignore:morph”. Manually or using Google Refine identify the normalized words that need to be annotated on the morph level. (See the

annotation_layer_names

Anonymous (anonymous@undisclosed.example.com) — 2025-05-28T17:45:27+00:00

Annotation layer names for Coptic SCRIPTORIUM Data This document supercedes the Google doc used previously. (Note: in the layer names, @ and _ are interchangeable; @ gets converted to _ when the file is converted) tok tokens, smallest possible unit to be annotated; MAY BE SMALLER THAN THE MORPHEMES IN ORIG

basic_annotation_workflow

Anonymous (anonymous@undisclosed.example.com) — 2020-08-04T00:08:31+00:00

Basic Annotation Workflow Transcribe your text Transcribe your text in GitDox. Alternatively, transcribe your text into a text file. Be sure the transcription divides the text into bound groups At this point, you will want to use the Natural Language Processing (NLP) Service online. Veteran users will remember processing texts with individual NLP tools on a local machine and then editing the annotations in an Excel spreadsheet. The local process is outlined at the end of this page, but it is…

checklist_for_publishing_corpora

Anonymous (anonymous@undisclosed.example.com) — 2024-01-12T16:04:54+00:00

Checklist for Publishing and Releasing Corpora 1. New and revised docs should be reviewed by a Senior editor. * 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

corpus_metadata

Anonymous (anonymous@undisclosed.example.com) — 2017-06-09T03:55:35+00:00

Metadata at the corpus level includes the following fields. See our annotation layer name documentation for document-level metadata. annotation names of anyone involved in annotation of any kind (transcription, annotation, editing, etc.) for all texts in the corpus, separated by a comma and a space between the names

create_a_normalized_bound_group_layer

Anonymous (anonymous@undisclosed.example.com) — 2015-10-14T17:59:17+00:00

Using the Conditional Merge Macro to create new layers from existing data Create an original text layer A. Make your orig layer: first duplicate the tok layer and rename the new layer orig. B. Open the Conditional Merge macro; do NOT select any column. Using the top option, enter orig into the left box (Column with cells to merge>Column Header), and enter norm in the right box (Merge based on >Column Header). This will take the data in the orig column and make it the same span or size as in …

ensuring_orig_and_norm_layers_are_the_same_span

Anonymous (anonymous@undisclosed.example.com) — 2015-09-09T14:44:39+00:00

Ensuring orig and norm layers are the same span You now need to make the orig layer the same size (not separated by morphs but by words) as the norm layer. F. Save your file. G. Open the Conditional Merge Macro and using the top option, enter orig into the left box (Column with cells to merge>Column Header), and enter norm in the right box (Merge based on >Column Header). This will take the data in the orig column and make it the same span or size as in the norm column. It will use orig dat…

gitdox_workflow

Anonymous (anonymous@undisclosed.example.com) — 2020-08-03T23:49:16+00:00

GitDox is an online XML and spreadsheet editor which uses GitHub for data storage. It works best with Chrome or Firefox and is located at GitDox and GitHub GitDox uses GitHub for file storage and versioning. In order to use GitDox, you must first have a GitHub account. You can set up an account at

google_refine

Anonymous (anonymous@undisclosed.example.com) — 2015-09-09T14:51:26+00:00

Cleaning Data with Open Refine Download the latest stable version from Follow instructions to install. (May install as Google Refine.) Double click on the icon to open it; it will open a browser window. Although it opens in a browser window, you do not need to be online to use the app.

import_macro

Anonymous (anonymous@undisclosed.example.com) — 2016-02-17T21:56:45+00:00

Import into spreadsheet Install the Excel Add-in to import your tokenized file into an Excel spreadsheet. Install the add-in appropriate for your OS; the Mac (SGML_ io_Mac) and Windows add-ins differ significantly. To install select in Excel Tools > Add ins > [browse to the proper add in on your computer to enable]

language_of_origin_tagging

Anonymous (anonymous@undisclosed.example.com) — 2015-09-09T13:22:38+00:00

Language of origin tagger The language tagger annotates loan words for language of origin (Greek, Hebrew, Aramaic, Latin, etc.) The language of origin tagger tags on the morph level. (Note: In Coptic SCRIPTORIUM we create a layer specifically for tagging we usually name the ignore:morph layer. since our morph layer of annotations only contains those words annotated on this level and does not contain all the words that are not further annotated on this level.)

managing_ingests_and_corpora

Anonymous (anonymous@undisclosed.example.com) — 2015-09-09T14:29:33+00:00

Managing Ingests and Corpora Creating Ingests Creating a new Ingest will reingest all data from ANNIS, including Corpus Meta Items, Texts, Text Meta Items, HTML Visualizations, Search Fields, and Search Field Values. Due to the fact that the ingest process needs to execute Javascript to ingest

metadata

Anonymous (anonymous@undisclosed.example.com) — 2019-03-11T15:49:50+00:00

Metadata Metadata is information about your data; in this project metadata describes the document (“document metadata”) and the corpus (“corpus metadata”). Metadata is available in: * ANNIS: click on the “i” icon for corpus metadata; use the dropdown menu that appears for document metadata for each document

natural_language_processing_service_online

Anonymous (anonymous@undisclosed.example.com) — 2020-08-06T14:33:11+00:00

Natural Language Processing (NLP) Pipeline This page describes how to use the NLP tools on the public Coptic Scriptorium website. * Access the Natural Language Processing Service Online. * Copy the digitized text into NLP Service text box * Be sure “My data contains meaningful linebreaks

normalization

Anonymous (anonymous@undisclosed.example.com) — 2015-09-09T12:16:08+00:00

Normalization SCRIPTORIUM Tokenizer * Duplicate the “orig” column (the segmented morphemes and punctuation), copy it into a blank text file, and use the normalizing script to produce a normalized version of the text. Copy that into the spreadsheet. Save in the folder where the normalizer is located. Normalizer is titled auto_norm.pl.

onboarding_new_annotators_editors

Anonymous (anonymous@undisclosed.example.com) — 2023-05-31T22:02:19+00:00

Onboarding In general, onboarding new staff or volunteers who are editing/annotating in GitDox follows the following steps: GitHub and GitDox accounts * If they do not already have a GitHub account, ask them to set one up. If they are a new or existing user at GitHub, they will still need to provide us with their username, password, and email address, so instruct them to select a unique password

part_of_speech_tagging_using_tree-tagger

Anonymous (anonymous@undisclosed.example.com) — 2015-09-09T12:30:20+00:00

Part of speech tagging The norm layer will be tagged with the tree-tagger pos-tagger. (The morph layer will be tagged by the language of origin tagger.) To tag for part of speech, you will need the Tree-tagger package and our training courpus Select the norm column, copy it, paste it into a text file. Make sure the text file is using Unix returns and is in UTF-8. Save the new text file in whichever directory has the tree-tagger script (for Macs, the tree-tagger-MacOSX-3.2-intel/bin/ direct…

pelagios_rdf

Anonymous (anonymous@undisclosed.example.com) — 2018-09-25T17:44:50+00:00

Pelagios and Pleiades Linked Geographic Data Introductory Information Coptic Scriptorium's text data is linked to Pelagios and Pleiades via Pelagios' API. Using RDF, Pelagios links to a query for a term in our corpora (in ANNIS) that corresponds to the Pelagios entry.

processing

Anonymous (anonymous@undisclosed.example.com) — 2015-09-09T14:52:21+00:00

Procedure for processing a text for inclusion in our corpora: March 2015 Workshop Demo We are happy to help you with this process. Please contact a member of the SCRIPTORIUM team if you have a text you want to include in our corpora. Sometimes there are copyright or intellectual property issues with a text (especially if you are working from a published edition), and we can talk to you about the options in these cases.

start

Anonymous (anonymous@undisclosed.example.com) — 2025-01-09T17:30:34+00:00

Coptic SCRIPTORIUM Wiki Current Guidelines Annotation layer names See the Documentation Page on our main website for the following guidelines: * Quick Start Guide for editors and annotators * Transcription * Part of Speech Tagging * Lemmatization * Entity Annotations Treebanking guidelines Contributor/Annotator Tools and Processes

tokenizer

Anonymous (anonymous@undisclosed.example.com) — 2015-09-09T10:31:00+00:00

Tokenizer The Coptic SCRIPTORIUM tokenizer, tokenize_coptic.pl, is located at . Instructions for use, including parameters, are in the documentation (the README file) there. Tokenization guidelines are in sections 3 & 4 of the Transcription Guidelines at The default parameters of the tokenizer will break up Coptic bound groups separate…

transcribe_a_text

Anonymous (anonymous@undisclosed.example.com) — 2016-10-15T03:21:00+00:00

Transcribing a Text File Take a text file of Coptic keyed in the unicode Coptic characterset. (SCRIPTORIUM uses the Antinoou font and keyboard.) Save the file as a plain text file (.txt) encoded in UTF-8. (Most text editors have an option in Preferences for opening and saving texts in UTF-8.)

troubleshooting

Anonymous (anonymous@undisclosed.example.com) — 2015-09-09T14:30:01+00:00

Troubleshooting If there are errors with ingests, there are a few steps to take to research and resolve the issue. Troubleshooting questions for Ingests: 1. Are all Corpora configured with a correct annis_corpus_name to ingest data from ANNIS?

urn_resolver_database_administration

Anonymous (anonymous@undisclosed.example.com) — 2015-09-09T14:27:26+00:00

Informal documentation for the application installed at data.copticscriptorium.org. To ADD a Corpus: 1. Add HTML Visualization Formats if new ones are associated with the corpus. (May also create corpus, then add HVF, then go back to the corpus and edit it to select the new format(s).)

urn_resolver_web_application_administration_archimedes_documentation

Anonymous (anonymous@undisclosed.example.com) — 2015-09-09T14:28:23+00:00

Coptic Scriptorium URN Resolver Administrative Documentation Providing information about interactions with the administrative interface, basic site functionality, and troubleshooting helps. Application repository: Application deployed in production, 2015:

versification

Anonymous (anonymous@undisclosed.example.com) — 2020-08-03T23:48:39+00:00

Versification and Chapter Divisions [coming soon]