LEMDO: Chapter 18. Metadata

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

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.

Sponsors.

Funders.

Availability and terms of use.

Source(s).

Encoding practices and editorial procedures.

Document classification.

Publication status.

Revision history.

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.

Chapter Contents

Introduction to Metadata

Metadata Basics

Complete LEMDO Metadata Model: Elements Only

Encode the Title Statement in Your Metadata

Encode Responsibility Statements

Encode Sponsors and Funders in Your Metadata

Encode the Series Statement and Edition Statement in Your Metadata

Encode the Publication Statement in in Your Metadata

License Your Edition and its Component Files

Encode the Source Description in Your Metadata

Encode the Source Description in in Your Metadata

Encode the Encoding Description in Your Metadata

Encode Metadata from External Sources

Encode the Revision Description

Metadata Template for Modernized Texts

Metadata Template for Anthology Pages

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 Facsimiles (Digital Surrogates).

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 Series Statement and Edition Statement in Your Metadata.


                                                <publicationStmt>

: See Encode the Publication Statement in in Your Metadata.


                                                <seriesStmt>

: See Encode the Series Statement and Edition 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>


                                                <textClass>

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>

containing a narrative description of the TEI customization


                                                <editorialDecl>


                                                <tagsDecl>

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.

Encode the Title Statement in Your Metadata

Rationale

Practice

Examples

Encode Responsibility Statements

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:

One giving credit to yourself as editor

One giving yourself credit as copyright holder over editorial content

One giving the University of Victoria credit as copyright holder over the XML and interface

One giving credit to the LEMDO Team for their collective work either encoding or converting and remediating your files

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.

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 what each contributor’s role is. 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.

Special Case: 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.

Special Case: 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:

<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:edt">Editor</resp>
 <persName ref="pers:PEEE1">Editor Name</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 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">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">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>

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.

Practice

We capture this information using the


                                          <sponsor>

and


                                          <funder>

elements inside the


                                          <titleStmt>

(the first child element of the


                                          <profileDesc>

element—see Encode the Title Statement in Your Metadata).

Sponsoring Anthology

The


                                             <sponsor>

element goes after the last


                                             <respStmt>

element inside the


                                             <titleStmt>

. The


                                             <sponsor>

element is an empty element (i.e., it has no content in the text node). 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:

Anthology	Value
Douai Shakespeare Manuscript Project	DOUA1
Digital Restoration Drama	DRDR1
Digital Renaissance Editions	DRE1
Early Modern Dramatic Paratexts	EMDP1
Early Modern England Encyclopedia	EMEE1
Internet Shakespeare Editions	ISE1
MoEML Mayoral Shows	MOMS1
New Internet Shakespeare Editions	NISE1
Queen’s Men Editions	QME1

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

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

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

<funder>Poculi Ludique Societas</funder>

Encode the Series Statement and Edition Statement in Your Metadata

Rationale

Practice: Write the Edition Statement

You will give information about which anthology release your edition was first included in in the


                                          <editionStmt>

element. The


                                          <editionStmt>

element contains a child

<p>

element that must follow LEMDO’s standard format: Released with [Anthology Name] [1.0], where you will 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 MoEML Mayoral Shows 1.0
</editionStmt>

Examples

Encode the Publication Statement in in Your Metadata

Rationale

Practice

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

Examples

License Your Edition and its Component Files

Rationale

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" corresp="anth:qme"/>
 <licence from="2022-10-31" resp="pers:MELN2" corresp="anth:lemdo"/>
 Intellectual copyright in this edition is held by the editor, Kirk Melnikoff. 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:

Encode the Source Description in Your Metadata

Rationale

Practice

Examples

Encode the Source Description in in Your Metadata

Rationale

Practice

Examples

Encode the Encoding Description in Your Metadata

Rationale

Practice

The


                                          <encodingDesc>

element has the following child elements:

<p>


                                                <projectDesc>

, which in turn has a child

<p>

element (only in edition pages).


                                                <editorialDecl>

, which in turn has a child

<p>

element.²

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.

Examples

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

Practice

Metadata Template for Modernized Texts

This file contains a template for the


                                       <teiHeader>

and


                                       <front>

elements of the modernized text of a play.

Sample TEI Header

<teiHeader>
 <fileDesc>
 <titleStmt>
 <title type="main">Authority Title</title>
 <title type="short">Abbreviated Title: M</title>
 <respStmt>
 <resp ref="resp:aut">Author</resp>
 <persName ref="pros:SHAK1">William Shakespeare</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:edt">Editor</resp>
 <persName ref="pers:ABBR1">Editor Name</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:cph">Copyright Holder (editorial content)</resp>
 <persName ref="pers:ABBR1">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>
 <sponsor ref="org:DRE1"/>
 <funder>Social Sciences and Humanities Research Council of Canada</funder>
 </titleStmt>
 <editionStmt>
 Released with [Anthology Name] 1.0
 </editionStmt>
 <publicationStmt>
 <publisher>University of Victoria on the Linked Early Modern Drama Online Platform</publisher>
 <availability>
 <licence from="2023-10-10" resp="pers:ABBR1" corresp="anth:lemdo"/>
 
 </availability>
 </publicationStmt>
 <seriesStmt>
 
 </seriesStmt>
 <sourceDesc>
 
 </sourceDesc>
 </fileDesc>
 <profileDesc>
 <particDesc>
 <listPerson>
 <person>
 <persName>
 <name>Character Name</name>
 <reg>Name used in speech prefixes</reg>
 </persName>
 <note>
 
 </note>
 </person>
 </listPerson>
 </particDesc>
 <textClass>
 <catRef scheme="tax:emdDocumentTypes" target="cat:ldtPrimaryText"/>
 <catRef scheme="tax:emdEditorialTreatments" target="cat:letModernized"/>
 </textClass>
 </profileDesc>
 <encodingDesc>
 Encoded in TEI P5 according to the LEMDO Customization and Encoding Guidelines
 <editorialDecl>
 
 </editorialDecl>
 </encodingDesc>
 <revisionDesc status="IML-TEI_INP">
 <change when="2023-01-12" who="pers:ABBR1" status="IML-TEI_INP">Remediated file.</change>
 <change when="2019-01-24" who="pers:ABBR1" status="prgGenerated">Created TEI from IML file.</change>
 </revisionDesc>
</teiHeader>

Notes

Feel free to ask LEMDO for help by emailing lemdo@uvic.ca (monitored by the Director and the Project Manager) or lemdo@uvic.ca (monitored by the Director, Project Manager, and Remediators).

Metadata Template for Anthology Pages

This file contains a template for the


                                       <teiHeader>

and


                                       <front>

elements of a born-digital file in an anthology.

Sample TEI Header

<teiHeader>
 <fileDesc>
 <titleStmt>
 <title type="main">Authority Title</title>
 <title type="short">Abbreviated Title</title>
 <respStmt>
 <resp ref="resp:aut">Author</resp>
 <persName ref="pers:ABBR1">Author Name</persName>
 </respStmt>
 <respStmt>
 <resp ref="resp:edt_mrk">Conversion and Remediation</resp>
 <orgName ref="org:LEMD1">LEMDO Team</orgName>
 </respStmt>
 <respStmt>
 <resp ref="resp:edt_mrk">Encoder</resp>
 <orgName ref="org:LEMD1">LEMDO Team</orgName>
 </respStmt>
 <sponsor ref="org:QME1">Queen’s Men Editions</sponsor>
 
 <funder>Social Sciences and Humanities Research Council of Canada</funder>
 </titleStmt>
 <editionStmt>
 Released with [Anthology Name] 1.0
 </editionStmt>
 <publicationStmt>
 <publisher>University of Victoria on the Linked Early Modern Drama Online Platform</publisher>
 <availability>
 <licence from="2020-12-30" resp="pers:OSTO1" corresp="anth:qme"/>
 
 
 </availability>
 </publicationStmt>
 <seriesStmt>
 
 </seriesStmt>
 <sourceDesc>
 Written for the LEMDO platform by the QME team.
 
 Originally created in the ISE’s XWiki platform and published on the original and now-staticized QME website. Converted and remediated for the LEMDO Platform and republished in the QME anthology.
 
 Originally created in the ISE’s Shakespeare in Performance (SIP) database and published on the original and now-staticized QME website. Converted and remediated for the LEMDO Platform and republished in the QME anthology.
 </sourceDesc>
 </fileDesc>
 <profileDesc>
 <textClass>
 <catRef scheme="tax:emdDocumentTypes" target="cat:ldtBornDigInfo"/>
 <catRef scheme="tax:emdDocumentTypes" target="cat:edhSourceXWiki"/>
 
 </textClass>
 </profileDesc>
 <encodingDesc>
 Encoded in TEI P5 according to the LEMDO Customization and Encoding Guidelines
 <editorialDecl>
 n/a
 </editorialDecl>
 
 </encodingDesc>
 <revisionDesc status="published">
 <change who="pers:JENS1" when="2020-12-31" status="published">Finalized metadata for inclusion of file in QME anthology. Changed status to published.</change>
 <change who="pers:TAKE1" when="2018-08-02" status="prgGenerated">Converted document.</change>
 
 <change who="org:QME1" notAfter="2018">Content added to XWiki by a member of the QME team or a member of the ISE team acting on behalf of QME. The earlier history of this content is not known.</change>
 
 <change who="org:QME1" notAfter="2018" status="peerReviewed">Original peer-reviewed content added to XWiki by a member of the QME team or a member of the ISE team acting on behalf of QME. The earlier history of this content was not captured in metadata.</change>
 <change who="org:QME1" notAfter="2018">Original content added to XWiki by a member of the QME team or a member of the ISE team acting on behalf of QME. The earlier history of this content was not captured in metadata.</change>
 </revisionDesc>
</teiHeader>

Notes

Feel free to ask LEMDO for help by emailing lemdo@uvic.ca (monitored by the Director and the Project Manager) or lemdo@uvic.ca (monitored by the Director, Project Manager, and Remediators).

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

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

Helen Ostovich

Helen Ostovich, professor emerita of English at McMaster University, is the founder and general editor of Queen’s Men Editions. She is a general editor of The Revels Plays (Manchester University Press); Series Editor of Studies in Performance and Early Modern Drama (Ashgate, now Routledge), and series co-editor of Late Tudor and Stuart Drama (MIP); play-editor of several works by Ben Jonson, in Four Comedies: Ben Jonson (1997); Every Man Out of his Humour (Revels 2001); and The Magnetic Lady (Cambridge 2012). She has also edited the Norton Shakespeare 3 The Merry Wives of Windsor Q1602 and F1623 (2015); The Late Lancashire Witches and A Jovial Crew for Richard Brome Online, revised for a 4-volume set from OUP 2021; The Ball, for the Oxford Complete Works of James Shirley (2021); The Merry Wives of Windsor for Internet Shakespeare Editions, and The Dutch Courtesan (with Erin Julian) for the Complete Works of John Marston, OUP 2022. She has published many articles and book chapters on Jonson, Shakespeare, and others, and several book collections, most recently Magical Transformations of the Early Modern English Stage with Lisa Hopkins (2014), and the equivalent to book website, Performance as Research in Early English Theatre Studies: The Three Ladies of London in Context containing scripts, glossary, almost fifty conference papers edited and updated to essays; video; link to Queen’s Mens Ediitons and YouTube: http://threeladiesoflondon.mcmaster.ca/contexts/index.htm, 2015. Recently, she was guest editor of Strangers and Aliens in London ca 1605, Special Issue on Marston, Early Theatre 23.1 (June 2020). She can be contacted at ostovich@mcmaster.ca.

Janelle Jenstad

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

Joey Takeda

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

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

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.

William Shakespeare

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.

Queen’s Men Editions (QME1)

The Queen’s Men Editions anthology is led by Helen Ostovich, General Editor; Peter Cockett, General Editor (Performance); and Andrew Griffin, General Editor (Text).

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 18. Metadata
Type of text	Documentation
Publisher	Linked Early Modern Drama
Series
Source
Editorial declaration
Edition
Encoding description
Document status	prgGenerated
License/availability