LEMDO

LEMDO

Remediation and Documentation Project (Fall 2019)

Posted by on 11 Sep 2019 in Activity log, Tasks

Fall 2019 LEMDO Project Plan

Team: RAs at UVic (Ashley Howard, Kate LeBere, Chris Horne); RA at UNR (Sarah Johnson); Programmer (Joey Takeda); Director (Janelle Jenstad)

Project Title: Remediation and Documentation

Outcomes

  1. Some ISE editions will be fully remediated and available on LEMDO (by RAs).
  2. One DRE edition will be fully remediated and available on LEMDO (by JJ).
  3. One QME edition will be fully remediated and available on LEMDO so that we can resolve performance notes encoding and video embedding for the LEMDO platform (by JT). 

Objectives

  1. Clean up six editions.
  2. Clean up the metadata for all the files in those five editions.
  3. Get the digital surrogates for those five editions (and metadata for the digital surrogates) into UVic ContentDM.
  4. Republish those six editions on LEMDO.
  5. Finish the documentation for all the parts of the edition.

Deliverables

See Asana LEMDO-Tech space for details.

Tasks

See Asana LEMDO-Tech space for details.

Texts

  1. JJ does 1HW
  2. JT does FV
  3. AH does AYL
  4. CH does H5
  5. KLB does Oth
  6. SJ does TBA

Process

  1. We all remediate one or more OS texts. Pick a facsimile from the ones available, document the choice in the metadata, and make sure the Library adds each one to ContentDM.
  2. JJ and AH finish the documentation for OS texts.
  3. We all remediate one or more M texts.
  4. JJ and AH finish the documentation for M texts.
  5. We all remediate an annotation file.
  6. JJ, AH, and JT finish the documentation for annotations.
  7. We all remediate a collation file.
  8. JJ, AH, and JT finish the documentation for collations.
  9. We all remediate one or more critical paratext files (secondary). This task will entail cleaning up bibliographies and adding entries to BIBL1.
  10. JJ, AH, and JT finish the documentation for critical paratexts.
  11. We all remediate one or more supplementary texts (hybrid primary/secondary).
  12. JJ, AH, and JT finish the documentation for supplementary texts.

Necessary Information

Types and Origins of Texts to Be Remediated

  1. OS: Old-spelling transcriptions of primary texts (from IML or EEBO-TCP)
  2. M: Modern-spelling texts of primary texts (from IML)
  3. Critical paratexts (from xWiki or from the old ISE, QME, and DRE sites)
  4. Annotations (XML files written in an IML-XML hybrid)
  5. Collations (XML files written in an IML-XML hybrid)
  6. Supplementary materials (from xWiki or from the old ISE, QME, and DRE sites. These texts were treated as critical paratexts in the ISE Platform; LEMDO treats them as primary texts.)
  7. Title pages from QME (already in good TEI; need LEMDO teiHeader)

Remediation Processes

There are four ways in which we convert texts for LEMDO.

  1. IML to LEMDO TEI-XML: OS and M texts.

IML files are stored as .txt files.

JT and/or MH run multiple conversion/cleanup cycles to produce rough LEMDO TEI.

RAs clean up the TEI and check the accuracy of the transcription simultaneously.

  1. EEBO-TCP TEI-XML P5 texts to LEMDO TEI-XML: OS texts only.

We get EEBO-TCP files from GitHub. They are already encoded in TEI P5.

JT runs a conversion process that produces relatively good LEMDO TEI.

RAs clean up the TEI and check the accuracy of the transcription simultaneously.

xWiki custom HTML to LEMDO TEI: Secondary texts, About pages, Paratextual materials

RAs clean up the files, with varying amounts of copyediting and checking. Generally, the editor of the edition and/or the Anthology Lead will be involved with checking.

RAs encode the files using the LEMDO tagset for born-digital files.

RAs clean up the files, with varying amounts of copyediting and checking. Generally, the editor of the edition and/or the Anthology Lead will be involved with checking.

Some texts were programmatically converted. 

We might have to copy and paste the text into our own XML files. 

  1. XML to TEI-XML conversion: Annotations and Collations

These files are stored as .xml files. They are encoded in a boutique IML-XML language.

JT does a conversion that embeds pointers to these annotations and collations (about 60% successful with the best texts).

RAs check the pointers. 

RAs manually add pointers for annotations and collations that could not be resolved programmatically.

RAs clean up the encoding of the annotations/collations.

This entry was posted by Janelle Jenstad and filed under Activity log, Tasks.