Resources for Student Researchers at StMU 2017


Information Session, September 8, 2017


First Training Session, September 29, 2017

Understand a page of Ceriani's 1861 Critical Edition

  1. Antonio Maria Ceriani transcribed Latin Moses (Jubilees and the Testament of Moses) based on what he (thought he) could read in 1861.
  2. We want a proper TEI version of his edition to use as a base for creating a new edition based on advanced images.
  3. The 96 pages of Latin Moses appear on 48 pages of Ceriani's edition (two manuscript pages per edition page).
  4. Two edition pages have been started by TRH as examples. First understand one of the examples.
  5. Bring up the Ceriani's critical edition of the first page of Latin Moses
  6. Bring up the TEI encoding of this page (in progress)
  7. Compare the conventions used by Ceriani and the TEI equivalent.

Work on a page in need of TEI encoding

  1. Login to github (using the stmusr account, or your own, or create your own)
  2. Go back to the annotation development branch,
  3. Ask for and click on an XML file that no one else is working on
  4. Copy the content of the xml file to the clipboard (I suggest clicking "Raw" then Ctrl-A then Ctrl-C)
  5. Navigate to the Validator on (LINK) and paste from the clipboard to the top pane (Ctrl-V).
  6. The bottom pane will either be green for valid TEI XML (but otherwise unimportant) or have a red error message, which may or may not be helpful.
  7. Look for a code or comment to indicate the 5c or 19c page number of one of the manuscript pages on your page of Ceriani. Use the IIIF Navigator to find the appropriate page of Ceriani's edition (as we did above for the first page).

Interpret human conventions in scholarly edition (Ceriani) into TEI XML

  1. Rule one is to not destroy information.
  2. Give yourself credit in the TEI header in the <titleStmt> after the </title> as follows:
    <respStmt><resp>TEI Encoding</resp><name>Firstname Lastname</name></respStmt>
  3. Add <milestone/> tags similar to the ones on the example page:
  4. Add <p></p> paragraph code tags surrounding blocks that begin with a hanging indent.
  5. Add <lb/> line beginning tags at the beginning of a new line that is not also the beginning of a paragraph.
  6. The "don't destroy information" rule applies to information in the provided text that is not found in Ceriani. Rather than delete, enclose the additions with <add resp="#ocp"></add>, meaning the enclosed was added and the responsible party is known as ocp (for Online Critical Pseudepigrapha).
  7. When information is corrected rather than added the original (sic) and correction are enclosed in a choice tag: <choice><sic>e</sic><corr resp="#ocp">E</corr></choice>.
  8. When in doubt, leave a comment to future editors as follows <!-- comment -->

Commit changes in GitHub

  1. If you are not still logged into Github it is important to log in now.
  2. Go back to the Github page for the file you are working on. If the tab is not still open find it in
  3. Click the pencil icon that says "Edit this file" when you hover over it.
  4. Copy and paste from the validator into the edit window.
  5. Add a brief note such as your name and how far you got in the brief description window.
  6. The default option should be "Commit directly to the development branch."
  7. Do a quick common sense check and click "Commit changes."

Human resources paperwork

  1. Dr. Hanneken has Personnel Action Forms that require your name (as it appears on official University records) and Student ID Number. Complete and return to him for routing through administrative signatures.
  2. If you have never been paid through StMU payroll before (in any context) there is more paperwork for you in the Human Resources office on the bottom floor of Saint Louis Hall.
  3. Hours (including the information session, a form of training) are to be entered into Gateway. I honestly do not know how this works so Human Resources or your friends will be a better source of information.



Text Encoding Initiative
eXtensible Markup Language, cf. HyperText Markup Language
A markup enclosed in angle brackets that describes content.
The first word in a tag that defines what kind of tag it is. It can have attributes within the angle brackets. It can contain other elements or character strings, in which case it terminates with a forward-slash tag. If not, the tag ends with a forward slash.
Additional information about the element. It is typically followed by an equal sign and a string of characters in quotation marks.

October 13, 2017

Review fundamental principles of TEI hierarchical and non-hierarchical tags

Use HTML transforms to check earlier work

Encode more conventions used in Ceriani and OCP

Thoughts on not drowning in user interfaces

October 27, 2017

Background on IIIF Navigator

Study manuscripts in IIIF Navigator

Use and contribute to paleography charts

Understanding the IIIF Image API

November 10, 2017

This workshop was dedicated to collaborative work on encoding Ceriani in TEI XML. The notes prepared for the possibility of encoding Gryson's edition of the Arian Commentary on Luke were not used but are preserved below for possible future reference.

Interpret human conventions in scholarly edition (Gryson) into TEI XML

Additional scholarly conventions