Edition Diagnostics Technical Writer Janelle Jenstad Technical Writer Navarra Houldin Proofreader Mahayla Galliford Project Director Janelle Jenstad Project Manager Mahayla Galliford Training and Documentation Lead Navarra Houldin Programmer Martin Holmes Programmer Joey Takeda Junior Programmer Tracey El Hajj Social Sciences and Humanities Research Council of Canada

Released with Linked Early Modern Drama Online 1.0

 University of Victoria on the Linked Early Modern Drama Online Platform

This file is licensed under a CC BY-NC_ND 4.0 license, which means that it is freely downloadable without permission under the following conditions: (1) credit must be given to the author and LEMDO in any subsequent use of the files and/or data; (2) the content cannot be adapted or repurposed (except in quotations for the purposes of academic review and citation); and (3) commercial uses are not permitted without the knowledge and consent of the editor and LEMDO. This license allows for pedagogical use of the documentation in the classroom.

Linked Early Modern Drama Online

TEI Customization created by Martin Holmes, Joey Takeda, and Janelle Jenstad; documentation written by members of the LEMDO Team

Encoded in TEI P5 according to the LEMDO Customization and Encoding Guidelines

n/a

 Document Types All documents in LEMDO are either born-digital documents or primary documents. Within those two general categories, LEMDO offers additional ways to categorize a file. Born-digital Born-digital documents are anything other than primary texts Documentation Encoding and editorial guidelines; programming, processing, and rendering instructions; how-to instructions; element descriptions; and records of remediation. Responsibilities Responsibilities Project Director A person or organization with primary responsibility for all essential aspects of a project, has overall responsibility for managing projects, or provides overall direction to a project manager. LEMDO uses the term project director for the person who directs the LEMDO project. For anthology leads, use pbd. Proofreader A person who corrects printed matter. LEMDO uses the term proofreader for the person who performs minor corrections to a finalized document, which usually include typographical or rendering fixes. For copy-editing, use resp:edt_cpy. Programmer A person, family, or organization responsible for creating a computer program. Gloss needed. Technical Writer Writer of Technical Material: A person responsible for writing or compiling documentation of the project’s editorial, encoding, and programming practices. Automatically generated this file by extracting its content from lemdo.lite.odd. Tracey El Hajj Tracey El Hajj

Junior Programmer 2019–2020. Research Associate 2020–2021. Tracey received her PhD from the Department of English at the University of Victoria in the field of Science and Technology Studies. Her research focuses on the algorhythmics of networked communications. She was a 2019–2020 President’s Fellow in Research-Enriched Teaching at UVic, where she taught an advanced course on Artificial Intelligence and Everyday Life. Tracey was also a member of the Map of Early Modern London team, between 2018 and 2021. Between 2020 and 2021, she was a fellow in residence at the Praxis Studio for Comparative Media Studies, where she investigated the relationships between artificial intelligence, creativity, health, and justice. As of July 2021, Tracey has moved into the alt-ac world for a term position, while also teaching in the English Department at the University of Victoria.

 Mahayla Galliford Mahayla Galliford

Project manager, 2025-present; research assistant, 2021-present. Mahayla Galliford (she/her) graduated with a BA (Hons with distinction) from the University of Victoria in 2024. Mahayla’s undergraduate research explored early modern stage directions and civic water pageantry. Mahayla continues her studies through UVic’s English MA program and her SSHRC-funded thesis project focuses on editing and encoding girls’ manuscripts, specifically Lady Rachel Fane’s dramatic entertainments, in collaboration with LEMDO.

 Martin Holmes Martin Holmes

Martin Holmes has worked as a developer in the UVic’s Humanities Computing and Media Centre for over two decades, and has been involved with dozens of Digital Humanities projects. He has served on the TEI Technical Council and as Managing Editor of the Journal of the TEI. He took over from Joey Takeda as lead developer on LEMDO in 2020. He is a collaborator on the SSHRC Partnership Grant led by Janelle Jenstad.

 Navarra Houldin Navarra Houldin

Training and Documentation Lead 2025–present. LEMDO project manager 2022–2025. Textual remediator 2021–present. Navarra Houldin (they/them) completed their BA with a major in history and minor in Spanish at the University of Victoria in 2022. Their primary research was on gender and sexuality in early modern Europe and Latin America. They are continuing their education through an MA program in Gender and Social Justice Studies at the University of Alberta where they will specialize in Digital Humanities.

 Janelle Jenstad Janelle Jenstad

Janelle Jenstad is a Professor of English at the University of Victoria, Director of The Map of Early Modern London, and Director of Linked Early Modern Drama Online. With Jennifer Roberts-Smith and Mark Beatrice Kaethler, she co-edited Shakespeare’s Language in Digital Media: Old Words, New Tools (Routledge). She has edited John Stow’s A Survey of London (1598 text) for MoEML and is currently editing The Merchant of Venice (with Stephen Wittek) and Heywood’s 2 If You Know Not Me You Know Nobody for DRE. Her articles have appeared in Digital Humanities Quarterly, Elizabethan Theatre, Early Modern Literary Studies, Shakespeare Bulletin, Renaissance and Reformation, and The Journal of Medieval and Early Modern Studies. She contributed chapters to Approaches to Teaching Othello (MLA); Teaching Early Modern Literature from the Archives (MLA); Institutional Culture in Early Modern England (Brill); Shakespeare, Language, and the Stage (Arden); Performing Maternity in Early Modern England (Ashgate); New Directions in the Geohumanities (Routledge); Early Modern Studies and the Digital Turn (Iter); Placing Names: Enriching and Integrating Gazetteers (Indiana); Making Things and Drawing Boundaries (Minnesota); Rethinking Shakespeare Source Study: Audiences, Authors, and Digital Technologies (Routledge); and Civic Performance: Pageantry and Entertainments in Early Modern London (Routledge). For more details, see janellejenstad.com.

 Joey Takeda Joey Takeda

Joey Takeda is LEMDO’s Consulting Programmer and Designer, a role he assumed in 2020 after three years as the Lead Developer on LEMDO.

 LEMDO Team The LEMDO Team is based at the University of Victoria and normally comprises the project director, the lead developer, project manager, junior developers(s), remediators, encoders, and remediating editors.
Prior Reading <ref target="learn_generalDiagnostics.xml">LEMDO Diagnostics</ref>
Rationale

LEMDO has set up a number of diagnostic checks for your edition that you will find useful as you prepare your edition. These diagnostics provide statistics about characters, entrances and exits, and spoken lines. Diagnostics also help you to encode links correctly to anchors from your collation and annotations. For that reason, we recommend that editors regularly check their edition diagnostics. This documentation will guide you through the process of checking your edition diagnostics and clearing any potential errors therein.

Practice: Run Edition Diagnostics

To run edition diagnostics, first open the file for your modernized text. In the tool bar at the top of your Oxygen window, click the red play button:

Oxygen play button

It typically takes some time to run the diagnostics. Once they are complete, a new tab will automatically open in your default Web browser with an HTML page listing diagnostics. At the top of the Web page will be the date that the diagnostics were generated and the ID for your edition. Each set of diagnostics and statistics is available through a drop-down on the HTML page.

Note that diagnostics that have no potential issues will have the number zero (0) beside them, while those diagnostics that do find potential issues will give the number of issues you need to resolve.

Edition Statistics

The first drop-down on your edition diagnostics page is for statistics. This section includes counts for number of acts, scenes, speeches, stage directions, and speaking characters in your edition. In addition, the length of your modernized text is given in both characters and words. Finally, you can see the total number of elements and attributes that you and the LEMDO team have added to your file.

The statistics section also offers statistics by character. In this table, each character in your edition is listed along with the number of speeches they give, number of words that they speak, their average speech length, the average length of words that they speak, the number distinct words that they use, and how many of their total words are distinct (given as a decimal between 0.0 and 1.0 with 1.0 meaning each word spoken is distinct). This information may be helpful to you when you write your critical introduction.

Unused Anchors Diagnostic

LEMDO uses anchors and pointers to link annotations and collations to modernized texts. All anchor elements should be linked to from somewhere in your edition. This diagnostic finds anchor elements that are not linked to from anywhere within the edition.

To resolve this diagnostic, you will first check that the anchor is not being linked to from another edition by searching the texts directory in the LEMDO repo. (Other editions should not be linking to anchors in your edition. They should be linking to the acts/scenes and speeches in your modern text, speeches or WLNs in your semi-diplomatic text, and divs or paragraphs in your critical paratexts.) Follow these steps to check that no other edition is linking to your anchors: Copy the xml:id of the unused anchor. You can copy this directly from your edition diagnostics. Right click on the texts directory in Oxygen’s project pane. Select Find/Replace in Files… Paste the xml:id in the Text to find text box. Click Find All. If there are no files linking to the anchor (as is likely the case, given LEMDO’s general diagnostic that looks for such links), only one result will come up (the anchor itself). In those cases, you may delete the unused anchor. If there is another edition linking to the anchor, leave the anchor in place but let the LEMDO team know that someone is linking to your edition so that we can help the other editor link in the LEMDO-allowed ways.

Pointers not Pointing at Anything Diagnostic

All pointers must link to an entity with an xml:id. This diagnostic finds ptr elements that are trying to link to non-existent xml:ids. If a file is committed with a pointer not pointing at anything, the LEMDO build will break. Checking this diagnostic before you commit files containing new ptr elements prevents the build breaking on this issue.

To resolve this diagnostic, search your edition for the pointer that is not pointing at anything and correct the value of its target attribute so that it correctly links to an entity. These errors are almost always typos (3411 when you mean 341.

Annotations and Collations Whose Pointers Are in the Wrong Order Diagnostic

When annotations and collation link to anchors in a modernized text, the first target must link to the anchor element that comes first in the modernized text while the second target must link to the anchor that comes second. If the anchors are invoked in the wrong order, our processor will not be able to mark the span and the LEMDO build will break. Checking this diagnostic before you commit your annotations or collation file prevents the build breaking on this issue.

To resolve this diagnostic, search for the annotation or collation entry that links to anchors in the wrong order and correct the order. Run your edition diagnostics again to ensure that the issue is fixed.

facs Attributes that do not Follow a Consistent Expected Pattern Diagnostic

LEMDO allows you to make links from pb (page beginning) elements to facsimile images using the facs attribute. Because all facsimile images are associated with xml:ids that are consecutively numbered and we link to facsimile images for all pages in semi-diplomatic transcriptions (including blank pages), we expect the links to follow the pattern of consecutively numbered xml:ids. This diagnostic finds any inconsistencies in the expected pattern.

To resolve this diagnostic, check that your facs links are correct. See <ref target="learn_MS_linkFacsimiles.xml">Link to Facsimiles from Semi-Diplomatic Transcriptions</ref> for more information.

Missing speaker Elements Diagnostic

All speeches in modernized texts should have speech prefixes encoded using the speaker element. This diagnostic finds sp elements (speeches) without a child speaker element. If you have a compelling reason not to give a speech prefix to a speech, take up the matter with your anthology lead(s), who will in turn take the matter to the LEMDO team.

To resolve this diagnostic, open your modernized text file and add speaker elements to speeches that do not yet have them. For more information on speech prefixes in modernized texts, see <ref target="learn_encodeSpeaker.xml">Encode Speakers in Modernized Texts</ref>.

Note that not all speeches in semi-diplomatic transcriptions will have speech prefixes. See <ref target="learn_semiDipSpeaker.xml">Encode Speech Prefixes in Semi-Diplomatic Transcriptions</ref> and <ref target="learn_speechesWithoutSpeakers.xml">Speeches without Speech Prefixes</ref> for our encoding practice in semi-diplomatic transcriptions.

Entrances and Exits

LEMDO lists all of the entrances and exits encoded in each scene of your modernized texts in the entrances and exits section of the edition diagnostics page. This information is often helpful to editors determining scene divisions. It is also useful information if you want to create a doubling chart.

If the list seems to be missing an entrance or exit, check that your encoding is correct. All entrances and exits should be encoded using the stage element. For entrances, ensure that the type attribute on the stage element has the entrance value on it. For exits, ensure that the type attribute has the exit value on it.

For more detailed information on encoding stage directions in modernized texts, see <ref target="learn_encodeStageDirections.xml">Encode Stage Directions in Modernized Texts</ref> and <ref target="learn_stageType.xml">Identify Stage Direction Types</ref>. For information on encoding stage directions in semi-diplomatic transcriptions, see <ref target="learn_encode_OSstage.xml">Encode Stage Directions in Semi-Diplomatic Transcriptions</ref>.

Other Resources LEMDO YouTube video: Putting It All Together (Editorial)
Further Reading <ref target="learn_checkLinks.xml">Check Link Validity</ref>