LEMDO: Remediate Collations

Remediate Collations

¶ Introduction

This document deals with the remediation of collations that were prepared for the ISE platform and need to be reworked for the LEMDO platform. Collations track variations in a text both as it differs between copies of an early edition and as it changes in later editions because of editorial interventions. The work of remediating collations entails fixing inconsistencies within the edition and bringing it into alignment with DRE guidelines and LEMDO encoding practices.

¶ Check Anchors and Pointers

Check that no collations are missing or misplaced on the LEMDO site before you begin remediating them. Compare collated words on the staticized DRE, ISE, or QME website against your modern edition and the collations file. Read each collation to ensure it is anchored to the correct word or phrase. See also Create Anchors.

Do not delete anchors in the modern file. There may be an annotation or collation that you do not know about that is pointing to those anchors. If you need to anchor a collation to a different word, add new anchors to the word and point the collation to the newly anchored word.

Note that the programmatic addition of anchors and targets to the modern text and collation file (respectively) does not always work. This is because the conversion removes square brackets, which means lemmas no longer match what is in the modern text. In these cases, the conversion makes the TLN the target instead and remediators must add anchors in place of the TLN targets.

¶ Add Anchors and Pointers

To add an anchor to a text, follow these steps:

Highlight the text around which you want to place an anchor.

Hit Ctrl+shift+a on a PC or Cmd+shift+a on a Mac to add numbered anchors.

Return to the collation file and change the TLN targets to the anchors you just made.

¶ Replace Ellipses

The lemmas of converted collations will contain instances of three spaced periods ( . . . ) used as an ellipsis. We never want three spaced periods to be used as ellipses, so you must replace them with an ellipsis character ( … ) from the character map on your computer or from LEMDOʼs pre-mapped characters. See Practice: Insert an Ellipsis Character.

Note that the


                                          <rdg>

elements may contain editorial elisions that are indicated by ellipses (either three spaced periods or the ellipsis character, whichever the editor used in the original file). You need to determine if the ellipsis occurred in the witness (i.e., the editor is quoting an ellipsis character) or if the editor is omitting material from a long reading and indicating the fact of omission with their own ellipsis character:

If the ellipsis occurs in the witness, type an ellipsis character and wrap it in the


                                                <pc>

element.

If the ellipsis indicates an editorial omission, replace it with the


                                                <gap>

element, the


                                             @reason

attribute, and the "sampling" value.

¶ Shorten Lemmas

Shorten lemmas that are more than three words long. Always keep at least the first and last words of the lemma. Remove any words that will not help readers identify the passage that is being annotated (e.g., “the”, “a”, “my”, “with”, “it”).

¶ Get xml:ids

Get xml:ids for the substantive variants in your collation file. First, find the editions and witnesses pointed to in your document. If the editions and witnesses are already in the LEMDO ecosystem, they can be found in two places:

LEMDO’s bibliographic database (BIBL1) contains bibliography entries for the early editions up to about 1700 (Q1, Q2, F, F2, etc). Each entry includes the DEEP number, which will help you cross-reference and ensure that you are selecting the right edition from BIBL1. We include the xml:id of the entry on the BIBL1 page, in the column on the right. For example, the first edition of The Honest Whore is listed in BIBL1 as: Dekker, Thomas, and Thomas Middleton. The Converted Courtesan. London: Valentine Simmes, 1604. STC 6501. DEEP 362. The xml:id of this edition in LEMDO is DEKK5. If the edition you want to collate is not yet in BIBL1, send all the bibliographical information for the edition (including the DEEP number) to the LEMDO team at UVic (lemdotech@uvic.ca). For more information on necessary bibliographical details, see Practice.

¶ Create Your List of Witnesses

Once you have xml:ids for all of the editions you wish to include in your stemma, you will make a witness list in your XML file. This is a list of witnesses collated, each with their edition-specific sigla. LEMDO uses the TEI


                                          <listWit>

element to capture this list in the


                                          <teiHeader>

of the collation file. Each witness is listed in a


                                          <witness>

element in the


                                          <listWit>

parent element. See 12.1.4.3 The Witness List in the TEI Guidelines.

The


                                          <witness>

element has two required attributes:


                                       @xml:id

and

@n

. There is one optional attribute,


                                       @corresp

, as explained below:

You will create the xml:id of the witness in your witness list. It will necessarily be unique in the overall LEMDO project because the xml:id includes the unique string of characters that make up the xml:id of your collation file.

The

@n

attribute allows you to assign an edition-level siglum for the witness. Sigla for your edition are defined in your witness list. The sigla for your witnesses do not have to be unique across LEMDO, but they do need to be unique in the context of your edition.

There are two possible ways to provide information about your witness. If the relevant entry in BIBL1 provides all the required information, then you can simply point to it from the


                                          <witness>

element using the


                                       @corresp

attribute. In this case, the


                                          <witness>

element itself must be empty. You will notice in the example of a


                                          <listWit>

element below that the witness list consists mainly of a list of empty witness elements that have attributes and values but no content.

In some cases, however, you may need to provide a more detailed explanation of a witness which is somehow more complex or problematic. In this case, do not use


                                       @corresp

; instead, provide your explanation inside the


                                          <witness>

element, making sure to include links to any relevant items in BIBL1 using the


                                          <ref>

element, as shown below.

Attribute	Value	Example
`@xml:id`	Must be unique to the LEMDO project. Make sure it is unique by using the already-unique name of the file, then adding your siglum.	emd1HW_M_collation_Q1
`@corresp`	If the entry is in BIBL1, use the bibl: prefix plus the unique xml:id of the entry in BIBL1.	bibl:DEKK14 (to point to an entry in the LEMDO bibliography)
`@n`	Your siglum, which must be unique to your edition but not to the whole project.	Q1 Dodsley

For empty


                                          <witness>

elements with the


                                       @corresp

attribute, LEMDO processing will pull in the information from BIBL1 to populate the element:

If you add content to the text node, the LEMDO processor will not pull in the data from BIBL1; instead, your own content will be used, but any links you have created in that content will function to retrieve BIBL1 entries:

<witness xml:id="emd1HW_M_collation_Q2S" n="Q2S">
<ref type="bibl" target="bibl:DEKK4">The second quarto of <title level="m">The Honest Whore</title>
</ref> was partially set from <soCalled>standing type</soCalled> that was never distributed back into the cases after Q1 was printed. Q2S refers to the pages that were printed from the standing type.</witness>

¶ Replace LEWs

In the process of converting old IML collations, LEMDO has created a lazy editor witness (LEW). As a remediator, you need to relplace these LEWs with a proper pointer to an xml:id in the


                                          <listWit>

. Note that some editors can use the lew: prefix while they are collating, in order to save time. We can easily convert their lew: prefixes to pointers.

Witnesses are under the


                                          <app>

parent element. The source reading will be wrapped in the


                                          <lem>

element with the attribute


                                       @source

. Other witnesses will be wrapped in the


                                          <rdg>

element with the attribute


                                       @wit

. In both cases, you will give the value of a hash character followed by the xml:id of your witness as defined in your


                                          <listWit>

. See the example below from Timon of Athens.

<app from="doc:emdTim_M#emdTim_M_anc_698" to="doc:emdTim_M#emdTim_M_anc_699">
  <lem source="#emdTim_M_collation_F1">as a cantherizing</lem>
  <rdg wit="#emdTim_M_collation_Rowe1709">as a Cauterizing</rdg>
  <rdg wit="#emdTim_M_collation_Capell1768">cancerizing</rdg>
</app>

¶ Point to Multiple Sources for a Reading

Sometimes more than one source will have the exact same reading. If this is the case:

Create a


                                             <lem>


                                             <rdg>

element as described above.

Provide the xml:id of your first witness as described above.

Provide the xml:id of successive witnesses in the same element with one space between each witness.

<rdg wit="#emd1HW_M_collation_Q1 #emd1HW_M_collation_Q2S">others at an other doore. Enter</rdg>

¶ Replace Any Lingering IML Braces

Use the find function (ctrl+f or cmd+f) to search for glyphs that are represented by curly brackets. Remove the curly brackets. Tag the glyphs using the

<g>

element and


                                       @ref

attribute. The value of


                                       @ref

is the "g:" prefix and the xml:id of the glyph. Glyph xml:ids are listed in Typographical Glyphs Taxonomy.

¶ Encode Supplied Materials

Some editors collate stage directions to indicate supplied materials, note differences between the modern text and early modern editions, and give credit to their editorial predecessors where credit is due. In this case, you will need to ensure that supplied materials are correctly encoded in your collation. To do this, you will follow these steps:

Identify supplied stage directions in the lemma (the text node of the


                                                <lem>

element) that have not been encoded. These are indicated with square brackets.

Wrap the supplied material in the


                                                <supplied>

element.

Remove the lingering square brackets.

Note that you will leave any square brackets in the


                                          <rdg>

elements as we consider them part of a quotation. See the example below from Friar Bacon and Friar Bungay:

<app from="doc:emdFBFB_M#emdFBFB_M_anc_640" to="doc:emdFBFB_M#emdFBFB_M_anc_641">
  <lem source="#doc:emdFBFB_M_collation_ThisEd">
    <supplied>She steps forward.</supplied>
  </lem>
  <rdg wit="#doc:emdFBFB_M_collation_Dyce1861">[Comes forward]</rdg>
  <rdg wit="#doc:emdFBFB_M_collation_Bevington2002">[She approaches Lacy.]</rdg>
</app>

Prosopography

Isabella Seales

Isabella Seales is a fourth year undergraduate completing her Bachelor of Arts in English at the University of Victoria. She has a special interest in Renaissance and Metaphysical Literature. She is assisting Dr. Jenstad with the MoEML Mayoral Shows anthology as part of the Undergraduate Student Research Award program.

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 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 is LEMDO’s Consulting Programmer and Designer, a role he assumed in 2020 after three years as the Lead Developer on LEMDO.

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

Project manager 2022–present. Textual remediator 2021–present. Navarra Houldin (they/them) completed their BA in History and Spanish at the University of Victoria in 2022. During their degree, they worked as a teaching assistant with the University of Victoriaʼs Department of Hispanic and Italian Studies. Their primary research was on gender and sexuality in early modern Europe and Latin America.

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.

Bibliography

Dekker, Thomas and Thomas Middleton. The Honest Whore, With, The Humours of the Patient man, and the Longing Wife. London: Valentine Simmes, 1604. STC 6501.5. DEEP 363.

Drake, Nathan. Shakespeare and His Times. 2 vols. London, 1817.

Orgography

LEMDO Team (LEMD1)

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.

Metadata

Authority title	Remediate Collations
Type of text	Documentation
Short title
Publisher	University of Victoria on the Linked Early Modern Drama Online Platform
Series	Linked Early Modern Drama Online
Source	TEI Customization created by Martin Holmes, Joey Takeda, and Janelle Jenstad; documentation written by members of the LEMDO Team
Editorial declaration	n/a
Edition	Released with Linked Early Modern Drama Online 1.0
Encoding description	Encoded in TEI P5 according to the LEMDO Customization and Encoding Guidelines
Document status	prgGenerated
Funder(s)	Social Sciences and Humanities Research Council of Canada
License/availability	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.