LEMDO: Encode Your Edition Page

Encode Your Edition Page

Prior Reading

Introduction to Editions and Licensing

Edition Directories

Encode File Categories for Edition Files

Rationale

An edition is comprised of multiple XML files all contained in a single directory in the LEMDO repository. One of the XML files is an edition page. The edition page serves two functions:

It contains the metadata for your edition that LEMDO needs in order to publish your edition in the correct anthology (or anthologies), including credits and a list of completed edition components.

It contains the content of the edition landing page curated and organized according to your anthology’s preferred layout.

This documentation will explain how to encode both the metadata and the contents in your edition page.

Practice: Create an Edition Page

The LEMDO team will create an edition page for you from your anthology’s edition page template upon request. When you start work on your LEMDO edition, contact the LEMDO team to ensure that they have created an edition page for you.

Components of Metadata

Information about your edition belongs in the


                                          <teiHeader>

of your edition page. The main components of the metadata are:


                                                <fileDesc>


                                                <profileDesc>


                                                <encodingDesc>


                                                <revisionDesc>

The File Description

The


                                          <fileDesc>

element contains information about the text encoded in the file. This includes the text’s title, responsibility statements for the author and all of the people (or organizations) who contributed to the file, an edition statement, publication information, a series statement, a notes statement, and a description of the text’s source.

Practice: Encode the Title Statement

There are four key components of the


                                             <titleStmt>

element: one child


                                             <title>

element, at least five


                                             <respStmt>

elements, at least one


                                             <sponsor>

element, and at least one


                                             <funder>

element.

You will give your edition an authority title in the


                                             <title>

element. Give the


                                             <title>

element a


                                          @type

value of "main". This is the title that will appear at the top of your edition page and on the front cover and half-title page of the printed edition of your play. You will want to think carefully about the title of your edition. Should it be Othello, the Moor of Venice, Othello, or The Tragedy of Othello? Each title constitutes a different critical statement about your edition. You will want to confer with your anthology lead as you finalize your edition title.

You will give credit to each person or group who worked on your edition in the


                                             <respStmt>

elements of your edition page. This includes research assistants, encoders, anthology leads, and peer reviewers (if your edition has undergone open peer review). All LEMDO edition pages are required to provide responsibility statements for at least the following five roles:

Editor

Anthology lead(s)

The LEMDO team (either for their work converting and remediating the edition, or for their encoding work)

Additionally, anyone who has contributed to, overseen, reviewed, or supervised your edition who has not been credited in any specific files must be given credit in the edition page. Those who have been credited in specific files also may be given credit again in the edition page. Your anthology leads can give you guidance for adding any additional responsibility statements. For more information on encoding the


                                             <respStmt>

element, see Encode Responsibility Statements.

For information on how to encode the


                                             <sponsor>

and


                                             <funder>

elements, see Encode Sponsors and Funders in Your Metadata.

Example Title Statement

<titleStmt>
 <title type="main">Authority Title</title>
 <respStmt>
 <resp ref="resp:edt">Editor</resp>
 <persName ref="pers:PEEE1">Your Name</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:edt_coord">Co-Coordinating Editor</resp>
 <persName ref="pers:PEEE1">Anthology Lead Name</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:cph">Copyright Holder (Editorial content)</resp>
 <persName ref="pers:PEEE1">Your Name</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:cph">Copyright Holder (XML and interface)</resp>
 <orgName ref="org:UVIC1">University of Victoria</orgName>
 </respStmt>
 <respStmt>
 <resp ref="resp:edt_mrk">Encoder</resp>
 <orgName ref="org:LEMD1">LEMDO Team</orgName>
 </respStmt>
 <sponsor ref="org:OOOO1"/>
 <funder>
 <ref target="https://www.sshrc-crsh.gc.ca/">Social Sciences and Humanities Research Council of Canada</ref>
 </funder>
</titleStmt>

Practice: Encode the Edition Statement

You will use the


                                             <editionStmt>

element to specify in which version of an anthology your edition was first published. For instructions on how to encode your edition page’s


                                             <editionStmt>

, see Practice: Write the Edition Statement.

Practice: Encode the Publication Statement

You will license your edition for publication in an anthology using the


                                             <publicationStmt>

element. For detailed instructions on how to encode your edition page’s


                                             <publicationStmt>

, see License Your Edition for Publication.

Practice: Encode the Notes Statement

You will include all completed¹ components of your edition in the


                                             <notesStmt>

element. The


                                             <notesStmt>

element contains a child


                                             <relatedItem>

element for each XML file that you wish to publish with your edition, including all of your apparatus files, critical paratexts, main texts, and supplementary texts (if any). If you have created video landing pages, each one must be listed, which may make your list of related items quite long. (Note that images and videos are not XML files; you do not need to list such media in the


                                             <notesStmt>

To encode your


                                             <notesStmt>

Add a


                                                   <relatedItem>

element for each XML file that you want to publish.

Add a


                                                @target

attribute on the


                                                   <relatedItem>

element.

Give the


                                                @target

attribute a value of "doc:" followed by the filename of the XML file that you wish to include.

For example:

If you list a file in the edition table of contents in the


                                             <text>

element of your edition page and do not also include it in the


                                             <notesStmt>

, you will get an error message reminding you that you must have a


                                             <relatedItem>

element for the file. Although every file mentioned in the


                                             <text>

must have a corresponding


                                             <relatedItem>

element, the converse is not true. You may have many more files in your


                                             <notesStmt>

than you choose to list in your table of contents. You might choose not to list a page in your edition table of contents if you want people to access it by clicking a link on another page (e.g., a list of resources that you want your user to access via a Resources landing page.

Note that if you are publishing your edition in stages (e.g., you are publishing a first version of your edition that includes only the semi-diplomatic transcription, modernized text, collation, and textual notes), you must not list in your


                                             <notesStmt>

files that you do not intend to publish .

Special Case: Include Generated Pages

Remember to include pages that are generated by a processing instruction in an otherwise empty file. Such files include the standalone character list (generated by a roleList instruction) and the standalone manuscript description (generated by a msDesc instruction). These generated pages are usually made by the LEMDO team for you, at your request. The onus is on you and your anthology lead to make sure that such pages are listed in your edition page


                                                <notesStmt>

and listed in your curated table of contents.

For information about LEMDO’s processing instructions, see Inline Processing Instructions in LEMDO.

Practice: Encode the Source Description

The


                                             <sourceDesc>

element has a child

<p>

element. Use this element to describe the source of the XML file for the edition landing page (i.e., the file described in this present document). For an edition landing page created by the LEMDO team on behalf of an editor, the


                                             <sourceDesc>

is as follows:

<sourceDesc>
Edition landing page created by the <orgName ref="org:LEMD1">LEMDO Team</orgName> and curated by <persName ref="pers:PEEE1">[Editor Name]</persName>

</sourceDesc>

The Encoding Description

The


                                          <encodingDesc>

element provides information about how you have encoded and edited your edition. All


                                          <encodingDesc>

elements have a child

<p>

element (which gives information about the encoding guidelines that govern the file, normally the LEMDO Customization and Encoding Guidelines) and a child


                                          <editorialDecl>

element (which, in turn, has a child

<p>

element describing the editorial guidelines that govern the editorial work). For information on how to encode and write your encoding description, see Encode the Encoding Description in Your Metadata. Note that your anthology will provide you with the required format for the text in your edition page’s editorial declaration.

Edition pages’ encoding descriptions also have an additional element not used elsewhere: the project description.

Practice: Encode the Project Description

The child

<p>

element of


                                             <projectDesc>

is an opportunity for the editor to describe the editorial project in narrative form. Anthology leads may prescribe particular wording if they wish. Project descriptions are especially useful for capturing division of labour.

Some examples are:

<projectDesc>
This edition was prepared by <persName ref="pers:MART1">Mathew Martin</persName> and <persName ref="pers:COCK1">Peter Cockett</persName> for the Queen’s Men Editions anthology on the LEMDO platform
</projectDesc>

<projectDesc>
This edition was prepared by <persName ref="pers:SLIG1">Jessica Slights</persName> for the Internet Shakespeare Editions and Broadview Press. It has been remediated by the <orgName ref="org:LEMD1">LEMDO Team</orgName> for republication in the New Internet Shakespeare Editions on the LEMDO platform.
</projectDesc>

<projectDesc>
This edition was prepared by <persName ref="pers:HOWA1">Ashley Howard</persName> for the LEMDO platform.
</projectDesc>

<projectDesc>
This edition of <title level="m">The Merchant of Venice</title> was newly prepared by <persName ref="pers:JENS1">Janelle Jenstad</persName> and <persName ref="pers:WITT1">Stephen Wittek</persName> for the New Internet Shakespeare Editions on the LEMDO platform. Jenstad transcribed and encoded the semi-diplomatic transcriptions. Wittek wrote the critical introductions. The editors prepared the modernized text and collations together.
</projectDesc>

Note that there is terminal punctuation in the


                                             <projectDesc>

The Revision Description

You will track changes in your file using the


                                          <revisionDesc>

element. See Encode the Revision Description for information about how to encode the


                                          <revisionDesc>

Practice: Encode the Content of Your Edition Page

The content of your edition page (everything in the


                                          <body>

element) appears on your edition landing page. It is designed to be maximally flexible so that anthologies have the power to organize their own edition landing pages. The content and order of the


                                          <byline>

elements are entirely at the discretion of the anthology leads. Anthologies are in control of the headers and the order of edition components (using the


                                          <list>


                                          <head>

, and


                                          <item>

elements). You may also add an image anywhere in this section of the file.

Because each anthology has a different format for the content of its edition pages, we cannot include a single example here. We do, however, have templates in our lemdo/data/templates folder for each anthology’s edition pages. You may look at these templates to see sample formats.

Notes

1.This same mechanism allows you to exclude unfinished items, if you and your anthology lead agree to release your edition in stages.↑

Prosopography

Ashley Howard

Ashley Howard took her MA in Medieval and Early Modern Studies at the University of Victoria (2017–2020). During that time, she was a Remediating Editor for LEMDO. For her MA thesis, she prepared the first born-LEMDO edition, a critical edition of Ralph Knevet’s Rhodon and Iris.

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.

Jessica Slights

Jessica Slights is Professor of English in the Department of English & Theatre at Acadia University in Nova Scotia. She writes about and lectures on various aspects of early modern literature and culture, and her work has appeared in Early Modern Literary Studies, English Studies in Canada, Studies in Philology, and Studies in English Literature. She is co-editor, with Paul Yachnin, of Shakespeare and Character: Theory, History, Performance, and Theatrical Persons (Palgrave 2009). Her print edition of Shakespeare’s Othello is available from Broadview Press.

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.

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 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.

Mathew Martin

Dr. Mathew R. Martin is Full Professor at Brock University, Canada. He is the author of Between Theatre and Philosophy (2001), Tragedy and Trauma in the Plays of Christopher Marlowe (2015) and Psychoanalysis and Literary Theory (2023), and co-editor, with his colleague James Allard, of Staging Pain, 1500–1800: Violence and Trauma in British Theatre (2009). For Broadview Press he has edited Christopher Marlowe’s Edward the Second (2010), Jew of Malta (2012), Doctor Faustus: The B-Text (2013) and Tamburlaine the Great Part One and Part Two (2014), and Robert Greene’s Selimus (2022). For Revels Editions he has edited George Peele’s David and Bathsheba (2018) and Marlowe’s The Massacre at Paris (2021). For Queen’s Men Editions he has edited The Famous Victories of Henry V (2016). He has published two articles of textual criticism on the printed texts of Marlowe’s plays: Inferior Readings: The Transmigration of Material in Tamburlaine the Great (Early Theatre 17.2 [December 2014]), and (on the political inflections of the shifts in punctuation in the early editions of the play) Accidents Happen: Roger Barnes’s 1612 Edition of Marlowe’s Edward the Second (Early Theatre 16.1 [June 2013]). His latest editing projects are a double-play Revels edition of Robert Greene’s Friar Bacon and Friar Bungay and John of Bordeaux and a Digital Renaissance Editions edition of Dido, Queen of Carthage.

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.

Peter Cockett

Peter Cockett is an associate professor in the Theatre and Film Studies at McMaster University. He is the general editor (performance), and technical co-ordinating editor of Queen’s Men Editions. He was the stage director for the Shakespeare and the Queen’s Men project (SQM), directing King Leir, The Famous Victories of Henry V, and Friar Bacon and Friar Bungay (2006) and he is the performance editor for our editions of those plays. The process behind those productions is documented in depth on his website Performing the Queen’s Men. Also featured on this site are his PAR productions of Clyomon and Clamydes (2009) and Three Ladies of London (2014). For the PLS, the University of Toronto’s Medieval and Renaissance Players, he has directed the Digby Mary Magdalene (2003) and the double bill of George Peele’s The Old Wives Tale and the Chester Antichrist (2004). He also directed An Experiment in Elizabethan Comedy (2005) for the SQM project and Inside Out: The Persistence of Allegory (2008) in collaboration with Alan Dessen. Peter is a professional actor and director with numerous stage and screen credits. He can be contacted at cockett@mcmaster.ca.

PLACEHOLDER PERSON

Stephen Wittek

Stephen Wittek is Assistant Professor of Literature at Carnegie Mellon University and co-editor with Janelle Jenstad for the ISE edition of The Merchant of Venice. He is the author of The Media Players: Shakespeare, Middleton, Jonson, and the Idea of News (University of Michigan Press, 2015), and has also written for journals including Studies in English Literature, Digital Humanities Quarterly, and Journal of Cognitive History. In 2014, the CBC Radio One program Ideas produced an hour-long episode showcasing Dr. Wittek’s research on the co-evolution of English theatre and news culture (available for streaming or download).

Dr. Wittek holds a PhD in literature from McGill University and a Master’s degree in Shakespeare Studies from the Shakespeare Institute in Stratford-Upon-Avon, England. From 2013 to 2017, he was a Postdoctoral Fellow for McGill’s Early Modern Conversions project, a five-year research endeavor that brought together an interdisciplinary team of humanities scholars to study the multiform proliferation of conversion and conversional representation in early modernity (see http://www.earlymodernconversions.com). His continuing work for the project includes the essay collection Performing Conversion: Urbanism, Theatre, and the Transformation of the Early Modern World, which he is co-editing with José R. Jouve-Martin for the Early Modern Conversions book series (University of Edinburgh Press).

On the digital humanities front, Dr. Wittek is co-developer with Stéfan Sinclair and Matthew Milner for DREaM (Distant Reading Early Modernity), a database that will index 44,000+ early modern texts, thus making long-neglected material more amenable for use with tools for large-scale textual analysis.

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.

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.

PLACEHOLDER ORGANIZATION (OOOO1)

The purpose of this item is to allow encoders to link to an organization when they cannot add a new one to the ORGS1 file for some reason. When linking to this item, please include a comment explaining the details of the item the link should really point to.

University of Victoria (UVIC1)

https://www.uvic.ca/

Metadata

Authority title	Encode Your Edition Page
Type of text	Documentation
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.