LEMDO: Appendix 3. Supplementary Texts

Appendix 3. Supplementary Texts

This chapter of our documentation is still in beta. We welcome feedback, corrections, and questions while we finalize the page in our 2024–2025 work cycle.

¶ Introduction to Supplementary Materials

Editors will want to consult with their anthology leads about the advisability or necessity of including supplementary materials. One important consideration is whether or not another project has already created or is likely to create a full edition of the text, in which case it would probably be better to point users to that full edition rather than include an excerpt in your own edition.

You might also think about whether or not it would suffice to include a block quotation in your critical introduction. You can and should include short block quotations in your critical introduction to support your points as necessary.

If you do include supplementary materials, keep in mind that the primary purpose of supplementary materials is likely to be pedagogical. Do not proliferate supplementary materials merely to support the argument(s) made in your critical introduction. To keep LEMDO lightweight and nimble, please be sure to select only supplementary materials that will be genuinely helpful to teachers and students interested in historical context and the discursive field.

LEMDO is also dealing with legacy supplementary materials from the legacy projects (ISE, DRE, and QME), some of which are more like critical paratexts (as indeed they were if they were published in an ISE-Broadview edition) and some of which are full editions in their own right (such as David Bevingtonʼs Galathea).

From the perspective of LEMDOʼs processor, supplementary materials are not a distinct type of text and have no logical place in any of the LEMDO taxonomies. They do not have a special schema nor do they have any special processing rules. LEMDO neither prohibits nor encourages supplementary materials. A supplementary document does not have a category in LEMDOʼs taxonomies by virtue of supplying some text. Rather, you need to think about whether the supplementary document is better classified as a critical paratext or as an excerpt from a primary text. You also need to think about the editorial treatment you have given the supplementary material.

¶ Document Type: Primary or Paratext

Your supplementary materials may be either primary or paratext. This distinction can be a bit fuzzy for some supplementary materials. A supplementary document is more like a primary text if it is an excerpt that could potentially be expanded into a full edition or if it gives the complete text of a short source (e.g., a pamphlet). In this case, you will give your document the document type value of ldtPrimary.¹. Sometimes, a supplementary document might function more like a critical paratext, with an explanatory paragraph or two or excerpts from multiple texts in the one file, in which case you will want to give it the document type value of ldtBornDigParatext.² You will want to make this call in conversation with your anthology lead. For example, the policy of DRE is that any supplementary materials must be treated as primary texts and given full editorial treatment. (In fact, DRE strongly discourages the inclusion of supplementary texts altogether because of the difficulty of producing a good edition of an excerpt.)

The document type of your supplementary (primary or paratext) determines how you create annotations. See Editorial Notes and Annotations for Supplementary Texts.

¶ Editorial Treatment

If your supplementary document falls into the ldtPrimary category, you will also need to capture the nature of your editorial treatment of the material. The options are as follows:

letSemiDiplomatic: Use in the very rare case that the original spelling has been retained in the supplementary document. Note that this editorial treatment is not advisable if the supplementary document is going to be of any use in the classroom. The one exception might be an excerpt from a work like The Faerie Queene where the spelling has semantic value.

letModernized: Use this value for supplementary documents that have been given the full editorial treatment as set out in an anthologyʼs editorial guidelines, such as the DRE Editorial Guidelines or (for legacy texts) the ISE Editorial Guidelines. Very few new supplementary documents will fall into this category. We have a few legacy supplementary documents that offer full editions (such as David Bevingtonʼs Galathea).

letExcerpted: Use this category for texts that are not complete, usually because of editorial selection in service of a specific goal. This is the normal editorial treatment of supplementary documents. This value can be combined with any other value in this list (e.g., a document could have two


                                                <catRef>

elements and two editorial treatment values: letExcerpted and letMixed).

letMixed: Use for supplementary materials in which a variety of possibly incongruous editorial approaches have been mixed. LEMDO created this value for legacy supplementary texts where we could not determine the editorial treatment. We do not advise new projects or new editors to take this approach to any text.

These values are not mutually exclusive. For example, the legacy supplementary documents usually have both the letExcerpted and the letMixed editorial treatments.

Note that we do not give lwt: categories to supplementary materials. Do not attempt to categorize your supplementary material as prose, verse, or drama.

¶ Other Taxonomies

You will want to use other taxonomies as needed in other parts of the


                                          <teiHeader>

of your supplementary documents. For example, you will want to use the relevant


                                          @docStatus

value on your


                                          <revisionDesc>

element and the emdRespTaxonomy to give credit where credit is due.

¶ Encode Supplementary Texts

¶ Introduction

LEMDO does not generally encourage supplementary materials in an edition. However, LEMDO is converting and remediating a number of editions that do include supplementary materials that offer excerpts from source materials, contextual materials, and analogues. LEMDO has devised three ways of treating supplementary materials.

Treat as critical paratexts (most common treatment)

Treat as primary sources

Treat as full editions (least common)

Most of the supplementary materials LEMDO has remediated function as critical paratexts. They were initially conceived for Broadview print editions and/or intended for classroom use. They were not prepared according to full editorial principles; i.e., the editor did not go back to an early witness, did not offer a collation, and did not worry about control text. They will have been silently modernized or even taken from already-modernized sources. Most of these supplementary materials are single excerpts from a text, a collection of excerpts from various texts on the same topic (e.g., war in the sixteenth-century), or a number of excerpts from a single text. Editors often preface excerpts with commentary, which means that the supplementary file is really a collection of quotations with some commentary. LEMDO categorizes these supplementary materials as critical paratexts (i.e., they will have the document type ldtBornDigParatextCritical. At processing time, these files will be processed and rendered the same way as other critical paratexts.

A few supplementary materials have been given a more robust editorial treatment. They may have modernized according to the same editorial guidelines. There may be some awareness of the textual history, in the form of annotations or a short textual note. They may be long enough that they have the potential to be scaled up into full editions.

Some editors have offered full semi-diplomatic transcriptions or modern editions of texts that relate to the work they are editing. For example, David Bevington offered a modernized and encoded text of Galathea with his edition of As You Like It. Michael Best’s edition of King Lear includes a modernized, encoded, and annotated text of Nahum Tate’s King Lear, prepared by Lynne Bradley. In the conversion and remediation process, LEMDO has chosen to put these full texts of plays into their own play portfolios. Galathea is in the lemdo/data/texts/Gal portfolio, but licensed for inclusion in the edition of As You Like It. If you plan to prepare a full text of another work for your edition, consult with your anthology lead and/or with the LEMDO team at UVic before you begin. We prefer resource-sharing and linking over duplication of effort. For the purposes of this present piece of documentation, we do not consider these full editions to be supplementary. They are governed by the encoding guidelines for modern texts.

¶ Choosing your Document Type

If your supplementary text is a critical paratext, do the following:

Give it the document type ldtBornDigParatextCritical

Put the title you want to give the page into the


                                                <title>

element of the


                                                <teiHeader>

of the file.

Provide a brief statement of your source (along with context if you wish) in the first


                                                <div>

of the file. (You may also provide a full source description in the


                                                <sourceDesc>

in the


                                                <teiHeader>

if you wish.)

If you would like to treat your supplementary text as a primary source, do the following:

Give it the document type ldtPrimary

Identify your editorial treatment. The possibilities are semi-diplomatic (letSemiDiplomatic), modern spelling (letModernized), or mixed (letMixed).

Unless you are providing a complete short text (a sonnet, a proclamation, a pamphlet, for example), you will also need to add an additional editorial treatment for excerpted (letExcerpted).

Supply a source description


                                                <sourceDesc>

Give a brief explanation of the passages you have chosen in the


                                             <samplingDecl>

of the


                                                <teiHeader>

Use the


                                                <front>

element to give your supplementary primary text a title. (It can be the same as the


                                                <title>

in the


                                                <teiHeader>

Use the first


                                                <div>

of the


                                                <body>

to give a narrative statement of your source and (if you wish) some contextual information.

If your supplementary file consists of multiple excerpts, each of which needs a narrative statement of your source and contextual information, then you need set up your file as .

¶ Filing Your Supplementary Texts in the Repository

¶ Document Types for Supplementary Texts

Supplementary texts can be either ldtPrimary or ldtBornDigital.

¶ Title of Your Supplementary Page

The title displayed at the top of your supplementary text on the website will be whatever you type into the


                                          <title>

element in the


                                          <titleStmt>

in the


                                          <teiHeader>

(i.e., in the metadata at the top of your file). Do not add a


                                          <front>

element to your supplementary text file, unless

¶ Basic Structural Elements: Prose or Verse

¶ Introduction and Source Information

You will probably want to give a few sentences of context and/or plot summary for the supplementary text and indicate your source. You will capture this information in the first


                                          <div>

of the


                                          <body>

of your file. You must give the


                                          <div>

an xml:id. Give the section a heading in the


                                          <head>

element. What information you provide about the source and your editorial treatment thereof is a matter for you to decide or for your anthology lead to prescribe. LEMDO does recommend that you give the STC (or Wing) and/or ESTC number for the source. The following example from Michael Best’s edition of King Lear.

<div xml:id="emdLr_Arcadia_M_source">
  <head>Introduction and Source</head>
  <p>Shakespeare’s main source for the plot concerning Gloucester and his two sons was Sir Philip Sidney’s popular prose romance, <title level="m">Arcadia</title>. It is set in an idealized, pastoral world full of love at first sight, savage beasts, and complex, overlapping narratives. A central narrative involves the friends Pyrocles and Musidorus as they undertake quests in pursuit of their loves. One adventure grows from accidentally overhearing a conversation between a blind father and his son. Shakespeare took this short episode and expanded it into the sub-plot of the Duke of Gloucester and his two sons, Edgar (here Leonatus) and Edmund (Plexirtus). Shakespeare develops the plot further, interweaving it with the main plot as Cornwall becomes the agent by which Gloucester is blinded (though Edmund is involved in betraying his father), and in the intrigues that Edmund generates by becoming involved with both Goneril and Regan. He also gives Edmund an almost Iago-like skill in manipulating those he seeks to destroy. This version is modernized from the transcription of STC <idno type="STC">22539a</idno>in <title level="m">Renascence Editions</title>, created by Richard Bear and archived on the <ref target="http://www.luminarium.org/">
    <title level="m">Luminarium</title>
  </ref> website.</p>
</div>

¶ Omissions

If you wish to omit a word, string, or short passage, use the


                                          <gap>

element with the


                                       @reason

attribute and the value sampling.

If your supplementary text samples disparate from a larger text (i.e., includes extracts from widely separated sections of the text), you may prefer to structure your file as .

¶ Notes on Supplementary Texts

See Editorial Notes and Annotations for Supplementary Materials for instructions for adding notes to supplementary texts.

¶ Editorial Notes and Annotations for Supplementary Materials

¶ Previous Reading

LEMDO generally does not encourage projects to create supplementary materials, on the grounds that another project will likely create full editions of any texts excerpted in supplementary materials. Read LEMDOʼs general statement on supplementary materials: Introduction to Supplementary Materials.

¶ Rationale

Supplementary texts must be pedagogically useful. Any editorial notes or annotations must therefore be written to help the student reader. Do not provide elaborate textual notes or commentary. Provide glosses and brief commentary as necessary.

¶ Practice

We have two practices, one for each type of supplementary text:

When supplementary texts are born-digital, treat them as paratexts and add editorial notes. To annotate a word, insert a


                                                <note>

element immediately after the word. Give the


                                             @type

attribute the value of editorial. Type your gloss, annotation, or explanation in the text node of the


                                                <note>

element.

When supplementary texts are primary, treat them as primary modern texts. Create an annotation file. Add anchors to your supplementary text and point to those anchors from the annotation file.

¶ Editorial Notes for Born-Digital Supplementary Materials: Step-by-Step

¶ Examples

<p>They are all four false and erroneous: the two first because God hath not given every man authority to revenge the injury done to him, but sayeth, <foreign xml:lang="la">Mihi vindicta, and ego rependam</foreign>.<note type="editorial">
<quote>Vengeance is mine, and I shall recompense.</quote> (<ref type="bibl" target="bibl:THEB2">Hebrews 10:30</ref>)</note>
</p>

¶ Annotations for Primary Supplementary Materials: Step-by-Step

How you annotate primary supplementary materials (i.e., documents that have ldtPrimary as their document type) depends on their editorial treatment.

If the supplementary document has been given a mixed editorial treatment (i.e., a document with the letMixed value), then you must use the


                                          <note>

element. Note that almost all of the supplementary materials prepared for the legacy projects have been given the value letMixed by LEMDO. Remember that the letMixed value is an editorial treatment value that LEMDO designed to deal with legacy supplementary materials.

Going forward, if you create supplementary materials at all (which is not advised by LEMDO), you will normally give them the editorial treatment letExcerpted and use the


                                          <note>

element to add glosses and light annotations as necessary.

If you choose to give your supplementary document the modern editorial treatment (with letModernized) or semi-diplomatic editorial treatment (with letSemiDiplomatic), then you must use anchors in the supplementary document and create a stand-off annotation file with pointers pointing to the anchors. If you plan to expand your supplementary document into a full edition in its own right, LEMDO recommends that you choose to give your supplementary document the modern-spelling editorial treatment (letModernized) and create stand-off annotations using anchors and pointers so that you can expand on the work later without having to re-encode your work. Again, you will want to confer with your anthology lead about the wisdom of undertaking this work for a supplementary document in your edition.

¶ Editorial Notes for Primary Supplementary Documents with Mixed Editorial Treatment

This example is an excerpt from Titus Andronicus included in Jessica Slightʼs ISE-Broadview edition of Othello:

<sp>
  <speaker>Aaron</speaker>
  <lg>
    <l>Why then she is the devil’s dam.<note type="editorial">Mother.</note> A joyful issue!</l>
  </lg>
</sp>

¶ Editorial Notes for Primary Supplementary Documents with Modern Spelling Editorial Treatment

Remember that this treatment is not necessary unless you plan to expand your supplementary document into a full edition. The first example shows the anchors in a file that has the editorial treatments letModernized and letExcerpted. The second example shows the stand-off annotations file that includes annotations for the first file. The values of


                                          @target

and


                                          @targetEnd

point to the first document and the anchors therein. (See Create Anchors for detailed instructions on how to insert anchors and pointers in your files.)

<p>Then he took the wife of the brother he had butchered, capping <anchor xml:id="emdSaxo_M_anc_1"/>unnatural murder<anchor xml:id="emdSaxo_M_anc_2"/> with incest.</p>

<note type="annotation" target="doc:emdSaxo_M#emdSaxo_M_anc_1" targetEnd="doc:emdSaxo_M#emdSaxo_M_anc_2">
<note type="label">unnatural murder</note>
<note type="gloss">These words of the Ghost in <title level="m">Hamlet</title>, 1.5.25, exactly translate <foreign xml:lang="la">parricidium</foreign>, which (with <foreign xml:lang="la">parricida</foreign>) occurs constantly in this narrative, and has been variously rendered by <q>slaying of kin</q> and <q>fratricide</q>.</note>
</note>

¶ Marginal Notes in Source

Generally, you will exclude marginal notes in the early modern text from your supplementary materials. However, if a marginal note (whether beside or below the text block) in your source text is important to your argument, you may capture it in your supplementary document using the


                                             <note>

element with the value marginal on the


                                          @type

attribute. You may capture marginal notes whether the supplementary document is functioning as a born-digital paratext or as a primary document (with either letMixed or letModernized or letSemiDiplomatic). LEMDO will render these notes as pop-up notes, regardless of their place on the original page.

The following example is from a legacy supplementary document in James Mardockʼs edition of Henry V. He has modernized the text and included a marginal note from the source that is essential to our understanding of the date of the events:

<p>Henry, prince of Wales,<note type="marginal">Anno reg. 1</note> son and heir to King Henry the Fourth, born in Wales at Monmouth on the river of Wye</p>

Notes

1.Do not use ldtPrimaryText for supplementary files. We reserve this value for modern-spelling texts and semi-diplomatic transcriptions.↑

2.Do not use the ldtBornDigParatextCritical for supplementary files. We reserve this value for critical, general, textual, and performance introductions.↑

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.

Kim Shortreed

Kim is a PhD Candidate in Media Studies and Digital Humanities, through UVicʼs English Department. Kim has worked for years in TEI and XML, mostly through the Colonial Despatches website, and in a number of roles, including technical editor, research and markup, writing and editing, documentation, and project management. Recently, Kim worked with a team of Indigenous students to find ways to decolonize the Despatches projectʼs content and encoding practices. Part of Kimʼs dissertation project, Contracolonial Practices in Salish Sea Namescapes, is to prototype a haptic map, a motion-activated topography installation that plays audio clips of spoken toponyms, in SENĆOŦEN and English, of the W̱SÁNEĆ Territory/Saanich Peninsula, respectively.

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.

Michael Best

Michael Best is Professor Emeritus at the University of Victoria, BC. He is the Founding Editor of the Internet Shakespeare Editions, of which he was the Coordinating Editor until 2017. In print, he has published editions of works of Elizabethan magic and huswifery, a collection of letters from the Australian goldfields, and Shakespeare on the Art of Love (2008). He contributed regular columns for the Shakespeare Newsletter on Electronic Shakespeares, and has written many articles and chapters for both print and online books and journals, principally on questions raised by the new medium in the editing and publication of texts. He has delivered papers and plenary lectures on electronic media and the Internet Shakespeare Editions at conferences in Canada, the USA, the UK, Spain, Australia, and Japan.

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.

Nicole Vatcher

Technical Documentation Writer, 2020–2022. Nicole Vatcher completed her BA (Hons.) in English at the University of Victoria in 2021. Her primary research focus was womenʼs writing in the modernist period.

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

The Bible. The Geneva Bible. London, 1587. STC 2146. ESTC S3398.

Metadata

Authority title	Appendix 3. Supplementary Texts
Type of text	Documentation
Short title
Publisher	Linked Early Modern Drama
Series
Source
Editorial declaration
Edition
Encoding description
Document status	prgGenerated
License/availability