Encode Title Page of Semi-Diplomatic Transcriptions

The title page of the playbook you are transcribing goes in the <front> element of your XML file.
If you are working from a converted EEBO-TCP text, correct the transcription as necessary (see the DRE Editorial Guidelines). TCP texts include the <titlePage> element. All the components of the <titlePage> are tagged with the <titlePart> element because our conversion processes cannot read the title page the way you can. You will need to parse the title page and tag the components correctly, using the following content model.
Title pages generally follow this content model, although the order may vary slightly (e.g., with a figure before the byline or an epigraph before the byline):
<!-- ... --> <titlePage>
  <docTitle>
    <titlePart type="main"><!-- title --></titlePart>
    <titlePart type="sub"><!-- subtitle, if any --></titlePart>
    <titlePart type="alt"><!-- alternate title, if any --></titlePart>
    <titlePart type="desc"><!-- description --></titlePart>
  </docTitle>
  <byline><!-- text --></byline>
  <figure>
    <figDesc><!-- description of figure --></figDesc>
  </figure>
  <epigraph><!-- epigraph --></epigraph>
  <docImprint><!-- imprint text --></docImprint>
</titlePage> <!-- ... -->
Use a self-closing <lb> element at the beginning of each line of text. (Do not add <lb> elements for empty lines. We will add padding between the components of the title page when it is rendered.) In general, put the <lb> element before the beginning of a new element.

Practice: Encode the Documentʼs Title

The <docTitle> element contains the full title of the playbook. Titles of playbooks are often long, with extended descriptions of the action of the play and possibly information about performance. Wrap the entire title in the <docTitle> element.
The <docTitle> element must include one or more <titlePart> elements. LEMDO has adopted the TEI recommended values for the @type attribute on <titlePart> : "main" (main title), "sub" (subtitle), "alt" (alternate title), and "desc" (descriptive title). However, there is no one pattern we can impose on early modern title pages, and, at the moment, we do not have plans to process or query the parts of title pages. If we were a project interested primarily in title pages, we would likely identify multiple title page patterns and prescribe encoding models for each one. Our advice to editors: use the values that make the most sense for the parts of the title of your playbook, in consultation with your anthology lead. Our advice to Encoders and Remediators on the LEMDO team: do your best with the knowledge that you have of the play (remembering that title pages double as advertisements for the playbook), ask the editor of the edition (if the editor is still active in the field and available for questions), or ask the Project Director.
Not all title pages will have all four parts. Some titles will have two or more parts that you might want to tag with the same value. For example, you might decide to treat all the parts of the title except the main title as "desc". In other words, there is no requirement to use all four <titlePart> values, nor is there a prohibition against using a value more than once.

Practice: Encode Parts of the Title

Wrap the components of the title in <titlePart> elements. Add a @type attribute to each <titlePart> with one of the following values: "main", "sub", "alt", "desc".
Punctuation is part of the title. Include the punctuation within the text node of <titlePart> .

The Main Title

Tag the main or initial part of the title with the @type value of "main". In most cases, follow the Short Title Catalogue, 2nd edition (or the Database of Early English Playbooks) to determine the extent of the main title.
<!-- ... --> <titlePart type="main">The most excellent<lb/>Historie of the Merchant<lb/>of Venice.</titlePart> <!-- ... -->
<!-- ... --> <titlePart type="main">Of yon knovv not me,<lb/>You know no bodie:</titlePart> <!-- ... -->

Subordinate Titles

General advice: As of 2022-02-18, LEMDO editors and encoders have not used "sub" for a <titlePart> . Generally, early modern title pages seem to offer descriptions and alternate titles more than subtitles. We retain the value but acknowledge that true subtitles are rare. LEMDO welcomes a use case. Please let us know if you are transcribing and/or encoding a title page that has what appears to be a subtitle.

Descriptive Titles

General advice: Use @type value of "desc" for parts of the title that describe the play or indicate where, by whom, or when it was performed. Use multiple <titlePart> elements if there are multiple descriptions (especially if they are separated by white space).
<!-- ... --> <titlePart type="desc">VVith the extreame crueltie of Shylocke the Iewe<lb/>towards the sayd Merchant, in cutting a iust pound<lb/>of his flesh: and the obtayning of Portia<lb/>by the choyse of three<lb/>chests.</titlePart> <!-- ... -->
<titlePart type="desc">As it hath beene diuers times acted by the Lord<lb/>Chamberlaine his Seruants.</titlePart>

Alternate Titles

General advice: Use @type value of "alt" for alternative titles that may follow the main title or the subtitle. The word or is a common beginning for an alternative title.
<titlePart type="alt">Or, <lb/>The troubles of Queene Elizabeth:</titlePart>

Practice: Encode Bylines

The byline on a playbook title page is usually short. Wrap any text that indicates authorship (whether accurate or spurious) in the <byline> element. Include Terminal punctuation inside the <byline> element. Do not tag the names; the LEMDO team will tag names in bylines before we publish your transcription.
<byline>Written by Thomas Dekker.</byline>

Practice: Encode Epigraphs

Some playbooks include an epigraph above or below the byline. The <epigraph> element cannot contain text alone. Wrap the text in an <ab> element and use the milestone <lb> element to capture compositorial line beginnings in the epigraph. Note that although epigraphs are often in a foreign language, they should not include the <foreign> element. LEMDO does not tag foreign languages in semi-diplomatic transcriptions. Instead, simply add a @rendition attribute with a value of "rnd:italic" if the text is in italic font.

Practice: Encode Figures

Figures include fleurons, ruled lines, and printerʼs ornaments. Because LEMDO users will always have access to the digital surrogates of the playbooks, we do not try to reproduce these figures. Instead, use the <figure> element to indicate where a figure occurs, and the <figDesc> element to describe it using the following terms (a LEMDO controlled vocabulary):
Fleuron
Printerʼs ornament
Horizontal rule
If these terms do not adequately capture what appears on your title page, contact lemdo@uvic.ca to discuss the possibility of adding a new term.
Do not put an <lb> element in front of your figure. We do not count figures as lines in LEMDO. At rendering time, LEMDO will add padding before and after figures.
<figure>
  <figDesc>Printerʼs ornament</figDesc>
</figure>

Practice: Encode the Imprint

Use the <docImprint> element to capture all the information on the title page about where, by whom, and when the book was created and made available. Transcribe the entire imprint line within the <docImprint> element and use child <persName> , <pubPlace> , and <docDate> elements to capture specific entitites contained therein and make them processable.
<!-- ... --> <docImprint> AT <pubPlace>LONDON</pubPlace>, <lb/>Printed by <persName>I. R.</persName> for <persname>Thomas Heyes</persname>, <lb/>and are to be sold in <pubPlace>Paules Church-yard, at the <lb/>signe of the Greene Dragon</pubPlace>. <lb/>
  <docDate>1600</docDate>. </docImprint> <!-- ... -->
The LEMDO team will add the printer to the historical prosopography (PROS1) and make a link later so that the final encoding will look as follows:
<!-- ... --> <docImprint> AT <pubPlace>LONDON</pubPlace>, <lb/>Printed by <persName ref="pros:ROBE11">I. R.</persName> for <persName ref="pros:HAYE2">Thomas Heyes</persName>, <lb/>and are to be sold in <pubPlace>Paules Church-yard, at the <lb/>signe of the Greene Dragon</pubPlace>. <lb/>
  <docDate>1600</docDate>. </docImprint> <!-- ... -->

Place of Publication

Use the <pubPlace> element for the city (e.g,. London, Norwich), the location of the publisherʼs shop or stall, and the sign of the shop or stall.
<!-- ... --> <docImprint>AT <pubPlace>LONDON</pubPlace>, <lb/>Printed by I. R. for Thomas Heyes, <lb/>and are to be sold in <pubPlace>Paules Church-yard, at the <lb/>signe of the Greene Dragon</pubPlace>. <lb/>1600. </docImprint> <!-- ... -->

Date of Publication

Use the <docDate> element to tag the date that the playbookʼs title page gives, even if we know that it is not accurate. (E.g., the Pavier quartos are dated 1601 even though we now know they were printed in 1619. We can capture the true date of printing in the document metadata.)
<!-- ... --> <docImprint> AT LONDON, <lb/>Printed by I. R. for Thomas Heyes, <lb/>and are to be sold in Paules Church-yard, at the <lb/>signe of the Greene Dragon. <lb/>
  <docDate>1600</docDate>. </docImprint> <!-- ... -->

Practice: Encode the Names of Printers, Publishers, and Booksellers

Tag the name or initials of printers, publishers, and booksellers with the <persName> element. The TEI does provide a unique element for a publisher (the <publisher> element) but not for a printer. Rather than make a potentially false claim about publication, we have elected to tag the printer simply with the <persName> element. The LEMDO team will add ids for the people named in the imprint line. (If we now know that the people named in the imprint line are not the agents who printed, published, or sold the book, we will be able to capture the correct agents in the documentʼs metadata. LEMDO is interested in the claims made by the title page, whether or not they are correct.)
Note that any punctuation that does not belong to the name is outside the closing tag of the <persName> element.
<!-- ... --> <docImprint>AT LONDON, <lb/>Printed by <persName>I. R.</persName> for <persName>Thomas Heyes</persName>, <lb/>and are to be sold in Paules Church-yard, at the <lb/>signe of the Greene Dragon. <lb/>1600. </docImprint> <!-- ... -->

Example

Below is a full example of an encoded title page:
<!-- ... --> <pb facs="https://archive.org/details/mostexcellenthis00shak/page/n2"/> <titlePage>
  <lb/>
  <titlePart type="main">The mo<g ref="g:longS">s</g>t excellent <lb/>Hi<g ref="g:longS">s</g>torie of the Merchant <lb/>of Venice.</titlePart>
  <lb/>
  <titlePart type="desc">VVith the extreame crueltie of Shylocke the Iewe <lb/>towards the <g ref="g:longS">s</g>ayd Merchant, in cutting a iu<g ref="g:longS">s</g>t pound <lb/>of his fle<g ref="g:longS">s</g>h: and the obtayning of Portia <lb/>by the choy<g ref="g:longS">s</g>e of three <lb/>che<g ref="g:longS">s</g>ts.</titlePart>
  <lb/>
  <titlePart type="desc">As it hath beene diuers times acted by the Lord <lb/>Chamberlaine his Seruants.</titlePart>
  <lb/>
  <byline>Written by William Shake<g ref="g:longS">s</g>peare.</byline>
  <figure>
    <figDesc>Ruled line</figDesc>
  </figure>
  <figure>
    <figDesc>Printerʼs ornament</figDesc>
  </figure>
  <figure>
    <figDesc>Ruled line</figDesc>
  </figure>
  <lb/>
  <docImprint>AT <pubPlace>LONDON</pubPlace>, <lb/>Printed by <persName>I. R.</persName> for <persName>Thomas Heyes</persName>, <lb/>and are to be <g ref="g:longS">s</g>old in <pubPlace>Paules Church-yard, at the <lb/>
    <g ref="g:longS">s</g>igne of the Greene Dragon</pubPlace>. <lb/>
    <docDate>1600</docDate>.</docImprint>
</titlePage> <!-- ... -->

Prosopography

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.

Kate LeBere

Project Manager, 2020–2021. Assistant Project Manager, 2019–2020. Textual Remediator and Encoder, 2019–2021. Kate LeBere completed her BA (Hons.) in History and English at the University of Victoria in 2020. During her degree she published papers in The Corvette (2018), The Albatross (2019), and PLVS VLTRA (2020) and presented at the English Undergraduate Conference (2019), Qualicum History Conference (2020), and the Digital Humanities Summer Institute’s Project Management in the Humanities Conference (2021). While her primary research focus was sixteenth and seventeenth century England, she completed her honours thesis on Soviet ballet during the Russian Cultural Revolution. She is currently a student at the University of British Columbia’s iSchool, working on her masters in library and information science.

Martin Holmes

Martin Holmes has worked as a developer in the UVicʼs Humanities Computing and Media Centre for over two decades, and has been involved with dozens of Digital Humanities projects. He has served on the TEI Technical Council and as Managing Editor of the Journal of the TEI. He took over from Joey Takeda as lead developer on LEMDO in 2020. He is a collaborator on the SSHRC Partnership Grant led by Janelle Jenstad.

Navarra Houldin

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

Nicole Vatcher

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

Rylyn Christensen

Rylyn Christensen is an English major at the University of Victoria.

Thomas Hayes

Variant spelling: Heyes.

Tracey El Hajj

Junior Programmer 2019–2020. Research Associate 2020–2021. Tracey received her PhD from the Department of English at the University of Victoria in the field of Science and Technology Studies. Her research focuses on the algorhythmics of networked communications. She was a 2019–2020 President’s Fellow in Research-Enriched Teaching at UVic, where she taught an advanced course on Artificial Intelligence and Everyday Life. Tracey was also a member of the Map of Early Modern London team, between 2018 and 2021. Between 2020 and 2021, she was a fellow in residence at the Praxis Studio for Comparative Media Studies, where she investigated the relationships between artificial intelligence, creativity, health, and justice. As of July 2021, Tracey has moved into the alt-ac world for a term position, while also teaching in the English Department at the University of Victoria.

Orgography

LEMDO Team (LEMD1)

The LEMDO Team is based at the University of Victoria and normally comprises the project director, the lead developer, project manager, junior developers(s), remediators, encoders, and remediating editors.

Metadata