LEMDO: Chapter 20. Metadata

Chapter 20. Metadata

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 Metadata

The documentation in this chapter is for all editors, encoders, remediators, and anthology leads. It will introduce you to the basic format of metadata for all LEMDO files and will guide you through the practice of encoding each section of metadata in your files. Note that each anthology will have metadata templates for each type of file included in their anthology that gives the specific wording for their metadata. Those templates accompany the generalized explanations in this documentation.

What is Metadata?

Metadata is data about your data or object. In a printed book, you will find the metadata on the Cataloguing in Publishing page that follows the title page. Such a page usually includes copyright information, author and publisher details, date of publication, and suggested cataloguing subjects and numbers.

In the LEMDO environment, your data consists of the various pages that make up your edition. Every page has a header that captures the following information about the page:

Title

Contributors

Rationale

Metadata in a LEMDO file serves a number of purposes:

It gives credit where credit is due—to the authors, editors, remediators and encoders, research assistants, peer reviewers or those who arrange for peer review, funders, publishers, and any other contributors to the making of the file.

It licenses the file for reuse in other contexts and prescribes the terms of use.

It contains information that our processing needs in order to render the file appropriately.

It describes the source on which the text contained in the file is based.

It captures important information about how the text in the file has been prepared and the decisions the editor of the file has made.

It indicates the categories to which the file belongs in LEMDO’s classification scheme.

It may capture metadata from a previous version of the file, such as the ISE or TCP metadata.

It keeps a record of the number and types of revisions that have been made to the file.

It indicates whether or not a file is ready to be published, and it indicates in which anthologies it can be included.

Depending on the type of file, it may also contain other information: editorial character lists in the case of modernized texts; descriptions of manuscripts and the hands therein in the case of manuscript; or descriptions of layout and typography in the case of semi-diplomatic transcriptions.

When to Add Metadata

Now: You will want to pay attention to metadata from the very beginning of your encoding process. If you are using one of LEMDO’s templates (see Use LEMDO’s Oxygen Templates), you will find extensive XML comments to guide you in filling out the metadata.

Ongoing: Keep track of your changes regularly. Add information about your source as it comes to light. Capture your editorial decisions when you make them.

Before a Release: Some metadata needs to be added or updated just before a release, such as the


                                          <editionStmt>

indicating the release in which the file is being published. Generally, anthology leads and LEMDO RAs will take care of adding last-minute metadata and ensuring consistency in metadata wording across the anthology.

Learning Outcomes

This chapter is designed to help you better understand and encode the metadata for your edition. By the time you have worked through this chapter, you will:

Be familiar with key metadata elements

Know what pieces of metadata you should update at what point

Be able to update your metadata

Section	Description
Metadata Basics	Learn about key elements that make up your metadata
Complete LEMDO Metadata Model: Elements Only	See a complete list of elements included in a `<teiHeader>`
Encode the Title Statement in Your Metadata	Learn how to encode the title of your document
Encode Responsibility Statements	Learn how to give credit to contributors
Encode Sponsors and Funders in Your Metadata	Learn how to recognize funders in your metadata
Encode the Edition Statement and Series Statement in Your Metadata	Learn how to indicate the anthology and website version that your edition is included in
Encode the Publication Statement in Your Metadata	Learn about how we capture licensing and use information
License Your Edition and its Component Files	Learn how to encode licensing information for your file
Encode the Source Description in Your Metadata	Learn how to describe the source for your files
Encode the Profile Description in Your Metadata	Learn about the profile description, which includes the categories that your files belong to and, in the case of modernized texts, your character list
Encode the Encoding Description in Your Metadata	Learn about the standard text that goes in the encoding description for your files
Encode Metadata from External Sources	Learn about how LEMDO retains metadata from other sources
Encode the Revision Description	Learn how to track the changes that you make in your files

Metadata Basics

Prior Reading

Introduction to Metadata

Where We Store Metadata

All LEMDO XML files except documentation files¹ have a


                                          <teiHeader>

. The purpose of the


                                          <teiHeader>

is to capture all the metadata for the XML file.

For the facsimile collection, which is made up of image files, we capture metadata for each set of facsimiles in a standoff XML file that we store in the lemdo/data/facsimiles folder. The standoff XML file has a


                                          <teiHeader>

containing metadata for the images. See Capture Facscimile Metadata.

For images used in individual editions, you will create a .txt file and save it in the images folder in your edition directory.

The remainder of this chapter addresses the curation of the


                                          <teiHeader>

element in XML files.

General Practice

We recommend using the appropriate LEMDO template when you create new files. (see Use LEMDO’s Oxygen Templates). The templates contain detailed information about how to complete the


                                          <teiHeader>

for that particular document type (primary text, critical paratext, apparatus, and so on).

You will also want to consult with your anthology lead about how to word the content of certain metadata elements. Consistency across the anthology is important.

Parts of the TEI Header

The LEMDO customization requires the following child elements in the


                                          <teiHeader>

. They must appear in the order given here:


                                                <fileDesc>


                                                <profileDesc>


                                                <encodingDesc>


                                                <revisionDesc>

The


                                          <teiHeader>

may also contain an optional child


                                          <xenoData>

data. If


                                          <xenoData>

is included, put it after the


                                          <encodingDesc>

and before the


                                          <revisionDesc>

The File Description

The LEMDO


                                          <fileDesc>

element contains the following child elements:


                                                <titleStmt>

: See Encode the Title Statement in Your Metadata.


                                                <editionStmt>

: Use this element to capture information about the anthology release in which the file is published. See Encode the Edition Statement and Series Statement in Your Metadata.


                                                <publicationStmt>

: See Encode the Publication Statement in Your Metadata.


                                                <seriesStmt>

: See Encode the Edition Statement and Series Statement in Your Metadata.


                                                <sourceDesc>

: See Encode the Source Description in Your Metadata.

Read more about the File Description in the TEI Guidelines.

The Profile Description

The LEMDO


                                          <profileDesc>

contains the following child elements:


                                                <particDesc>

: Only used in modernized texts to capture character lists. See Encode Character Lists in Modernized Texts.


                                                <textClass>

: Used to capture the categories for your file and trigger specific processing. See Encode File Categories for Edition Files and Introduction to LEMDO’s Taxonomies.

Both elements are also described in Encode the Profile Description in Your Metadata.

Read more about the Profile Description in the TEI Guidelines.

The Encoding Description

The LEMDO


                                          <encodingDesc>

contains the following child elements, all of which are described in Encode the Encoding Description in Your Metadata:

<p>

: used to provide a narrative description of the TEI customization.


                                                <editorialDecl>

: used to explain your editorial choices.


                                                <tagsDecl>

: used in semi-diplomatic transcriptions to create file-wide style. See Encode File-Wide Style in Semi-Diplomatic Transcriptions.

Read more about the Encoding Description in the TEI Guidelines.

Non-LEMDO Metadata

Use the optional


                                          <xenoData>

element to capture any non-TEI metadata (e.g., the iseHeader from legacy IML files) or any TEI metadata from earlier projects (e.g., TCP metadata). See Encode Metadata from External Sources.

Read more about the Non-TEI Metadata in the TEI Guidelines.

The Revision Description

The


                                          <revisionDesc>

, described in Encode the Revision Description, contains one or more


                                          <change>

elements.

Read more about the Revision Description in the TEI Guidelines.

Complete LEMDO Metadata Model: Elements Only

This document lists all the metadata elements for a complete


                                       <teiHeader>

. For details on attributes, values, and element contents, see subsequent sections of this chapter.

Other Resources

LEMDO YouTube video: Putting It All Together (Technical)

Encode the Title Statement in Your Metadata

Rationale

LEMDO uses the


                                          <titleStmt>

element to capture the title of a file along with the contributors, funders, and sponsoring anthology for the file. This is where we give credit to the file’s author(s), editors, encoders, and copyright holders.

This documentation will guide you through the basic process of encoding your title statement and will direct you towards more specific documentation pages for each child element of


                                          <titleStmt>

Contents of the Title Statement

While the exact wording and requirements of your title statement will depend on the piece of your edition that you are encoding, the number of contributors to the file, and if you have received funding for your edition, all title statements share the same general structure. Regardless of what type of file you are encoding, your


                                          <titleStmt>

will contain the following child elements:

One


                                                <title>

element: Use the


                                                <title>

element to title the page that you are encoding. Each part of an edition has a different standard naming format; follow the format given in the template for your file to ensure consistency across editions. For information on encoding the


                                                <title>

element, see Encode Titles.

At least four


                                                <respStmt>

elements: Responsibility statements give credit to contributors to the file. You must include


                                             <respStmts>

for:

Yourself as editor or author of a file depending on the part of the edition you are encoding.

The LEMDO team as an encoder of the file.

Yourself as copyright holder of the contents of the file (except in the case of semi-diplomatic transcriptions).

The University of Victoria as the copyright holder of the XML and interface.

You may include additional


                                                <respStmt>

elements for other contributors to the file, including the author of the play in the case of modernized texts and semi-diplomatic transcriptions. For information on encoding the


                                                <respStmt>

element, see Encode Responsibility Statements.

At least one


                                                <sponsor>

element: Use the


                                                <sponsor>

element to indicate the anthology (or anthologies) that commissioned your edition. For information on encoding the


                                                <sponsor>

element, see Encode Sponsors and Funders in Your Metadata.

At least one


                                                <funder>

element: The


                                                <funder>

element acknowledges the funders for your edition. All LEMDO editions must acknowledge the Social Sciences and Humanities Research Council of Canada (SSHRC), which funds the LEMDO project. Also give credit to any additional funders that you may have. For information on encoding the


                                                <funder>

element, see Encode Responsibility Statements.

Template

Your anthology will have specific templates for the metadata of each type of file. Those templates will contain the exact wording required by your anthology and the additional


                                          <respStmt>

and


                                          <funder>

elements that you should include. All anthologies will, however, follow this base template:

<titleStmt>
 <title type="main">Full Title</title>
 <respStmt>
 <resp ref="resp:aut">Author</resp>
 <persName ref="pers:PEEE1">Your Name</persName>
 
 </respStmt>
 <respStmt>
 <resp ref="resp:edt_mrk">Encoder</resp>
 <orgName ref="org:LEMD1">LEMDO Team</orgName>
 </respStmt>
 <respStmt>
 <resp ref="resp:cph">Copyright Holder (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>
 <sponsor ref="org:ANTH1"/>
 <funder>
 <ref target="https://www.sshrc-crsh.gc.ca/">Social Sciences and Humanities Research Council of Canada</ref>
 </funder>
</titleStmt>

Semi-diplomatic transcriptions consistently have a different set of responsibility statements for semi-diplomatic transcriptions. The base template for semi-diplomatic transcriptions is:

<titleStmt>
 <title type="main">Play Title, Quarto 1</title>
 <respStmt>
 <resp ref="resp:aut">Author</resp>
 <persName ref="pros:PRRR1">Author Name</persName>
 
 </respStmt>
 <respStmt>
 <resp ref="resp:trc">Transcriber</resp>
 <persName ref="pers:PEEE1">Transcriber Name</persName>
 
 </respStmt>
 <respStmt>
 <resp ref="resp:edt_mrk">Encoder</resp>
 <persName ref="pers:PEEE1">Encoder Name</persName>
 
 </respStmt>
 <respStmt>
 <resp ref="resp:edt_mrk">Batch Changes and Metadata</resp>
 <orgName ref="org:LEMD1">LEMDO Team</orgName>
 </respStmt>
 <respStmt>
 <resp ref="resp:pfr">Proofreader</resp>
 <persName ref="pers:PEEE1">Proofreader Name</persName>
 
 </respStmt>
 <respStmt>
 <resp ref="resp:vet">Peer Reviewer</resp>
 <persName ref="pers:PEEE1">Editor Name or Other Peer Reviewer</persName>
 
 </respStmt>
 <respStmt>
 <resp ref="resp:cph">Copyright Holder (Content)</resp>
 <persName ref="pers:UVIC1">University of Victoria</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:cph">Copyright Holder (XML and interface)</resp>
 <orgName ref="org:UVIC1">University of Victoria</orgName>
 </respStmt>
 <sponsor ref="org:ANTH1"/>
 <funder>
 <ref target="https://www.sshrc-crsh.gc.ca/">Social Sciences and Humanities Research Council of Canada</ref>
 </funder>
</titleStmt>

Encode Responsibility Statements

Prior Reading

Encode the Title Statement in Your Metadata

Rationale

We give credit to the contributors of each file using a series of responsibility statements. This documentation gives information on the critical practice of giving credit where it is due with the


                                          <respStmt>

element in the metadata of each file.

Practice: Who to Give Credit To

You will encode a series of


                                          <respStmt>

elements in the


                                          <titleStmt>

at the top of each of your files. Each file will contain at least four


                                          <respStmt>

elements giving credit to:

Yourself as editor (or, depending on file type, author, collator, or compiler)

The LEMDO team for their collective work either encoding or converting and remediating your files

Yourself as copyright holder over editorial content

The University of Victoria as copyright holder over the XML and interface

In addition to these four


                                          <respStmt>

elements, you may wish to give credit to other contributors such as research assistants.

In your edition page only, you will also add a


                                          <respStmt>

for each of your anthology leads. If your edition was peer-reviewed by someone that has agreed to be credited publicly, you will also give them a


                                          <respStmt>

in your edition page.

In your edition page, your modernized text, and your semi-diplomatic transcription, you will also add a


                                          <respStmt>

for the author of your text.

Semi-diplomatic transcriptions are a special case. In addition to giving credit to the author of the play, you will add a


                                          <respStmt>

element for:

At least one transcriber

At least one individual encoder

The LEMDO team for batch changes and metadata

The LEMDO team member who proofread the encoding of the semi-diplomatic transcription

Yourself as peer reviewer

The University of Victoria as the copyright holder over the transcription

The University of Victoria as the copyright holder over the XML and interface

Practice

Each


                                          <respStmt>

has two child elements:


                                          <resp>

and one of either


                                          <persName>


                                          <orgName>

. Note that we do not use the


                                          <name>

element.

The


                                          <resp>

element is for stating the role of each contributor. LEMDO generally uses the standard vocabulary from the Library of Congress’s MARC Code List for Relators to define each contributor’s role. For a full list of the roles that we allow in our


                                          <resp>

elements, see Responsibilities Taxonomy. To encode the


                                          <resp>

element:

Add a


                                             @ref

attribute to the


                                                <resp>

element.

For the value of the


                                             @ref

attribute, add a resp: prefix followed by the appropriate value from the


                                                @xml:id

column in the Responsibility Values table.

In the text node of the


                                                <resp>

element, add the contributor’s role. In most cases, this will be the name that corresponds with the responsibility value that you used.

Use the


                                          <persName>

element when giving credit to an individual contributor. To encode the


                                          <persName>

element:

Add a


                                             @ref

attribute to the


                                                <persName>

element.

For the value of the


                                             @ref

attribute, add a pers: prefix if the person is an editorial, encoding, or technical contributor (i.e., editors, anthology leads, RAs, programmers, etc.) or a pros: if the person is a historical figure (i.e., authors, booksellers, publishers, printers, etc.).

After the prefix in the value of the


                                             @ref

attribute, put the contributor’s xml:id. If you are uncertain of their xml:id, check our Personography (for current contributors) or Prosopography (for historical people).

In the text node of the


                                                <persName>

element, add the contributor’s full name.

Use the


                                          <orgName>

element when giving credit to a group or organization. To encode the


                                          <orgName>

element:

Add a


                                             @ref

attribute to the


                                                <orgName>

element.

For the value of the


                                             @ref

attribute, add an org: prefix followed by the group or organization’s xml:id. If you are uncertain of its xml:id, check our Orgography.

Practice: Encode Responsibility Statements for Copyright Holders

LEMDO adds two separate


                                          <respStmt>

elements for copyright holders. The first states the person who retains intellectual rights (licensed under a CC BY-SA NC license) over the text. The second states that the University of Victoria retains intellectual rights over the markup used in the file.

Both


                                          <respStmt>

elements for copyright holders are encoded by putting the


                                       @ref

attribute and resp:cph value on the


                                          <resp>

element. The distinction between the two is made in the text node of the


                                          <resp>

element: for textual copyright holders, add (Content) at the end of the text node; for markup copyright holders, add (XML and interface) at the end of the text node.

Practice: Give Credit to the LEMDO Team

LEMDO credits the LEMDO team as a whole for their work encoding, converting, and remediating files. Because the LEMDO team works on every file that is published, they are credited in each file. To give credit to the LEMDO team:

Add a


                                                <respStmt>

element at the end of your list of responsibility statements.

Give a value of resp:edt_mrk on the


                                             @ref

attribute on the


                                                <resp>

element.

If your file was converted from IML, put Conversion and Remediation in the text node of the


                                                <resp>

element.

If your file was encoded for the first time in TEI (i.e., it was not converted from IML), put Encoder in the text node of the


                                                <resp>

element.

Put an


                                                <orgName>

element after the


                                                <resp>

element.

Give a value of org:LEMD1 on the


                                             @ref

attribute on the


                                                <orgName>

element.

In the text node of the


                                                <orgName>

element, put LEMDO Team.

Examples

The following is an example of a series of responsibility statements in a critical paratext:

<titleStmt>
 <title type="main">Title</title>
 <respStmt>
 <resp ref="resp:aut">Author</resp>
 <persName ref="pers:PEEE1">Author of Critical Paratext</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:cph">Copyright Holder (Content)</resp>
 <persName ref="pers:PEEE1">Editor 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>
</titleStmt>

The following is an example of a series of responsibility statements in a modernized text:

The following is an example of a series of responsibility statements in an edition page:

<titleStmt>
 <title type="main">Title</title>
 <respStmt>
 <resp ref="resp:edt">Editor</resp>
 <persName ref="pers:PEEE1">Editor Name</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:edt_coord">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">Editor 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:vet">Peer Reviewer</resp>
 <persName ref="pers:PEEE1">Peer Reviewer Name</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:edt_mrk">Encoder</resp>
 <orgName ref="org:LEMD1">LEMDO Team</orgName>
 </respStmt>
</titleStmt>

The following is an example of a series of responsibility statements in an edition page:

<titleStmt>
 <title type="main">Title</title>
 <respStmt>
 <resp ref="resp:aut">Author</resp>
 <persName ref="pros:PRRR1">Author Name</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:trc">Transcriber</resp>
 <persName ref="pers:PEEE1">Transcriber Name</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:edt_mrk">Encoder</resp>
 <persName ref="pers:PEEE1">Encoder Name</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:edt_mrk">Batch Changes and Metadata</resp>
 <orgName ref="org:LEMD1">LEMDO Team</orgName>
 </respStmt>
 <respStmt>
 <resp ref="resp:pfr">Proofreader</resp>
 <persName ref="pers:PEEE1">Proofreader Name</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:vet">Peer Reviewer</resp>
 <persName ref="pers:PEEE1">Editor Name or Other Peer Reviewer</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:cph">Copyright Holder (Content)</resp>
 <persName ref="pers:UVIC1">University of Victoria</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:cph">Copyright Holder (XML and interface)</resp>
 <orgName ref="org:UVIC1">University of Victoria</orgName>
 </respStmt>
</titleStmt>

Encode Sponsors and Funders in Your Metadata

Prior Reading

Encode the Title Statement in Your Metadata

Rationale

We need to give credit to the anthology that commissions an edition and arranges for peer review. The work of shepherding an edition through the publication process is significant, as is the subsequent work of peer review. We also need to give credit to any funding agencies, charitable organizations, and donors who supported the work financially or materially (e.g., by making it possible to pay encoders, project managers, and contract programmers; fund performances; and purchase digital scanning services and image rights from libraries). We use the


                                          <sponsor>

and


                                          <funder>

elements to give credit to sponsoring anthologies and funding agencies. This documentation page will guide you through the process of giving credit with the


                                          <sponsor>

and


                                          <funder>

elements.

Practice: Credit Your Sponsoring Anthology

The


                                          <sponsor>

element is a child of the


                                          <titleStmt>

element and must be placed after the last


                                          <respStmt>

. The


                                          <sponsor>

element is an empty element (i.e., it has no content in the text node).

To encode the sponsor anthology for your edition, add a


                                       @ref

attribute to the


                                          <sponsor>

element. Give the


                                       @ref

attribute a value of org: followed by the ID for the anthology that has commissioned your edition and/or peer-reviewed or arranged for peer review of the edition. Anthology IDs are listed in the LEMDO orgography (ORGS1). To see the entirety of ORGS1, click the “Resources” button in the top navigation bar of the LEMDO-dev website and select “Organizations”. Anthology IDs are listed under the heading Editorial Projects Producing Anthologies.

As of 2026-06-17, our current anthology IDs are:

Anthology	Value
Cambridge Edition of the Works of Ben Jonson	CWBJ1
Douai Shakespeare Manuscript Project	DOUA1
Digital Restoration Drama	DRDR1
Digital Renaissance Editions	DRE1
Early Modern Dramatic Paratexts	EMDP1
Early Modern England Encyclopedia	EMEE1
Early Modern Dramatic Paratexts	EMDP1
Internet Shakespeare Editions	ISE1
John Day Project	JDAY1
LEMDO Website	LEMD4
MoEML Mayoral Shows	MOMS1
New Internet Shakespeare Editions	NISE1
Queen’s Men Editions	QME1

Practice

Add a


                                       @ref

attribute with the appropriate value for the anthology that commissions the edition and/or peer-reviewed or arranged for peer review of the edition. Anthologies are listed in the ORGS1 file. Current values for


                                       @ref

are:

In some cases, commissioning and peer-reviewing has been shared by two anthologies. In these cases, you can give two


                                          <sponsor>

elements, one for each anthology. The most common case thus far appears in editions that were begun under the aegis of the Internet Shakespeare Editions and completed under the aegis of the New Internet Shakespeare Editions. It is also possible for an edition to be commissioned by one anthology and peer-reviewed by another; for example, the MoMS Coordinating Editors cannot review their own MoMS editions and have asked DRE to handle peer review.

Funders

The


                                             <funder>

element appears last in the


                                             <titleStmt>

. Unlike the


                                             <sponsor>

element, it does have a text node with content and it does not bear any attributes. There is no limit to the number of


                                             <funder>

elements a file can have.

Every LEMDO file must have a


                                             <funder>

element for the Social Sciences and Humanities Research Council of Canada, whether or not the editor is in Canada. The LEMDO platform has been built with SSHRC funds, and SSHRC funds have supported every aspect of the documenting, converting, remediating, and encoding processes.

Other sources of funding should be recognized using the preferred wording of the institution, donor, funding agency, or grantor.

If you wish, you can wrap the name of the funding source in the


                                             <ref>

element and use a


                                          @target

attribute to point to the URL of the funding source.

Examples

<editionStmt>
<funder>Social Sciences and Humanities Research Council of Canada</funder>
</editionStmt>

<editionStmt>
 <funder>
 <ref target="https://internetshakespeare.uvic.ca/Foyer/makingwaves/friends/index.html">Friends of the ISE</ref>
 </funder>
</editionStmt>

<editionStmt>
<funder>Poculi Ludique Societas</funder>
</editionStmt>

Encode the Edition Statement and Series Statement in Your Metadata

Rationale

LEMDO uses the


                                          <editionStmt>

and


                                          <seriesStmt>

elements to give information about the anthology release that editions are included in. In these elements, we document which LEMDO anthology an edition is published with. In the


                                          <editionStmt>

, we also specify which version (i.e., edition) of the anthology that an edition is being published as part of.

This documentation will guide you through encoding both the edition statement and the series statement in each file of your edition.

Practice: Write the Edition Statement

Give information about which anthology release your edition was first included in in the


                                          <editionStmt>

element. The


                                          <editionStmt>

element is a child of the


                                          <fileDesc>

element and should be placed after the


                                          <titleStmt>

and before the


                                          <publicationStmt>

To encode the edition statement, add a child

<p>

element. The text node of the

<p>

element must follow LEMDO’s standard format: Released with [Anthology Name] [1.0]. Replace [Anthology Name] with the name of your anthology and [1.0] with the version number of the anthology release that your edition will be released with.

For example:

<editionStmt>
Released with Digital Renaissance Editions 2.0
</editionStmt>

Practice: Encode the Series Statement

The


                                          <seriesStmt>

element is a child of the


                                          <fileDesc>

element. It should be placed after the


                                          <publicationStmt>

and before the


                                          <sourceDesc>

To encode the series statement, add a child

<p>

element. Add the full name of the anthology that your edition is being published by in the text node of the

<p>

element.

For example:

<seriesStmt>
Digital Renaissance Editions
</seriesStmt>

Encode the Publication Statement in Your Metadata

Rationale

LEMDO uses the


                                          <publicationStmt>

element to licence editions and provide information about their availability. This documentation will guide you through the basic process of encoding your publication statement and will direct you towards additional documentation for encoding specific child elements of the


                                          <publicationStmt>

element.

Contents of the Publication Statement

While each anthology may determine the exact wording and requirements for their


                                          <publicationStmt>

elements, the basic structure of elements is shared across all LEMDO anthologies and LEMDO has suggested wording that our anthologies typically follow. Regardless of which anthology you are working with, your


                                          <publicationStmt>

will contain the following child elements:

One


                                                <publisher>

element: Use the


                                                <publisher>

element to indicate the institution publishing and hosting your edition.

One


                                                <availability>

element: The


                                                <availability>

element contains child elements that hold information about the licensing that your edition is under:

Two


                                                      <licence>

elements: Use the


                                                      <licence>

element to indicate the publication date after which your edition is licensed, to link copyright over the content of the file to yourself using your xml:id, and to specify each anthology that you are licensing your edition with. One


                                                      <licence>

element will license your edition for your anthology, the other will license your edition for the LEMDO project. For information on encoding the


                                                      <licence>

element, see License Your Edition for Publication.

One or more

<p>

elements: Use the

<p>

element to provide the specific availability information following the wording provided by your anthology. For information about encoding the narrative licensing information for your edition using the

<p>

element, see License Your Edition and its Component Files.

Practice: Encode the Publisher Element

Type the name of the institution hosting your edition directly in the text node of the


                                          <publisher>

element. In most cases, anthologies follow LEMDO’s recommended wording for the publisher element: “University of Victoria on the Linked Early Modern Drama Online Platform”. Do not include terminal punctuation in the


                                          <publisher>

element.

Step-by-Step: Encode the Availability Element

Follow these steps to encode your


                                          <availability>

element:

Add a


                                                <licence>

element with a


                                             @from

value of the expected publication date for your edition, a


                                             @resp

value of pers: followed by your xml:id, and a


                                             @corresp

value of anth: followed by the abbreviation for your anthology given in lowercase letters.

Add a second


                                                <licence>

element with the same


                                             @from

and


                                             @resp

values and a


                                             @corresp

value of anth:lemdo.

Add a

<p>

element. Add the wording required by your anthology to the text node, replacing generic


                                                <persName>

elements with your own name and xml:id.

Examples

The following is the standard template for the


                                          <publicationStmt>

element recommended by LEMDO:

<publicationStmt>
 <publisher>University of Victoria on the Linked Early Modern Drama Online Platform</publisher>
 <availability>
 <licence from="2025-03-10" resp="pers:PEEE1" corresp="anth:anth"/>
 <licence from="2025-03-10" resp="pers:PEEE1" corresp="anth:lemdo"/>
 Intellectual copyright in this edition is held by the editor, . Copyright on the TEI-XML markup is held by the <orgName ref="org:UVIC1">University of Victoria</orgName> on behalf of the <orgName ref="org:LEMD1">LEMDO Team</orgName>. The content and TEI-XML markup in this file are licensed under a <ref target="https://creativecommons.org/licenses/by-nc-nd/4.0/">CC BY-NC_ND 4.0 license</ref>. This file is freely downloadable without permission under the following conditions: (1) credit must be given to the editor, , and LEMDO in any subsequent use of the files and /or data; (2) this availability statement must remain in the file; (3) the content cannot be adapted or repurposed (except for quotations for the purposes of academic review and citation); and (4) commercial uses are not permitted without the knowledge and consent of the editor, , and LEMDO. Neither the content nor the code in this file is licensed for training large language models (LLMs), ingestion into an LLM, or any use in any artificial intelligence applications; such uses are considered to be commercial uses and are strictly prohibited.
 </availability>
</publicationStmt>

Special Case: Encode the Publication Statement for staticSearch

LEMDO uses a staticSearch engine. Each anthology will have a staticSearch file that corresponds to its search page. One of the ways that we give credit to staticSearch is by using the staticSearchGenerator license in the publication statement of our search pages.

Use the following publication statement in your anthology’s search file:

<publicationStmt>
 <publisher>University of Victoria on the Linked Early Modern Drama Online Platform</publisher>
 <availability>
 <licence from="2023-10-31" resp="pers:HOLM1" corresp="anth:qme"/>
 <licence from="2023-10-31" resp="pers:HOLM1" corresp="anth:lemdo"/>
 projectEndings/staticSearch is licensed under a <ref target="https://github.com/projectEndings/staticSearch/blob/dev/LICENSE">Mozilla Public License 2.0</ref> and under a <ref target="https://github.com/projectEndings/staticSearch/blob/dev/license_BSD.txt">BSD license</ref>. 
 </availability>
</publicationStmt>

(Replace qme in the first


                                          <licence>

element with the abbreviation for your anthology.)

Other Resources

LEMDO YouTube video: Putting It All Together (Editorial)

LEMDO YouTube video: Putting It All Together (Technical)

Prior Reading

License Your Edition for Publication

Rationale

The person and/or organization holding the copyright licenses the file to the anthologies in which it will be released. The license information is captured in the


                                          <teiHeader>

along with other file metadata.

Practice

The license belongs in the


                                          <publicationStmt>

, as a child of


                                          <availability>

. The TEI element is


                                          <licence>

(using British spelling).

Examples

Sample license for an edition page:

<publicationStmt>
 <publisher>University of Victoria on the Linked Early Modern Drama Online Platform</publisher>
 <availability>
 <licence from="2022-10-31" resp="pers:MELN2 org:UVIC1" corresp="anth:qme"/>
 <licence from="2022-10-31" resp="pers:MELN2 org:UVIC1" corresp="anth:lemdo"/>
 Intellectual copyright in this edition is held by the editor, Kirk Melnikoff. Technical copyright in the TEI-XML and processing thereof is held by the University of Victoria on behalf of LEMDO. The XML files of the semi-diplomatic transcription and the modernized texts are licensed for reuse under a <ref target="https://creativecommons.org/licenses/by-nc-sa/4.0/">CC BY-NC-SA 4.0 license</ref>, which means that they are freely downloadable without permission under the following conditions: (1) credit must be given to the editor, QME, and LEMDO in any subsequent use of the files and/or data; (2) derivatives (e.g., adapted scripts for performance) must be shared under the same CC BY-NC-SA 4.0 license; and (3) commercial uses are not permitted without the knowledge and consent of QME, the editor, and LEMDO. The critical paratexts are licensed under a <ref target="https://creativecommons.org/licenses/by-nc-nd/4.0/">CC BY-NC_ND 4.0 license</ref>, which means that they are freely downloadable without permission under the following conditions: (1) credit must be given to the editor, QME, and LEMDO in any subsequent use of the files and/or data; (2) the content cannot be adapted or repurposed (except for quotations for the purposes of academic review and citation); and (3) commercial uses are not permitted without the knowledge and consent of QME, the editor, and LEMDO. This license allows for pedagogical use of the critical paratexts in the classroom.
 </availability>
</publicationStmt>

Sample license for a critical paratext:

Sample license for a semi-diplomatic or modernized text:

Other Resources

LEMDO YouTube video: Putting It All Together (Editorial)

LEMDO YouTube video: Putting It All Together (Technical)

Encode the Source Description in Your Metadata

Rationale

LEMDO uses the


                                          <sourceDesc>

element to describe the origin of our files. This documentation will guide you through adding the source description to your files.

Contents of the Source Description

All


                                          <sourceDesc>

elements must have at least one child

<p>

element to provide a narrative description of the origin of the file. All semi-diplomatic transcriptions should have additional

<p>

elements providing information about the source facsimile(s) used.

The


                                          <sourceDesc>

of semi-diplomatic transcriptions of manuscript plays only should also have a child


                                          <msDesc>

element to capture information about the location of the manuscript. For information on encoding the manuscript description, see Describe Source Manuscripts.

Practice

To encode your source description, add the


                                          <sourceDesc>

element as a child of the


                                          <fileDesc>

element. It should be placed after the


                                          <seriesStmt>

or, in files that have a


                                          <notesStmt>

element, after the


                                          <notesStmt>

Add a child

<p>

element to the


                                          <sourceDesc>

. Write the source description in the

<p>

element following the standard format provided by your anthology. In most cases, anthologies follow LEMDO’s suggested wording for this narrative description. The basic wording is:

Born-digital, peer-reviewed prepared by and encoded by the LEMDO Team for publication in the [[Anth]] 1.0 anthology on the LEMDO platform.

Note that there may be minor variations depending on the history of the file, the component of the edition that you are adding the source description to, and the anthology that you are working with.

Special Case: Semi-Diplomatic Transcriptions

Semi-diplomatic transcriptions are unique in that they must credit the source of the copytext in addition to recording the history of the XML file. For semi-diplomatic transcriptions, you must add at least four

<p>

elements as children of the


                                          <sourceDesc>

In the first paragraph, note which edition the transcription is for (e.g., “Quarto 1”, “Folio 1”) and the publication year.

In the second paragraph, type “Source URI:” followed by the URI for the facsimile source wrapped in an


                                                <idno>

element with a


                                             @type

value of URI.

In the third paragraph, type “Facsimile from the” followed by the source library name.

In the final paragraph, provide the source description for the file following your anthology’s recommended wording.

Note that you will add paragraphs containing the source URI and source library name for each additional facsimile that you use in your transcription before the final paragraph.

Examples

The following is a template source description for a modernized text:

<sourceDesc>
Born-digital, peer-reviewed modern text prepared by  and encoded by the <orgName ref="org:LEMD1">LEMDO Team</orgName> for publication in the [[Anth]] 1.0 anthology on the LEMDO platform.
</sourceDesc>

The following is a template source description for a semi-diplomatic transcription:

<sourceDesc>
 Quarto 1, 1600
 Source URI: <idno type="URI">URL to facsimile source goes here</idno>
 
 Facsimile from the 
 Transcription prepared by <persName ref="pers:PEEE1">Name Here</persName>. First published in the DRE 1.0 anthology on the ISE platform. Converted to TEI-XML and remediated by the <orgName ref="org:LEMD1">LEMDO Team</orgName> for republication in the DRE 2.0 anthology on the LEMDO platform.
</sourceDesc>

Other Resources

LEMDO YouTube video: Putting It All Together (Technical)

Encode the Profile Description in Your Metadata

Rationale

LEMDO uses the


                                          <profileDesc>

element to specify the categories for each file and to add character lists to modernized texts. This documentation will describe the basic structure of the


                                          <profileDesc>

element and will direct you towards specific documentation for encoding each component of the profile description.

Contents of the Profile Description

The profile description for all files must include a child


                                          <textClass>

element. Use the


                                          <textClass>

element to specify the categories for your file. These categories are necessary to trigger processing specific to each file type. For more information about encoding the categories for your files, see Introduction to LEMDO’s Taxonomies.

In addition to the


                                          <textClass>

element, profile descriptions for modernized texts should include a


                                          <particDesc>

element in which you encode your character list. For information on encoding the


                                          <particDesc>

element and the character list for your modernized text, see Encode Character Lists in Modernized Texts.

Other Resources

LEMDO YouTube video: Literary Divisions (Editorial-Technical)

Encode the Encoding Description in Your Metadata

Rationale

LEMDO uses the


                                          <encodingDesc>

element to describe the encoding and editorial standards and decisions used in the preparation of each file. In most cases, there is standard wording for each component of the encoding description. This documentation will guide you through the process of encoding and adding content to each part of the encoding description.

Contents of the Encoding Description

All encoding descriptions should contain two child elements:

One

<p>

element: Use the

<p>

element to specify the encoding practices that you follow in the file.

One


                                                <editorialDecl>

element: The


                                                <editorialDecl>

element must contain a child

<p>

element in which you describe the editorial guidelines that you follow and any significant additional editorial decisions that you made while preparing the file for publication.²

In addition to the

<p>

and


                                          <editorialDecl>

elements, there are two elements that are part of the encoding description of certain types of files.

In your edition page: Add a


                                                <projectDesc>

element before the


                                                <editorialDecl>

element to describe the anthology that your edition is being published with and the editorial guidelines that you followed across your edition. See Practice: Encode the Project Description in Encode Your Edition Page.

In your semi-diplomatic transcription: You may add a


                                                <tagsDecl>

element to add file-wide style. See Encode File-Wide Style in Semi-Diplomatic Transcriptions.

Practice: Add a Narrative Statement for Your Encoding Practice

The child

<p>

element of


                                          <encodingDesc>

is a narrative statement that the file has been encoded according to LEMDO’s encoding guidelines. It is always as follows:

<encodingDesc>
Encoded in TEI P5 according to the LEMDO Customization and Encoding Guidelines
</encodingDesc>

Note that there is no terminal punctuation.

Practice: Add Your Editorial Declaration

Your anthology will have specific wording for the child

<p>

element in your editorial declaration. In most cases, anthologies follow LEMDO’s recommended wording. For edition pages, modernized texts, and apparatus files, the recommended wording is:

<encodingDesc>
 <editorialDecl>
 Edited according to the <title level="m">DRE Editorial Guidelines</title> using Canadian English spelling
 </editorialDecl>
</encodingDesc>

For critical paratexts, the recommended wording is simply:

<encodingDesc>
 <editorialDecl>
 Canadian English spelling
 </editorialDecl>
</encodingDesc>

Special Case: Encode the Encoding Description in Your Semi-Diplomatic Transcription

LEMDO uses different wording for the encoding description of semi-diplomatic transcriptions so that all style and encoding decisions are captured in each published file. Providing a detailed encoding description for semi-diplomatic transcriptions allows us to apply style across all semi-diplomatic transcriptions while still aligning with the Endings Principles for Digital Longevity.

For information on the specific required wording for the encoding description and editorial declaration in semi-diplomatic transcriptions, see Introduction to Style in Semi-Diplomatic Transcriptions.

Examples

The following is the base template for the encoding description for modernized texts and apparatus files:

<encodingDesc>
 Encoded in TEI P5 according to the LEMDO Customization and Encoding Guidelines
 <editorialDecl>
 Edited according to the <title level="m">DRE Editorial Guidelines</title> using Canadian English spelling
 </editorialDecl>
</encodingDesc>

The following is the base template for the encoding description for critical paratexts:

<encodingDesc>
 Encoded in TEI P5 according to the LEMDO Customization and Encoding Guidelines
 <editorialDecl>
 Canadian English spelling
 </editorialDecl>
</encodingDesc>

The following is the base template for the encoding description for edition pages:

<encodingDesc>
 Encoded in TEI P5 according to the LEMDO Customization and Encoding Guidelines
 <projectDesc>
 This edition was prepared by <persName ref="pers:PEEE1">Editor Name</persName> for the [[Anthology Name]] anthology on the LEMDO platform
 </projectDesc>
 <editorialDecl>
 This edition was edited according to the <title level="m">DRE Editorial Guidelines</title> using Canadian English spelling
 </editorialDecl>
</encodingDesc>

The following is the base template for the encoding description for semi-diplomatic transcriptions:

<encodingDesc>
 Encoded in TEI P5 according to the LEMDO Customization and Encoding Guidelines. The encoding makes the following assumptions (rendered via the _semi-dip.scss file): text is aligned left and set in Roman type unless otherwise specified; titlepage components and running titles are centered; signatures are centered and letterspaced; running titles are centered and set in italic type; catchwords are aligned right; speech prefixes are indented and set in italic type; and stage directions are set in italic type and aligned left unless the stage element has a place attribute. Where this playbook differs generally from LEMDOʼs default assumptions, the TEI Header includes one or more tagsDecl elements describing this playbookʼs particular imposition and composition. Where this playbook contains local deviations from its own general patterns, the encoding includes element-level and inline CSS to describe the playbookʼs unique features.
 <editorialDecl>
 This semi-diplomatic text was originally prepared according to the <title level="m">ISE Editorial Guidelines</title>. It has been fully remediated and proofread by the LEMDO team to comply with the <title level="m">DRE Editorial Guidelines</title> and the <title level="m">LEMDO Encoding Guidelines</title>, with the following exceptions: long s and ligatures have been transcribed or encoded, in keeping with the <title level="m">ISE Editorial Guidelines</title>.
 
 </editorialDecl>
 <editorialDecl>
 This semi-diplomatic text has been prepared according to the <title level="m">DRE Editorial Guidelines</title> and the <title level="m">LEMDO Encoding Guidelines</title>.
 </editorialDecl>
 
 <tagsDecl>
 <rendition selector="label" scheme="css"> font-style: italic; </rendition>
 </tagsDecl>
</encodingDesc>

Other Resources

LEMDO YouTube video: Semi-Diplomatic Transcriptions (Technical)

LEMDO YouTube video: Putting It All Together (Technical)

Encode Metadata from External Sources

Rationale

Many LEMDO files come from external sources and already contain metadata. On principle, LEMDO is committed to preserving the metadata of our sources and ensuring that it travels with the LEMDO files and remains available to future users of our XML. Rather than try to convert that metadata to LEMDO’s customization of TEI P5, we preserve the original metadata in its entirety in a special element in the


                                          <teiHeader>

Common Scenarios

Legacy ISE, QME, and DRE files were originally published on the ISE platform. Until 2014, the metadata for those files was captured at the top of the file in an <iseHeader> element; after 2014, the metadata was captured in a stand-off file. The LEMDO Director has copies of the metadata as it stood in 2014 and 2018. Remediators will need to add this metadata to LEMDO files.

Texts converted from the Text Creation Partnership XML files have TCP metadata. When we convert GitHub files to LEMDO’s customization of TEI P5, we retain the metadata. Remediators will need to move this metadata into the


                                          <xenoData>

element.

Practice

TEI provides a


                                          <xenoData>

element for external metadata. In our customization, the


                                          <xenoData>

element goes after the


                                          <encodingDesc>

and before the


                                          <revisionDesc>

The first child element of


                                          <xenoData>

must be a root element for the metadata. The element must have the


                                       @xmlns

attribute with the URL that indicates a namespace.

For files first published on the ISE platform, the root element is iseHeader. For legacy ISE, DRE, and QME files, the namespace is https://internetshakespeare.uvic.ca.

For files converted from TCP, the root element is


                                          <publicationStmt>

. Even though TCP files are encoded in TEI, we use the URL https://textcreationpartnership.org/ for the value of the


                                       @xmlns

attribute.

Note that a file can have multiple


                                          <xenoData>

elements if it has a complex history. As LEMDO remediates files from other projects, we will add new examples to this documentation.

Examples

<xenoData>
 <publicationStmt>
 <publisher>Text Creation Partnership,</publisher>
 <pubPlace>Ann Arbor, MI ; Oxford (UK) :</pubPlace>
 <date when="2003-01">2003-01 (EEBO-TCP Phase 1).</date>
 <idno type="TCP">A07859</idno>
 <idno type="STC">STC 18230</idno>
 <idno type="STC">ESTC S106305</idno>
 <idno type="EEBO-CITATION">99842023</idno>
 <idno type="PROQUEST">99842023</idno>
 <idno type="EEBO-VID">6646</idno>
</publicationStmt>
</xenoData>

Encode the Revision Description

Rationale

LEMDO uses the


                                          <revisionDesc>

to record the progress of a file and significant milestones towards publication. This documentation will guide you through the basic model for the revision description and will point you towards specific documentation pages for each component of the revision description.

Contents of the Revision Description

All


                                          <revisionDesc>

elements should have a


                                       @status

attribute that indicates the current status of the file. The value of the


                                       @status

attribute will change with each significant milestone towards publication (e.g., when there is a complete draft of the file, when the file has been proofread, when the file is published). For information on encoding the status of a file, see Encode Document Status.

All


                                          <revisionDesc>

elements must have at least one child


                                          <change>

element. The


                                          <change>

elements must be given in reverse chronological order; the most recent changes are given at the top of the list while the earliest changes to the file are given at the bottom. A


                                          <change>

element is added every time that someone begins work on a file, when they finish work on the file, when encoding or editorial milestones are reached, and when the LEMDO team does work on the file. For information about adding


                                          <change>

elements, see Track Your Work.

Notes

1.Individual documentation files are rooted on the


                                    <div>

element and combined into a single documentation file via a table of contents in our ODD file. The metadata for the documentation is contained in the


                                    <teiHeader>

of the ODD file. See Give Credit for Documentation Files for information on how we give credit to contributors to LEMDO documentation.↑

2.LEMDO Director Janelle Jenstad observes that this feature of the TEI metadata model is illogical. She has put in a feature request to the TEI asking that the


                                    <editorialDecl>

not be a child of


                                    <encodingDesc>

, on the grounds that encoding practice and editorial approach are distinct.↑

Prosopography

Illya

Illya has a BA in English and Sociocultural Anthropology and an MA in English. Prior to joining the HCMC, he was a PhD candidate in English and Book History at the University of Toronto and worked on Records of Early English Drama and on the Modernist Archives Publishing Project. His work at the HCMC focuses on creating web-based applications for research projects led by members of the faculty of Humanities at the University of Victoria. This involves creating schemas for new and existing datasets, writing XSLT and build files to transform datasets into structured TEI and HTML formats, implementing staticSearch, and ensuring that new projects are Endings Principles compliant.

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

Kirk Melnikoff

Kirk Melnikoff is Professor of English at UNC Charlotte and a past president of the Marlowe Society of America. His research interests range from sixteenth-century British Literature and Culture, to Shakespeare in Performance, to Book History. His essays have appeared in a number of journals and books, and he is the author of Elizabethan Book Trade Publishing and the Makings of Literary Culture (U Toronto P, 2018). He has also edited four essay collections, most recently Christopher Marlowe, Theatrical Commerce, and the Book Trade (Cambridge UP, 2018), and published an edition of Robert Greene’s James IV in 2020. He is currently co-editing a collection of early modern book-trade wills which will be published by Manchester UP, editing Marlowe’s Edward II for the Oxford Marlowe: Collected Works project, and working on a monograph on bookselling in early modern England.

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.

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.

PLACEHOLDER HISTORICAL PERSON

PLACEHOLDER PERSON

Samuel Seaberg

Samuel Seaberg, a University of Victoria English undergrad, enjoys riding his bike. During the summer of 2025, he began working with LEMDO as a recipient of the Valerie Kuehne Undergraduate Research Award (VKURA). Unfortunately, due to his summer being spent primarily in working to establish an edition of Thomas Heywood’s If You Know Not Me, You Know Nobody, Part 2 and consequently working out how to represent multi-text works in a digital space, his bike has suffered severely of sheltered seclusion from the sun. Note: Samuel now works for LEMDO as the Assistant Project Manager, much to his bike’s chagrin.

Si Micari-Lawless

Si Micari-Lawless is a research assistant with LEMDO and MoEML, and an incoming fourth-year English major at the University of Victoria.

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

Digital Renaissance Editions (DRE1)

Anthology Leads and Co-Coordinating Editors: Brett Greatley-Hirsch, Janelle Jenstad, James Mardock, and Sarah Neville.

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.

MoEML Mayoral Shows (MOMS1)

Anthology Leads and General Editors: Mark Kaethler and Janelle Jenstad. The team includes SSHRC-funded research assistants. Peer review is coordinated by the General Editors but conducted by other editors and external scholars.

University of Victoria (UVIC1)

https://www.uvic.ca/

Glossary

empty element

“Empty elements are also called milestone or self-closing elements, but LEMDO uses the term empty element. Empty elements do not have child text or element nodes.”

Metadata

Authority title	Chapter 20. Metadata
Type of text	Documentation
Publisher	Linked Early Modern Drama
Series
Source
Editorial declaration
Edition
Encoding description
Document status	prgGenerated
License/availability

Chapter 20. Metadata

Introduction to Metadata

What is Metadata?

Rationale

When to Add Metadata

Learning Outcomes

Contents

Metadata Basics

Prior Reading

Where We Store Metadata

General Practice

Parts of the TEI Header

The File Description

The Profile Description

The Encoding Description

Non-LEMDO Metadata

The Revision Description

Complete LEMDO Metadata Model: Elements Only

Other Resources

Encode the Title Statement in Your Metadata

Rationale

Contents of the Title Statement

Template

Encode Responsibility Statements

Prior Reading

Rationale

Practice: Who to Give Credit To

Practice

Practice: Encode Responsibility Statements for Copyright Holders

Practice: Give Credit to the LEMDO Team

Examples

Encode Sponsors and Funders in Your Metadata

Prior Reading

Rationale

Practice: Credit Your Sponsoring Anthology

Practice

Funders

Examples

Encode the Edition Statement and Series Statement in Your Metadata

Rationale

Practice: Write the Edition Statement

Practice: Encode the Series Statement

Encode the Publication Statement in Your Metadata

Rationale

Contents of the Publication Statement

Practice: Encode the Publisher Element

Step-by-Step: Encode the Availability Element

Examples

Special Case: Encode the Publication Statement for staticSearch

Other Resources

Further Reading

License Your Edition and its Component Files

Prior Reading

Rationale

Practice

Examples

Other Resources

Further Reading

Encode the Source Description in Your Metadata

Rationale

Contents of the Source Description

Practice

Special Case: Semi-Diplomatic Transcriptions

Examples

Other Resources

Encode the Profile Description in Your Metadata

Rationale

Contents of the Profile Description

Other Resources

Encode the Encoding Description in Your Metadata

Rationale

Contents of the Encoding Description

Practice: Add a Narrative Statement for Your Encoding Practice

Practice: Add Your Editorial Declaration

Special Case: Encode the Encoding Description in Your Semi-Diplomatic Transcription

Examples

Other Resources

Encode Metadata from External Sources

Rationale

Common Scenarios