LEMDO: Chapter 5. Entities and Databases

Chapter 5. Entities and Databases

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 Sitewide Data Files

LEMDO has a number of shared databases that serve all of the anthologies. LEMDO maintains these databases on behalf of editors and anthology leads. The documentation in this chapter is therefore mainly for the internal use of the LEMDO team members who add entities to these databases. If editors and anthology leads wish to add entities, send them to lemdotech@uvic.ca.

The sitewide databases are as follows:

DB Name and Documentation Link	Purpose	Abbreviation
Personography	List of all contributors (editors, RAs, anthology leads, board members, developers, designers, directors, actors in PAR productions)	PERS1
Prosopography	List of all historical persons (authors, printers, publishers)	PROS1
Orgography	List of all organizations (universities, libraries, museums, LEMDO anthologies)	ORGS1
Bibliography	List of all primary and secondary sources (except editions)	BIBL1
Production Database	List of all productions cited in editions and anthologies	PROD1
Handography	List of all manuscript hands identified in manuscript plays	HAND1
Glossary	List of technical terms	GLOSS1

This chapter also contains documentation on placeholder entities. If you want to tag a person who is not yet in PERS1, for example, you may use a placeholder entity.

¶ Personography (PERS1)

¶ Introduction

The Personography is a sitewide database file in the data directory of the Subversion repository. It contains the xml:ids and biographies of LEMDO contributors, editors, and research assistants. Since many people occasionally edit PERS1.xml, make sure no one else is working in the file before you make any changes. If you are in HCMC, talk to the other LEMDO team members. If you are not in the lab, send an email to all repository users with the subject Working in PERS1. When you have finished, validated, and committed your work, send out another email with the subject Finished working in PERS1.

If you are unable to add an entry to PERS1.xml when you need to, you can link instead to the placeholder entry PEEE1, and then come back to it later. When linking to the placeholder, make sure you include an XML comment with full details of what needs to be done. For more information on placeholder entries, see Placeholder Entities.

¶ Structure

PERS1.xml is structured as follows:

¶ Create a PERS1 entry

Here is an example of a PERS1 entry:

<person xml:id="LEBE1">
  <persName>
    <reg>Kate LeBere</reg>
    <forename>Kate</forename>
    <surname>LeBere</surname>
    <abbr>KL</abbr>
  </persName>
  <note>
    <p>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 <title level="j">The Corvette</title> (2018), <title level="j">The Albatross</title> (2019), and <title level="j">PLVS VLTRA</title> (2020) and presented at the English Undergraduate Conference (2019) and Qualicum History Conference (2020). 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.</p>
  </note>
</person>

We will break down this entry below.

¶ Encode the Root Element

The


                                             <person>

element is the root of every Personography entry. It requires a unique xml:id, so that references in other documents to people may be tagged with that unique xml:id and links be made to the information in the Personography file. The value of the


                                          @xml:id

should be comprised of a unique four digit and one letter identifier. Ctrl+F the A–Z Index text file on the lemdo-dev site (available from the Resources menu) to find the next unused ID.

<person xml:id="LEBE1"/>

Nested within the


                                             <person>

element should be the following second-tier elements:


                                             <persName>

and


                                             <note>

. The following sections describe how to encode these elements.

¶ Encode Names

Nest a


                                             <persName>

element inside the


                                             <person>

element. We use the


                                             <persName>

element to tag the various names (forename, surname, etc.) associated with a person. Nest a


                                             <name>

element within the


                                             <persName>

element. There are four name element that you can use when encoding a person’s name:


                                             <reg>


                                             <forename>


                                             <surname>

, and


                                             <abbr>

<person>
  <persName>
    <reg/>
    <forename/>
    <surname/>
    <abbr/>
  </persName>
</person>

Use the


                                             <reg>

element to tag a regularized version of the person’s name. In most instances, the regularized version will be the person’s forename followed by their surname. Do not include titles in a personʼs


                                             <reg>

name (i.e., Dr.):

<persName>
<reg>Kate LeBere</reg>
</persName>

Use the


                                             <forename>

element to tag a person’s forename or given name. Sometimes, a person will have more than one forename (i.e., they will have a middle name or middle names). We tag every such name separately using the


                                             <forename>

element:

<persName>
<reg>Kate LeBere</reg>
<forename>Kate</forename>
</persName>

Use the


                                             <surname>

element to tag a person’s surname or family name. Sometimes, a person will have more than one surname (e.g., they got married and changed their surname). We tag every such name separately using the


                                             <surname>

element:

<persName>
  <reg>Kate LeBere</reg>
  <forename>Kate</forename>
  <surname>LeBere</surname>
</persName>

After


                                             <surname>

, you may use the


                                             <abbr>

element to tag the contributor’s initials:

<persName>
  <reg>Kate LeBere</reg>
  <forename>Kate</forename>
  <surname>LeBere</surname>
  <abbr>KL</abbr>
</persName>

¶ Encode Biographical Notes

Nest a


                                             <note>

element inside the


                                             <person>

element. We use the


                                             <note>

element to contain the biographical statement. Contributors write their own biographical statements. Content within biographical statements are encoded according to our general encoding guidelines (e.g., titles of books and journal articles are tagged with the


                                             <title>

element). Links to open-source articles are also permitted.

<person>
<persName/>
<note/>
</person>

For members of the LEMDO team, entries will need to be updated regularly. When a team member leaves, their biographical statement can either be changed into the past tense or can be edited to explain where the team member is now. Sometimes, a team member will have held multiple roles at LEMDO. If they have had multiple roles over the course of months or years, list each role chronologically (including corresponding dates) at the beginning of their biographical statement:

<note>
<p>Project Manager, 2020-2021. Assistant Project Manager, 2019-2020. Textual Remediator and Encoder, 2019-2021.</p>
</note>

¶ Link to a PERS1 Entry

For instructions on how to link to Personography entries within a document, refer to our instructions on encoding entities.

¶ Prosopography (PROS1)

¶ Introduction

The Prosopography is a sitewide database file in the data directory of the Subversion repository. It contains the xml:ids of historical people. Since many people occasionally edit PROS1.xml, make sure no one else is working in the file before you make any changes. If you are in HCMC, talk to the other LEMDO team members. If you are not in the lab, send an email to all repository users with the subject Working in PROS1. When you have finished, validated, and committed your work, send out another email with the subject Finished working in PROS1.

If you are unable to add an entry to PROS1.xml when you need to, you can link instead to the placeholder entry PRRR1, and then come back to it later. When linking to the placeholder, make sure you include an XML comment with full details of what needs to be done. For more information on placeholder entries, see Placeholder Entities.

¶ Structure

PROS1.xml is structured as follows:

¶ Create a PROS1 entry

Here is an example of a PROS1 entry:

<person xml:id="SHAK1">
  <persName>
    <reg>William Shakespeare</reg>
    <forename>William</forename>
    <surname>Shakespeare</surname>
  </persName>
</person>

We will break down this entry below.

¶ Encode the Root Element

The


                                             <person>

element is the root of every Prosopography entry. It requires a unique xml:id so that references in other documents to people may be tagged with that unique xml:id and links be made to the information in the Prosopography file. The value of the


                                          @xml:id

should be comprised of a unique four digit and one letter identifier. Search the A–Z Index on the lemdo-dev site using Ctrl + F the A–Z Index text file on the lemdo-dev site (available from the Resources menu) to find the next unused ID.

<person xml:id="SHAK1"/>

Nested within the


                                             <person>

element should be the


                                             <persName>

element. The following section describes how to encode this element.

¶ Encode Names

Nest a


                                             <persName>

element inside the


                                             <person>

element. We use the


                                             <persName>

element to tag the various names (forename, surname, etc.) associated with a person. Nest a


                                             <name>

element within the


                                             <persName>

element. There are four name elements that you can use when encoding a person’s name:


                                             <reg>


                                             <forename>


                                             <surname>

, and


                                             <addName>

<person>
  <persName>
    <reg/>
    <forename/>
    <surname/>
    <addName/>
  </persName>
</person>

Use the


                                             <reg>

element to tag a regularized version of the person’s name. In most instances, the regularized version will be the person’s forename followed by their surname. Do not include titles in a personʼs


                                             <reg>

name (e.g., Mr.):

<persName>
<reg>William Shakespeare</reg>
</persName>

Use the


                                             <forename>


                                             <forename>

element:

<persName>
<reg>William Shakespeare</reg>
<forename>William</forename>
</persName>

Use the


                                             <surname>

element to tag a person’s surname or family name. Sometimes, a person will have more than one surname (e.g., they got married and changed their surname). We tag every such name separately using the


                                             <surname>

element:

<persName>
  <reg>William Shakespeare</reg>
  <forename>William</forename>
  <surname>Shakespeare</surname>
</persName>

Use the


                                             <addName>

element to tag any aliases, nicknames, or epithets associated with a person’s name. The


                                             <addName>

element is not used for variant spellings of a person’s name or location-based indicators (e.g., of Norwich or of France):

<persName>
  <reg>Alfred the Great</reg>
  <forename>Alfred</forename>
  <addName>the Great</addName>
</persName>

¶ Link to a PROS1 Entry

For instructions on how to link to Prosopography entries within a document, see our instructions on encoding entities.

¶ Orgography (ORGS1)

¶ Introduction

The Orgography is a sitewide database file in the data directory of the Subversion repository. It contains the xml:ids of organizations. Since many people occasionally edit ORGS1.xml, make sure no one else is working in the file before you make any changes. If you are in HCMC, talk to the other LEMDO team members. If you are not in the lab, send an email to all repository users with the subject Working in ORGS1. When you have finished, validated, and committed your work, send out another email with the subject Finished working in ORGS1.

If you are unable to add an entry to ORGS1.xml when you need to, you can link instead to the placeholder entry OOOO1, and then come back to it later. When linking to the placeholder, make sure you include an XML comment with full details of what needs to be done. For more information on placeholder entries, see Placeholder Entities.

¶ Structure

ORGS1.xml is structured as follows:

<TEI version="5.0" xml:id="ORGS1">
  <teiHeader></teiHeader>
  <text>
    <body>
      <div>
        <listOrg>
          <head>LEMDO Organizations</head>
          <org></org>
        </listOrg>
        <listOrg>
          <head>Universities and Libraries</head>
          <org></org>
        </listOrg>
        <listOrg>
          <head>Funders and Supporters</head>
          <org></org>
        </listOrg>
        <listOrg>
          <head>Theater Companies</head>
          <org></org>
        </listOrg>
        <listOrg>
          <head>Boards</head>
          <org></org>
        </listOrg>
        <listOrg>
          <head>Editorial Projects Producing Anthologies</head>
          <org></org>
        </listOrg>
        <listOrg>
          <head>Early Modern Institutions, Companies, and Organizations</head>
          <org></org>
        </listOrg>
        <listOrg>
          <head>Placeholder/testing</head>
          <org></org>
        </listOrg>
      </div>
    </body>
  </text>
</TEI>

Below is a brief description of each of the Orgographyʼs sections.

¶ ORGS1 Sections

Section	Purpose
LEMDO Organizations	Groups that apply for grant funding on behalf of LEMDO; the team at UVic; the editorial and advisory boards for LEMDO.
Universities and Libraries	Institutions that have partnered with UVic on grant applications; institutions that have donated resources; universities and libraries that have shared facsimiles with LEMDO. Note that we often need an entry for the institution and for the library at that institution.
Funders and Supporters	Funding agencies; campus offices and units providing support; individual donors.
Theatre Companies	Theatre companies that have partnered with LEMDO or provided materials for editions.
Boards	Editorial and Advisory Boards of the anthologies.
Editorial Projects Producing Anthologies	The abstract concept of the project that produces that the anthology output. QME is the `<org>` behind the QME anthology.

¶ Create a ORGS1 entry

Here is an example of a ORGS1 entry:

<org xml:id="LEMD1">
  <orgName>
    <reg>LEMDO Team</reg>
  </orgName>
  <note>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.</note>
</org>

We will break down this entry below.

¶ Encode the Root Element

The


                                             <org>

element is the root of every Orgography entry. It requires a unique xml:id, so that references in other documents to people may be tagged with that unique xml:id and links be made to the information in the Orgography file. The value of the


                                          @xml:id

should be comprised of a unique four digit and one letter identifier. Ctrl+F the A–Z Index text file on the lemdo-dev site (available from the Resources menu) to find the next unused ID.

<org xml:id="LEMD1"/>

Nested within the


                                             <org>

element should be the


                                             <orgName>

element. The following section describes how to encode this element.

¶ Encode Names

Nest a


                                             <orgName>

element inside the


                                             <org>

element and nest a


                                             <reg>

element within the


                                             <orgName>

element. We use the


                                             <reg>

element to tag the name of the organization.

<org xml:id="LEMD1">
  <orgName>
    <reg>LEMDO Team</reg>
  </orgName>
</org>

¶ Encode Note

Nest a


                                             <note>

element inside the


                                             <org>

element underneath the


                                             <orgName>

element. The text node of the note element is a brief description of the organization.

¶ Link to a ORGS1 Entry

For instructions on how to link to Orgography entries within a document, refer to our instructions on encoding entities.

¶ Bibliography (BIBL1)

¶ Introduction

The Bibliography is a sitewide database file in the data directory of the Subversion repository. It contains the xml:ids of sources (books, journal articles, etc.) referenced in editions and anthologies. Since many people occasionally edit BIBL1.xml, make sure no one else is working in the file before you make any changes. If you are in HCMC, talk to the other LEMDO team members. If you are not in the lab, send an email to all repository users with the subject Working in BIBL1. When you have finished, validated, and committed your work, send out another email with the subject Finished working in BIBL1.

If you are unable to add an entry to BIBL1.xml when you need to, you can link instead to the placeholder entry BBBB1, and then come back to it later. When linking to the placeholder, make sure you include an XML comment with full details of what needs to be done. For more information on placeholder entries, see Placeholder Entities.

¶ Structure

BIBL1.xml is structured as follows:

¶ Create a Bibliography entry

Here is an example of a bibliography entry:

<bibl xml:id="CONN4">
<editor>Connor, Francis X.</editor>, ed. <title level="m">A Pleasant Conceited Comedy Called Love’s Labour’s Lost</title>. By <author>William Shakespeare</author>. <title level="m">The New Oxford Shakespeare</title>. Ed. <editor>Gary Taylor</editor>, <editor>John Jowett</editor>, <editor>Terri Bourus</editor>, and <editor>Gabriel Egan</editor>. <pubPlace>Oxford</pubPlace>: <publisher>Oxford University Press</publisher>, <date>2016</date>. 777–844. WSB <idno type="WSB">aaag2304</idno>.</bibl>

The


                                          <bibl>

element is the root of every BIBL1.xml entry. It requires a unique xml:id, so that references in other documents to people may be tagged with that unique xml:id and links be made to the information in the Bibliography file. The value of the


                                       @xml:id

should be comprised of a unique four digit and one letter identifier. Ctrl+F the A–Z Index text file on the lemdo-dev site (available from the Resources menu) to find the next unused ID.

<bibl xml:id="CONN4"/>

The text node of the bibliography entry is nested in the


                                          <bibl>

element. For documentation on how to compose the text node of a bibliography entry, see Prepare Edition Bibliography. For documentation on how to encode the text node of a bibliography entry, see Encode Bibliography.

¶ Link to a Bibliography Entry

For instructions on how to link to BIBL1.xml entries within a document, refer to our instructions on encoding entities.

¶ Production Database (PROD1)

¶ Introduction

The Production Database is a sitewide database file in the data directory of the Subversion repository. It contains the xml:ids of productions (plays, films etc.) referenced in editions and anthologies. Since many people occasionally edit PROD1.xml, make sure no one else is working in the file before you make any changes. If you are in HCMC, talk to the other LEMDO team members. If you are not in the lab, send an email to all repository users with the subject Working in PROD1. When you have finished, validated, and committed your work, send out another email with the subject Finished working in PROD1.

If you are unable to add an entry to PROD1.xml when you need to, you can link instead to the placeholder entry PDDD1, and then come back to it later. When linking to the placeholder, make sure you include an XML comment with full details of what needs to be done. For more information on placeholder entries, see Placeholder Entities.

¶ Structure

PROD1.xml is structured as follows:

¶ Create a Production entry

Here is an example of a PROD1.xml entry:

<bibl xml:id="BRAN3">
<author>Branagh, Kenneth</author> and <author>Paul Kafno</author>, dir. <title level="m">Twelfth Night</title>. <distributor>Thames Television</distributor>, <date when="1987">1987</date>. WSB <idno type="WSB">cg31</idno>.</bibl>

The


                                          <bibl>

element is the root of every PROD1.xml entry. It requires a unique xml:id, so that references in other documents to people may be tagged with that unique xml:id and links be made to the information in the Production Database file. The value of the


                                       @xml:id

should be comprised of a unique four digit and one letter identifier. Ctrl+F the A–Z Index text file on the lemdo-dev site (available from the Resources menu) to find the next unused ID.

<bibl xml:id="BRAN3"/>

The text node of the Production Database entry is nested in the


                                          <bibl>

element. For documentation on how to compose the text node of a PROD1.xml entry, see Prepare Production Database Entries. For documentation on how to encode the text node of a PROD1.xml entry, see Encode Productions.

¶ Link to a Production Entry

For instructions on how to link to PROD1.xml entries within a document, refer to our instructions on encoding entities.

¶ Technical Glossary (GLOSS1)

¶ Scope

The sitewide technical glossary in GLOSS1.xml contains technical terms and project-specific terms and definitions thereof. Exclusions: it does not contain definitions of bibliographical or editorial terms. Those terms will be defined in a separate glossary or in EMEE.

Only LEMDO Team members at UVic can edit GLOSS1.

¶ Structure

The file is structured as a series of


                                          <div>

elements, one for each letter of the alphabet. Each one contains a


                                          <list>

element with the


                                       @type

value of glossary.

<div xml:id="GLOSS1_F">
  <head>F</head>
  <list type="glossary">
    <item xml:id="PATH1">
      <label>file path</label>
      <gloss>A list of nested directory names separated by slashes. It is a way of showing directories nested within other directories (e.g., lemdo/data/texts).</gloss>
    </item>
    <item xml:id="EXTE1">
      <label>file extension</label>
      <gloss>The letters that follow the period in a filename. These letters, known as a filename suffix, indicate the file type, for example, .xml is an eXtensible Markup Language document.</gloss>
    </item>
  </list>
</div>

Give the


                                          <div>

the


                                       @xml:id

value of GLOSS1_X, where X is the letter of the alphabet contained in the


                                          <div>

Each item needs a unique xml:id. Follow the ABCD1 pattern for LEMDO xml:ids.

The


                                          <label>

element contains the term being glossed. As much as possible, this term is the one used in the documentation. There may, however, be cases where a synonym is used in the documentation, with a link on the synonym to the term. The content of


                                          <label>

will be displayed in the pop-up.

The


                                          <gloss>

element contains our definition. If you are writing the definition, keep in mind that the people who need these glosses are editors using the LEMDO Encoding Guidelines to encode their editions, and Research Assistants at UVic and elsewhere. Avoid using additional technical terms in your definition of a technical term. Give examples where appropriate. Make a link to another resource if it is helpful.

Note: We have a Schematron rule to prevent <list type="glossary"> from being used outside of GLOSS1, except in


                                          <egXML>

¶ Placeholder Entities

The sitewide data files are edited by many people. To prevent conflicts, only one person can work on each sitewide database file at a time.

If you are unable to add an entry to PERS1.xml, PROS1.xml, ORGS1.xml, BIBL1.xml, or PROD1.xml when you need to, you can link instead to a placeholder entry. Placeholder entries are not meant to be permanent—when you get a chance, replace the placeholder with the correct xml:id. When linking to the placeholder, make sure you include an XML comment with full details of what needs to be done, so encoders who run across the placeholder know why it is there.

The table below outlines the different placeholders.

Sitewide Database File	Placeholder xml:id	Description
PERS1	PEEE1	The purpose of this item is to allow encoders to link to a Personography item when they do not have access to PERS1 or cannot add a new entry.
PROS1	PRRR1	The purpose of this item is to allow encoders to link to a Prosopography item when they do not have access to PROS1 or cannot add a new entry.
ORGS1	OOOO1	The purpose of this item is to allow encoders to link to a Orgography item when they do not have access to ORGS1 or cannot add a new entry.
BIBL1	BBBB1	The purpose of this item is to allow encoders to link to a Bibliography item when they do not have access to BIBL1 or cannot add a new entry.
PROD1	PDDD1	The purpose of this item is to allow encoders to link to a Production Database item when they do not have access to PROD1 or cannot add a new entry.

When linking to any of the above placeholder items, please include a comment explaining the details of the item the link should really point to.

Prosopography

Isabella Seales

Isabella Seales is a fourth year undergraduate completing her Bachelor of Arts in English at the University of Victoria. She has a special interest in Renaissance and Metaphysical Literature. She is assisting Dr. Jenstad with the MoEML Mayoral Shows anthology as part of the Undergraduate Student Research Award program.

Janelle Jenstad

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

Joey Takeda

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

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.

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.

Glossary

Schematron

“Schematron is an open-source language for ensuring that certain patterns are present in XML documents. For example, it can insist upon certain spellings, enforce curly apostrophes, and limit the use of elements to specific contexts. It is the feather duster of an XML project. See An Overview of Schematron.”

Metadata

Authority title	Chapter 5. Entities and Databases
Type of text	Documentation
Short title
Publisher	Linked Early Modern Drama
Series
Source
Editorial declaration
Edition
Encoding description
Document status	prgGenerated
License/availability