The documentation in this chapter is for all editors and encoders. It provides information about LEMDO’s categories and taxonomies including those categories needed to trigger specific processing, standard play IDs, and allowed values for placement of stage directions in semi-diplomatic transcriptions.

Types of Categories

Additional Taxonomies

Learning Outcomes

Contents

Section	Description
Document Type Taxonomy	Learn about key categories for classifying documents and triggering specific category-based processing
Work Type Taxonomy	Learn how to capture the genre of primary documents (e.g., play, mayoral show)
Print Book Formats Taxonomy	Learn how to capture the format of the copytext for your semi-diplomatic transcription (e.g., quarto, folio, manuscript)
Editorial Treatments Taxonomy	Learn how to classify your editorial treatment of a file
Document Histories Taxonomy	Learn how to capture key information about the origin of your file
Audiences Taxonomy	Learn about the audiences we write documentation for
Document Status Taxonomy	Learn about the values we use to track the progress of a file and to indicate a file’s current status
Responsibilities Taxonomy	Learn about the responsibility categories we use to give credit to contributors and collaborators
IDNO Authorities Taxonomy	Learn about the authority identifiers that we use to provide stable references in bibliography entries
Prefix Definitions Taxonomy	Learn about the prefixes LEMDO has created to simplify linking practices
Placement Taxonomy	Learn how to use our placement values to describe the location of stage directions and labels in semi-diplomatic transcriptions
Typographical Glyphs Taxonomy	Learn about the glyphs that LEMDO has used in semi-diplomatic transcriptions (note that we no longer encourage encoders to tag glyphs in new files)
Typographical Ligatures Taxonomy	Learn about the ligatures that LEMDO has used in semi-diplomatic transcriptions (note that we no longer encourage encoders to tag ligatures in new files)
DRE Play IDs	Find the standard abbreviation for each play in the LEMDO repository
Renditions Taxonomy	Learn about the standard renditions that LEMDO has created to simplify inline styling in semi-diplomatic transcriptions

All documents in LEMDO are either born-digital documents or primary documents. Within those two general categories, LEMDO offers additional ways to categorize a file.

Born-digital documents in an edition include: annotations, critical paratexts, bibliographies, the edition landing page, and XML files containing instructions for generating the print output. Born-digital documents in LEMDO-dev include documentation pages, landing pages, databases, and programmatically generated pages. Born-digital files in an anthology include pedagogy pages, landing pages, About pages (i.e., about the project/anthology), history pages (e.g., history of a playing company), and information pages (e.g., copyright, citatation).

Primary documents in an edition include: facsimiles, semi-diplomatic transcription(s), collations, primary paratexts (commendatory poems, prefatory matter, addresses to the reader, alternate prologues), and modernized text(s). LEMDO-dev does not have primary pages. An anthology might have primary documents that are not in an edition, if the anthology chooses to present contextual documents relevant to the entire anthology (e.g., a lease for a playhouse).

Every XML file must have a document type indicated in its <teiHeader> . Capture this information via the <catRef> element. The value of @scheme is tax:emdDocumentTypes. The value of the @target attribute is the relevant category within the Document Type Taxonomy. This example indicates that the file has the document type category cat:ldtPrimaryText.

Born Digital

@xml:id	Name	Description
ldtBornDigAbout	About	Documents about LEMDO or another anthology.
ldtBornDigAboutPolicy	Policy	Documents about LEMDO policy or the policies of another anthology.
ldtBornDigDocumentation	Documentation	Encoding and editorial guidelines; programming, processing, and rendering instructions; how-to instructions; element descriptions; and records of remediation.
ldtBornDigLanding	Landing	Landing pages.
ldtBornDigInfo	Information	Information pages.
ldtBornDigDatabase	Database	Entity collection files.
ldtBornDigGenerated	Generated	Files created automatically during the build.
ldtBornDigAnthology	Anthology	Anthology files (rooted on a <teiCorpus> element).
ldtBornDigEdition	Edition	Root files for textual editions.
ldtBornDigPrint	Print	Root files for print editions.
ldtBornDigParatext	Paratext	Ancillary files that typically form part of an edition, such as acknowledgements.
ldtBornDigParatextCritical	Critical	Critical material, such as a general introduction or a textual introduction.
ldtBornDigParatextBibl	Bibliography	Bibliographies and reference lists.
ldtBornDigParatextCharacters	Characters	Character lists and cast lists. Note that character lists for modernized texts belong in the header of the modernized text, not in a separate file.
ldtBornDigParatextAnnotation	Annotation	Notes, glosses, and other annotations.
ldtBornDigParatextCollation	Apparatus	Collation files.
ldtBornDigParatextHist	History	Documents on historical background.
ldtBornDigParatextPedagogical	Pedagogy	Teaching notes, lesson plans, and other pedagogical material.

Primary

@xml:id	Name	Description
ldtPrimaryText	Primary Source Text	Edited primary source texts. Modernized texts and semi-diplomatic texts must have this value. Not to be used for supplementary texts.
ldtPrimaryFacsimile	Facsimile	Files with <facsimile> pointing to digital surrogates.
ldtPrimaryParatext	Primary Paratext	Dedications, addresses, commendatory poems, and other primary source paratexts. Do not use for EMDP. Use lpt values instead.
ldtTest	Test	Test-only document.

LEMDO’s work type taxonomy allows us to capture the genre of our primary documents. The work type triggers certain types of processing. The current list of work types is short: play, poetry, prose, and mayoral show, and dramatic paratext. We are open to adding new types as required for new anthologies.

Only documents that have the document type of primary (i.e., that have a value of ldtPrimaryText) can have a work type. Capture this information via the <catRef> element. The value of @scheme is tax:emdWorkTypes. The value of the @target attribute is the relevant category within the Work Type Taxonomy. In the following example, note that the file has the document type primary and the work type play.

Work Types

@xml:id	Name	Description
lwtPlay	Play	Dramatic text, semi-diplomatic or modernized.
lwtPoetry	Poetry	Work which is primarily non-dramatic poetry.
lwtProse	Prose	Work which is primarily prose.
lwtShow	Mayoral Show	Mayoral show, semi-diplomatic or modernized.
lwtPara	Dramatic Paratext	Dramatic paratext transcribed for EMDP.

LEMDO’s print book format taxonomy allows us to capture the book format of the sources we transcribe in the semi-diplomatic transcriptions. The book format type triggers certain types of processing as well. The current list of book formats types is short: broadside, folio, quarto, and octavo. We are open to adding new types as required for new anthologies.

Only documents that have the document type value of ldtPrimary (or a subordinate primary document type such as ldtPrimaryText) and editorial treatment type of letSemiDiplomatic can have a book format type. Capture this information via the <catRef> element. The value of @scheme is tax:emdBookFormats. The value of the @target attribute is the relevant category within the Book Format Taxonomy.

Book Formats

@xml:id	Name	Description
lbfBroadside	Broadside	Large sheet printed on one side only.
lbfFolio	Folio	Print volume constructed from sheets folded once.
lbfQuarto	Quarto	Print volume constructed from sheets folded twice.
lbfOctavo	Octavo	Print volume constructed from sheets folded three times.
lbfManuscript	Manuscript	Manuscript.
lbfDuodecimo	Duodecimo	Duodecimo.

LEMDO’s editorial treatment taxonomy allows us to indicate the general editorial treatment the editor has applied to the text. The editorial treatment type triggers certain types of processing as well. For example, some elements (e.g., <pb> , <fw> ) are allowed in texts given semi-diplomatic editorial treatment but not allowed in texts given modernized editorial treatment. The current list of editorial treatments is short: semi-diplomatic, modern, excerpted, and mixed.

Note that LEMDO created the mixed editorial treatment category (letMixed) to deal with legacy supplementary texts. New texts prepared on the LEMDO platform are not allowed to have this editorial treatment. If anthologies choose to allow supplementary texts in an edition, editors must follow either the modern editorial and encoding guidelines or the semi-diplomatic editorial and encoding guidelines. Unless there is some value in retaining semi-diplomatic (e.g., an excerpt from The Faerie Queene, in which spelling is semantically significant), supplementary texts should be modernized because their primary purpose is pedagogical. Most supplementary texts will also be excerpts, which means they will have the additional editorial treatment type of letExcerpted.

Only documents that have the document type value of ldtPrimary (or a subordinate primary document type such as ldtPrimaryText) can have an editorial treatment type. Capture this information via the <catRef> element. The value of @scheme is tax:emdEditorialTreatments. The value of the @target attribute is the relevant category within the Editorial Treatment Taxonomy.

A modern-spelling edition of a play would have the following <catRef> elements:

Editorial Treatments

@xml:id	Name	Description
letSemiDiplomatic	Semi-diplomatic transcription	Texts in which original spelling and other features have been retained.
letModernized	Modernized	Texts that have been modernized according to a set of editorial principles.
letExcerpted	Excerpted	Texts which are not complete, usually because of editorial selection in service of a specific goal.
letMixed	Mixed	Texts in which a variety of possibly incongruous editorial approaches have been mixed. Use this category in combination with ldtPrimary.

LEMDO’s document history taxonomy allows us to indicate the history of a document in cases where we have converted a file from some other source for use in the LEMDO ecosystem. The current list of document history types is short: IML (anything we converted from the ISE Markup Language), XWiki (anything we converted from XWiki, either directly from XWiki files before the server failed or from staticized web pages of XWiki output), TCP (anything we converted to LEMDO TEI P5 from EEBO-TCP’s TEI P4), MoEML (semi-diplomatic transcriptions of mayoral shows for the MoMS anthology), and SQL (anything we created from an SQL database).

Such converted files also undergo lengthy remediation. You will also use the @status attribute on the <revisionDesc> element to track the progress of the remediation. See Document Status Taxonomy.

Only documents that have been converted and have a prior history in some other markup language have a document history type. Capture this information via the <catRef> element. The value of @scheme is tax:emdDocumentHist. The value of the @target attribute is the relevant category within the Document History Taxonomy.

The following example gives the various <catRef> elements for the modernized text of a play that was first prepared in IML for the old ISE platform:

Document History Values

@xml:id	Name	Description
edhSourceIML	Original Source: IML	This TEI file was created based on one or more files from the Internet Shakespeare Editions anthology, originally encoded in ISE Markup Language (a custom markup language somewhat resembling SGML).
edhSourceCBJ	Original Source: Cambridge Ben Jonson	This TEI file was created based on one or more files from the Cambridge Edition of the Works of Ben Jonson Online (CEWBJO or CWBJO), originally encoded in different customization of TEI.
edhSourceXWiki	Original Source: XWiki	This TEI file was created based on one or more supplementary files from the Internet Shakespeare Editions anthology, originally encoded in HTML and stored in the ISE’s XWiki system.
edhSourceTCP	Original Source: TCP	This TEI file was created based on an original encoding from the Text Creation Partnership.
edhSourceMoEML	Original Source: MoEML	This TEI file was created based on an original encoding from The Map of Early Modern London.
edhSourceSQL	Original Source: SQL Database	This TEI file was created from data originally captured in a SQL database structure.

LEMDO’s audience taxonomy allows us to indicate the readership we have in mind when we write documentation. The current list of imagined audiences is short: remediators, encoders, editors, anthology leads, developers, repository users, and documenters. Each of these audiences (except for documenters) also has a Quickstart page. (See Introduction to Quickstart Guidelines.)

Audience types can be applied to the root element of a documentation file, i.e., the root <div> element or any child <div> element. We do not apply the audience types to more deeply nested <div> elements.

Audience Types

@xml:id	Name	Description
audRemediator	Remediator	An encoder who has the responsibility of converting IML-encoded or TCP texts to the LEMDO TEI P5 customization.
audEncoder	Encoder	Anyone who is encoding texts in the LEMDO TEI P5 customization.
audEditor	Editor	Anyone who is editing a play or related works for publication in a LEMDO anthology.
audAnthologyLead	Anthology Lead	Anyone who is responsible for a group of editors who are editing plays or related works for publication in a LEMDO-generated anthology (e.g., the leads of MoMS, QME, DRE, NISE).
audDeveloper	Developer	Anyone who is responsible for maintaining the repository, writing processing, running builds, or customizing a CSS file for an anthology. Normally, developers are based at UVic and work in the lemdo/code section of the repository. Anthology leads may hire a developer/designer to customize a CSS file for an anthology.
audRepoUser	Repository User	Anyone who commits work to the LEMDO repository, including editors and RAs who have write privileges on an edition portfolio.
audDocumenter	Documenter	Anyone who writes project documentation.

LEMDO’s document status taxonomy allows us to track the progress of a file from creation to publication. For converted files, the values allows us to track the progress of the remediation. The document status value triggers different aspects of the schema. For example, a document with the @status value of IML-TEI will not trigger most of the schema and Schematron errors. The schema and Schematron kick in only when you changed the @status to IML-TEI_INP. This feature of LEMDO ensures that the files we commit, regardless of their state of remediation or completion, are always valid according to the set of rules that we apply.

Although it may seem redundant, we capture the status in two places whenever the status changes: The reason we have adopted this approach is that it allows us to keep track of the date of all the status changes. Ultimately, we are most interested in the date of publication so that future users can cite the page by its publication date.

A born-LEMDO file will normally go through the following status changes:

A file that was converted from EEBO-TCP will normally go through the following status changes:

A file that was converted from IML will go through the following status changes:

In the example below, we show how we tracked the status of the conversion and remediation of the modernized text of Famous Victories in the <revisionDesc> of emdFV_M. We know that the file was peer reviewed before 2018, when the ISE server failed. Joey Takeda ran the conversion on 2018-07-11. Tracey El Hajj started to remediate the file on 2020-07-10, work that took some time. Janelle Jenstad proofed the file on 2020-12-03. On 2020-12-21, the file was published. The status of the file on the <revisionDesc> would have changed on each of those dates. Since <revisionDesc> shows only the most recent status, the @status attribute on the <change> elements allows us to keep a history of the status changes.

Note that you can switch your document from IML-TEI_INP back to IML-TEI if you have not been able to achieve a fully valid document before you need to commit your file and end your work session for the day. As long as the file is valid with the @status of IML-TEI, you may commit it.

Note on @status published and peerReviewed: LEMDO has anticipated that some parts of editions may be published before undergoing peer review and that some parts of an edition may never undergo peer review (e.g., supplementary materials). LEMDO’s system is designed so that you can have a file published first and peer reviewed later, or vice versa. The date of publication and the date of peer review will be taken from the @when attribute on the <change> element. The final status of the document can be either peerReviewed or published without implying anything about peer review or publication status.

Note on @status draft: This status is for born-digital documents (i.e., documents with <catDesc> of ldtBornDig (or subordinate categories).

Note on @status empty: Do not use this value. We have a handful of empty files left over from the batch conversion of IML files to TEI, to which we have given the status empty to help us find them. Once we have added the content from other sources, we will deprecate this status. Normally, there is no good reason to create an empty file. Most of the time, you will have at least some content to add right away or a template in place. Consult with the LEMDO team at UVic if you do want to create an empty file.

Document Status Values

@xml:id	Name	Description
prgGenerated	Programmatically Generated	Files that are programmatically generated using xslt. Most such files are documentation or apparatus files.
published	Published	Files that have been published.
publishedWithPeerReview	Published with peer review	Files that have been published after being peer-reviewed.
publishedWithoutPeerReview	Published without peer review	Files that have been published before being peer-reviewed.
peerReviewed	Peer-reviewed	Files that have been peer reviewed.
draft	Draft	Files that are being drafted.
empty	Empty	Files that are empty (have no content other than a minimal TEI Header).
deprecated	Deprecated	This document is no longer relevant or has been superseded, but is being preserved as part of LEMDO’s digital archive.
IML-TEI	IML to TEI	The text has been programmatically converted from IML to LEMDO TEI via a series of transformations. The file is a .xml file. There are stray IML tags in these texts that we retain until we have proofed the TEI. The transcription may have been checked by an ISE editor but LEMDO has not yet checked it.
IML-TEI_INP	IML-to-TEI In Progress	The programmatic conversion is in the process of being carefully checked and remediated by a LEMDO team member. The file is a .xml file.
IML-TEI_proofing	IML-to-TEI Ready for Proofing	The fully remediated file is ready for proofing or in the process of being proofed by a LEMDO team member, editor, or anthology lead.
IML-TEI_proofed	IML-to-TEI Proofed	The programmatic conversion has been carefully checked and fully remediated by a LEMDO team member and/or an editor or anthology lead. The file is now ready for peer review (or for publication without peer review).
TCP-TEI	TCP-to-TEI	The text has been programmatically converted from TCP TEI P4 to LEMDO TEI (P5) via a series of transformations. The file is a .xml file. The transcription is only as correct as the underlying TCP transcription (which contains gaps, errors, and normalized long “s” characters). The TCP metadata is retained. This category is only for documents that also have the document type ldt:primary (but not ldt:primaryModern).
TCP-TEI_INP	TCP to TEI In Progress	The text has been programmatically converted from TCP TEI P4 to LEMDO TEI (P5) via a series of transformations. The file is in the process of being carefully corrected, remediated, and proofed by a LEMDO team member. The file is a .xml file. This category is only for documents that also have the document type ldt:primary.
TCP-TEI_proofing	TCP-to-TEI Ready for Proofing	The fully remediated file is ready for proofing or in the process of being proofed by a LEMDO team member, editor, or anthology lead.
TCP-TEI_proofed	TCP to TEI Proofed	This semi-diplomatic text has been programmatically converted from TCP TEI P4 to LEMDO TEI (P5) via a series of transformations and carefully corrected, remediated, and proofed by a LEMDO team member. The file is a .xml file. The transcription has been corrected; gaps have been supplied; the long s has been restored. The TEI tagging has been checked and corrected by a LEMDO team member. This category is only for documents that also have the document type ldt:primary.
TEI_INP	TEI in Progress	The text is being encoded in TEI.
TEI_collating	TEI Collation in Progress	A modernized text has been created from other sources, but has not yet been remediated to fix e.g. capitalization issues or speech prefixes.
TEI_proofing	TEI Ready for Proofing	The fully remediated file is ready for proofing or in the process of being proofed by a LEMDO team member, editor, or anthology lead.
TEI_proofed	TEI Proofed	The text is finished in TEI and proofed.

Because LEMDO is committed to the Collaborators’ Bill of Rights and the Student Collaborators’ Bill of Rights (see LEMDO Ethos), we have an extensive taxonomy of responsibilities that allow you to give credit in specific ways to everyone who contributed in any way to a file. We use the same method to give credit to the early modern authors and printers.

We have used the Library of Congress MARC Code List for Relators (MARC relators) taxonomy as much as possible. See https://www.loc.gov/marc/relators/relaterm.html. The LoC has occasionally added MARC relators at our request (e.g., mrk was a new addition to capture the role of the encoder or markup editor). In other cases, where there is no MARC relator for the responsibility we need to capture, we have created a value of our using the same principle of three letters representing an abbreviation of the full role name.

We give credit via a <respStmt> in the <titleStmt> of the <teiHeader> . You need the name and xml:id of the person responsible. You need the value that best describes their role from the responsibility taxonomy. Finally, you need a phrase for the text node of the <resp> element.

In this example, we indicate that a play is by Thomas Heywood:

In this example, we give credit to the LEMDO team for encoding a transcription and supplying metadata:

Note on the text node of the <resp> element: This is a free text field. LEMDO encourages anthologies to develop their own standardized wording for different types of work but does not currently have any diagnostics to ensure consistency across an anthology.

Responsibility Values

@xml:id	Name	Description
aut	Author	MARC Code List for Relators definition: A person, family, or organization responsible for creating a work that is primarily textual in content, regardless of media type (e.g., printed text, spoken word, electronic text, tactile text) or genre (e.g., poems, novels, screenplays, blogs). Use also for persons, etc., creating a new work by paraphrasing, rewriting, or adapting works by another creator such that the modification has substantially changed the nature and content of the original or changed the medium of expression. LEMDO uses the term author in two contexts: (1) to indicate the author of a primary work or document (such as Hamlet), and (2) to indicate the author of a secondary text (such as the Critical Introduction to Hamlet, by David Bevington).
aut_attrib	Supposed Author	MARC Code List for Relators definition: An author, artist, etc., relating them to a resource for which there is or once was substantial authority for designating that person as author, creator, etc. of the work. LEMDO usage aligns with that of MARC.
bsl	Bookseller	MARC Code List for Relators definition: A person or organization who makes books and other bibliographic materials available for purchase. Interest in the materials is primarily lucrative. LEMDO uses the term bookseller only in the metadata for publications and copies. In cases where a publication was issued with variant title pages, list all booksellers in all variant states of the title page.
csl	Consultant	MARC Code List for Relators definition: A person or organization relevant to a resource, who is called upon for professional advice or services in a specialized field of knowledge or training. Consultant or Technical Advisor: A person who is called upon for professional advice during the editorial and/or encoding processes. Give a person a credit in the edition page if their role is more than one would list in the Acknowledgements page. LEMDO uses this value for a technical advisor who provides training, answers questions, and advises on encoding matters.
edt	Editor	MARC Code List for Relators definition: A person, family, or organization contributing to a resource by revising or elucidating the content, e.g., adding an introduction, notes, or other critical matter. An editor may also prepare a resource for production, publication, or distribution. For major revisions, adaptations, etc., that substantially change the nature and content of the original work, resulting in a new work, see author. LEMDO uses the general term editor only in edition metadata and only to indicate when a person is responsible for editing all parts of an edition. Otherwise, use the more granular terms to describe the precise nature of the editorial role.
edt_asstcoord	Assistant Coordinating Editor	This term is for use in project-level or edition-level credits if an anthology’s organizational structure includes this role. The term assistant coordinating editor appears in the metadata for documents produced before 2017. From 2017 on, this term is reserved for project-level credits. Do not use at the file level; if an assistant coordinating editor performs a specific function with respect to a file, use the precise resp value for their work.
edt_assoccoord	Associate Coordinating Editor	This term is for use in project-level or edition-level credits if an anthology’s organizational structure includes this role. The term assistant coordinating editor appears in the metadata for documents produced before 2017. From 2017 on, this term is reserved for project-level credits. Do not use at the file level; if an associate coordinating editor performs a specific function with respect to a file, use the precise resp value for their work.
edt_assoctext	Associate Textual Editor	This term is for use in project-level or edition-level credits if an anthology’s organizational structure includes this role. The term associate textual editor appears in the metadata for documents produced before 2017. From 2017 on, this term is reserved for project-level credits. Do not use at the file level; if an associate textual editor performs a specific function with respect to a file, use the precise resp value for their work.
cont	Generic Contributor	Legacy term. Do not use: This is a generic category LEMDO uses when we have been unable to determine a more precise role for this person. All generic contributors should be replaced by a more specific value when/if we learn more information.
edt_cont	Contributing Editor	A contributing editor makes a significant contribution to an edition. LEMDO uses this term to give credit to editors who have passed on their work (through choice, retirement, or death) to a new editor or editorial team. If the new editor retains or revises any of the original editor’s work, LEMDO acknowledges the original editor’s input via this resp value.
edt_sup	Supervising Editor	An editor who supervises the work of a student editor.
edt_coord	Coordinating Editor	Some anthologies have one or more coordinating editor. Use this value in responsibility statements on an edition title. Normally, anthologies should not list coordinating editors or general editors on every XML file in an edition.
edt_cpy	Copy Editor	LEMDO uses the term owner for the person who checks facts, quotations, and citations; may make formatting changes; may convert from one citation style to another; may suggest wording changes; and enforces conformity with the project style guide.
edt_gen	General Editor	This term is for use in project-level or edition-level credits if an anthology’s organizational structure includes this role. The term general editor appears in the metadata for documents produced before 2017. From 2017 on, this term is reserved for project-level credits. Do not use at the file level; if an general editor performs a specific function with respect to a file, use the precise resp value for their work.
edt_gentext	General Textual Editor	This term is for use in project-level or edition-level credits if an anthology’s organizational structure includes this role. The term general textual editor appears in the file-level metadata for documents produced before 2017. From 2017 on, this term is reserved for project-level credits. Do not use at the file level; if an general textual editor performs a specific function with respect to a file, use the precise resp value for their work.
edt_genperf	General Editor (Performance)	A person responsible for the performance strategy and methodology of a project.
man	Project Manager	A person responsible for managing the LEMDO project or a project within the LEMDO suite of anthologies.
edt_mrk	Markup Editor	MARC Code List for Relators definition: A person or organization performing the coding of SGML, HTML, or XML markup of metadata, text, etc. LEMDO uses this term for someone who encodes a file, remediates a converted text, or reviews the XML markup of a file.
edt_perf	Performance Editor	This term is for use in project-level or edition-level credits if an anthology’s organizational structure includes this role. The term performance editor appears in the file-level metadata for documents produced before 2017. From 2017 on, this term is reserved for project-level credits. Do not use at the file level; if a performance editor performs a specific function with respect to a file, use the precise resp value for their work.
edt_text	Textual Editor	This term is for use in project-level or edition-level credits if an anthology’s organizational structure includes this role. The term textual editor appears in the file-level metadata for documents produced before 2017. From 2017 on, this term is reserved for project-level credits. Do not use at the file level; if a textual editor performs a specific function with respect to a file, use the precise resp value for their work.
prn	Production Company	MARC Code List for Relators definition: An organization that is responsible for financial, technical, and organizational management of a production for stage, screen, audio recording, television, webcast, etc. LEMDO uses this term for a group that performs a play or makes a film version of a play. Example: Lord Denney’s Players.
edm	Video Editor	MARC Code List for Relators definition: A person, family, or organization responsible for assembling, arranging, and trimming film, video, or other moving image formats, including both visual and audio aspects. LEMDO uses this term for a person who edits the video of a stage performance or edits a film version of a play.
pbd	Anthology Lead	MARC Code List for Relators definition: A person or organization who presides over the elaboration of a collective work to ensure its coherence or continuity. This includes editors-in-chief, literary editors, editors of series, etc. A person who presides over the creation of an anthology on the LEMDO platform, a role that includes commissioning editions, approving proposals, supporting editors, arranging for peer review, and liaising with the LEMDO team.
ptr	Printer	MARC Code List for Relators definition: A person, family, or organization involved in manufacturing a manifestation of printed text, notated music, etc., from type or plates, such as a book, newspaper, magazine, broadside, score, etc. LEMDO uses this term for an early modern printer and for a publisher who is also a printer. For booksellers who are not also printers, use the term bookseller.
rtm_ra	Editorial Research Assistant	MARC Code List for Relators definition: A person who participated in a research project but whose role did not involve direction or management of it Legacy term. Use rtm or appropriate role from 2017 on.
rtm	Research Team Member	MARC Code List for Relators definition: A person who participated in a research project but whose role did not involve direction or management of it. LEMDO uses this term for someone who contributes intellectual work but is not an RA.
scr	Scribe	MARC Code List for Relators definition: A person who is an amanuensis and for a writer of manuscripts proper. LEMDO uses this term to credit the person who copies a manuscript or prepares a fair copy of it. Hands can be described in the HAND1 file.
trl	Translator	MARC Code List for Relators definition: A person or organization who renders a text from one language into another, or from an older form of a language into the modern form. LEMDO usage aligns with that of MARC.
pdr	Project Director	MARC Code List for Relators definition: A person or organization with primary responsibility for all essential aspects of a project, has overall responsibility for managing projects, or provides overall direction to a project manager. LEMDO uses the term project director for the person who directs the LEMDO project. For anthology leads, use pbd.
drt	Director	MARC Code List for Relators definition: A person responsible for the general management and supervision of a filmed performance, a radio or television program, etc. LEMDO uses the term director for the person who manages or supervises a performance. We do not use it for project level directors.
pfr	Proofreader	MARC Code List for Relators definition: A person who corrects printed matter. LEMDO uses the term proofreader for the person who performs minor corrections to a finalized document, which usually include typographical or rendering fixes. For copy-editing, use resp:edt_cpy.
own	Owner	MARC Code List for Relators definition: A person, family, or organization that currently owns an item or collection, i.e., has legal possession of a resource. LEMDO uses the term owner for the person, family, or library that owns the physical copy of an artifact reproduced in facsimile on the platform. The owner is often but not necessarily the copyright holder.
vet	Peer Reviewer	LEMDO uses the term peer reviewer for a person who reviews a transcription, critical materials, dataset, and/or some or all components of an edition.
cph	Copyright Holder	MARC Code List for Relators definition: A person or organization to whom copy and legal rights have been granted or transferred for the intellectual content of a work. The copyright holder, although not necessarily the creator of the work, usually has the exclusive right to benefit financially from the sale and use of the work to which the associated copyright protection applies. Normally the editor is the copyright holder for an LEMDO edition.
edt_comp	Compiler	MARC Code List for Relators definition: A person, family, or organization responsible for creating a new work (e.g., a bibliography, a directory) through the act of compilation, e.g., selecting, arranging, aggregating, and editing data, information, etc. LEMDO uses the term compiler for the person who chooses and aggregates the resources included in an edition, if those resources are not all by the editor of the edition. The compiler and the editor may be the same person; in that case, the person needs two responsibility statements.
aut_ann	Author of Annotations	MARC Code List for Relators definition: A person or organization responsible for the commentary or explanatory notes about a text. LEMDO uses the term author of annotations for a person who writes annotions for a text.
ann	Annotator	MARC Code List for Relators definition: A person who makes manuscript annotations on an item.
aut_col	Collator	A person who compiles the vertical collations for a text.
anl	Analyst	MARC Code List for Relators definition: A person or organization that reviews, examines, and interprets data or information in a specific area. LEMDO usage aligns with that of MARC.
prg	Programmer	MARC Code List for Relators definition: A person, family, or organization responsible for creating a computer program. LEMDO usage aligns with that of MARC.
trc	Transcriber	MARC Code List for Relators definition: A person, family, or organization contributing to a resource by changing it from one system of notation to another. LEMDO uses transcriber to describe those that transcribe the text from a digital surrogate of an early modern text into a semi-diplomatic transcription and for those that do significant work in correcting and encoding the transcription of an early modern work.
wtm	Technical Writer	MARC Code List for Relators definition: Writer of Technical Material: A person responsible for writing or compiling documentation of the project’s editorial, encoding, and programming practices. LEMDO usage aligns with that of MARC.

Part of LEMDO’s long-term linking strategy is to create links to stable projects that offer URIs for their resources. For many projects, the identification number of a resource or catalogue entry forms the basis of the project’s URIs and ultimately URLs to which we can link. In TEI, we wrap identification numbers in the <idno> element. IDNOs that we capture include DEEP numbers, DOIs, ISBNs, STC numbers, GitHub numbers, and others.

To learn how to encode an <idno> element, see Capture Authority Identifiers in Bibliography Entries and Practice: Link to Authorities and Surrogates.

IDNO Values

@xml:id	Name	Description
BBTI	BBTI	British Book Trade Index
BritDrama	BritDrama	Number in Wiggins and Richardson, British Drama 1533–1642: A Catalogue
call	Call Number	Library call number or shelf mark
DEEP	DEEP	Database of Early English Playbooks: http://deep.sas.upenn.edu
DOI	DOI	Digital Object Identifier
EMDP	EMDP	Identifier given to playbook or paratext in the Folger SQL database version of Early Modern Dramatic Paratexts
TCP-GIT	TCP-Github	TCP Github Number
EEBO-CITATION	EEBO-CITATION	EEBO Citation Number
EEBO-VID	EEBO-VID	EEBO Image Identifier
ESTC	ESTC	English Short Title Catalogue: estc.bl.uk
Greg	Greg	W.W. Greg’s A Bibliography of English Printed Drama to the Restoration
GB	GB	Google Books
ISBN	ISBN	International Standard Book Number
LEME	LEME	Lexicons of Early Modern English
Mar_Census	Marlowe Census	Marlowe Census, ed. Rob Carson (https://www.marlowecensus.org/)
Murphy	Murphy	Murphy, Andrew
OCLC	OCLC	World Cat
oldURI	Old URI	The old URI of a webpage that has disappeared or is soon to be deprecated. Use in the sourceDesc for remediated ISE, DRE, QME, CWBJO, B&F, and EMDP texts, and in other contexts where the old URI might be useful. The value of recording old URIs is not just historical; sometimes these webpages have been captured by the Wayback Machine. Providing the old URI means that users can search for the webpage in the Wayback Machine.
LEMDO	LEMDO	The current canonical URI of a modern edition of a play on the LEMDO site. This is used in the print edition of a play to provide a URL for readers to go from print to online.
PROQUEST	PROQUEST	Proquest
ShakCensus	Shakespeare Census	Shakespeare Census, ed. Adam G. Hooks and Zachary Lesser (https://shakespearecensus.org/)
sigla	Sigla	The sigla for a bibliographic item in the collation
STC	STC	Short Title Catalogue
TCP	TCP	Text Creation Partnership
URI	URI	Universal Resource Identifier
Wing	Wing	Wing
WSB	WSB	World Shakespeare Bibliography

LEMDO uses prefixes as a kind of shorthand across the project so that you do not have to type full pathways and URLs when you want to point to something inside or outside the project using a <ref> element. When we build an HTML page from your XML, we replace the prefix with the part of the URL that comes before the forward slash. So mol becomes “https://mapoflondon.uvic.ca/”. Prefixes are always followed by a colon and then the unique identifier for the resource within the project to which we wish to point.

You will want to use this page in conjunction with Encode Reference Links.

A prefix is an abbreviation for the predictable part of a Uniform Resource Indicator (URI). A prefix allows us to point easily to unique resources (URIs) within a digital project (e.g., documents, entities, entries, sections of documents) without having to repeat the predictable part of the URI. For example, the Map of Early Modern London’s (MoEML’s) URIs all begin with https://mapoflondon.uvic.ca/. We often point to MoEML resources from LEMDO editions. The full URI of those resources would clutter up our encoding. Instead, we use the prefix mol. When LEMDO’s static HTML pages are built from the underlying encoding, the processing instructions in the LEMDO taxonomy turn mol into https://mapoflondon.uvic.ca. We use prefixes to point to heavily used resources in our own project, such as the Personography and Bibliography, as well as to a few stable resources outside our project. As long as a project has predictable URIs that are constructed of a stable path plus a unique ID, we can use prefixes and the unique ID to point directly to that resource. Our encoding is thus efficient and consistent: doc:lemdo_about yields a link to https://lemdo.uvic.ca/lemdo_about.html; mol:CHEA2 yields a link to https://mapoflondon.uvic.ca/CHEA2.htm. This method of pointing is compatible with Linked Open Data applications and will help LEMDO connect its data to other datasets in the future.

LEMDO’s placement taxonomy allows us to capture where something appears on the printed or manuscript page of the sources we transcribe in semi-diplomatic transcriptions.

These values may only be used in documents that have the categories ldtPrimaryText and letSemiDiplomatic. (See Document Type Taxonomy and Editorial Treatments Taxonomy.)

Note that some values may be used for both print and manuscript sources, some values may be used only for print sources, and some values may be used only for manuscript sources.

Placement Values

@xml:id	Name	Description
plc-right	Right / Droite	A generic place value for anything to the right of the text or a figure, or on the right side of an otherwise empty line (in print) or space (in manuscript). Use this value for transcriptions of print or manuscript texts if your anthology is not using the more granular values of right-margin, right-inline, right-adjacent, right-top, and right-bottom. Allowed in print and manuscript texts. Emplacement par défaut à la droite du texte ou d’une image, ou à la droite à la fin d’une ligne vide dans un livre imprimé / d’un espace vide dans un manuscrit. A utiliser pour la transcription d’un texte imprimé ou manuscrit si l’anthologie n’utilise pas les valeurs plus spécifiques de: marge-droite, intégré-droite, adjacent-droite, haut-droite, bas-droite. Autorisé pour les imprimés et les manuscrits.
plc-right-margin	Right Margin / Marge-droite	In the right margin. For print texts, the right margin is a formal area to the right of the text block. For manuscripts, use your judgement about what constitutes the marginal area. Allowed in print and manuscript texts. Dans la marge droite. Pour les textes imprimés, la marge droite définit la zone à la droite du bloc de texte. Ce qui constitue la marge dans le cas des manuscrits est à l’appréciation de l’éditeur. Autorisé pour les imprimés et les manuscrits.
plc-right-inline	Right Inline (Print) / Intégré-droite (Imprimé)	Within a compositorial line of a printed text and aligned to the right margin. Allowed only in print texts and in manuscript texts that are modelled on printed pages. Dans le corps du texte imprimé et aligné sur la marge droite. Autorisé seulement pour les imprimés.
plc-right-adjacent	Right Adjacent / Adjacent-droite	Beside a speech or other literary division, inside the text block (printed texts) or close to the main text (manuscript) but not in the margin. Use this value for interjections, simultaneous speeches, and floating stage directions that span multiple lines. Allowed in print and manuscript texts. A côté d’une réplique ou d’une autre division du texte, à l’intérieur du bloc de texte pour les imprimés, et à côté du texte principal pour les manuscrits, mais pas dans la marge. Valeur à utiliser pour les interjections, les répliques simulténées et les didascalies flottantes qui se poursuivent sur plusieurs lignes. Autorisé dans les manuscrits et imprimés
plc-right-top	Right Top / Haute-droite	At the top right of the page. For print texts, the top is the forme work area. For manuscripts, use your judgement about what constitutes the top of the page. For print folio collections, use this value to indicate placement of page numbers. For manuscripts, use this value to indicate placement of foliation numbers. Allowed in print and manuscript texts. Dans la marge supérieure à droite. Pour les imprimés, il s’agit du blanc de tête. A l’appréciation de l’éditeur pour les manuscrits. Pour les imprimés, utiliser cette valeur pour indiquer le placement de la pagination. Pour les manuscrits, utiliser cette valeur pour indiquer le placement de la foliotation. Autorisé pour imprimés et manuscrits.
plc-right-bottom	Right Bottom / Bas-droite	At the bottom right of the page. For print texts, the bottom is the forme work area. For manuscripts, use your judgement about what constitutes the bottom of the page. Note that catchwords are assumed to be right-bottom, so you do not need to add a place attribute and value. Allowed in print and manuscript texts. Dans la marge inférieure à droite de la page. Pour les textes imprimés, désigne le blanc de pied. Pour les manuscrits, à l’appréciation de l’éditeur. Notez que les réclames sont en bas à droite par défaut, il n’est pas pas nécessaire d’ajouter un attribut et une valeur d’emplacement. Autorisé pour les imprimés et les manuscrits.
plc-left	Left / Gauche	A generic place value for anything to the left of the text or a figure, or on the left side of an otherwise empty line (in print) or space (in manuscript). Use this value for transcriptions of print or manuscript texts if your anthology is not using the more granular values of left-margin, left-inline, left-top, and left-bottom. Allowed in print and manuscript texts. Emplacement par défaut à la gauche du texte ou d’une image, ou à la gauche de la ligne vide d’un livre imprimé / de l’espace vide d’un manuscrit. À utiliser pour la transcription d’un texte imprimé ou manuscrit si l’anthologie n’utilise pas les valeurs plus spécifiques de marge-gauche, intégré-gauche, adjacent-gauche, haut-gauche, bas-gauche. Autorisé pour imprimés et manuscrits.
plc-left-margin	Left Margin / Marge gauche	In the left margin. For print texts, the left margin is a formal area to the left of the text block. For manuscripts, use your judgement about what constitutes the marginal area. Allowed in print and manuscript texts. Dans la marge gauche. Pour les imprimés, la marge gauche définit la zone à la gauche du bloc de texte. Ce qui constitue la marge dans le cas des manuscrits est à l’appréciation de l’éditeur. Autorisé pour imprimés et manuscrits.
plc-left-inline	Left Inline (Print) / Intégré gauche (imprimé)	Within a compositorial line of a printed text and aligned to the left margin. Allowed only in print texts. Prohibited in manuscript texts. Dans le corps du texte imprimé et aligné sur la marge gauche. Proscrit dans les manuscrits.
plc-left-top	Left Top / Haut gauche	At the top left of the page. For print texts, the top is the forme work area. For manuscripts, use your judgement about what constitutes the top of the page. For print folio collections, use this value to indicate placement of page numbers. For manuscripts, use this value to indicate placement of foliation numbers. Allowed in print and manuscript texts. En haut à gauche de la page. Pour les textes imprimés, il s’agit du blanc de tête. Pour les manuscrits, à l’appréciation de l’éditeur. Pour les imprimés, utilisez cette valeur pour indiquer l’emplacement de la pagination; our les manuscrits, celui de la foliotation. Autorisé pour imprimés et manuscrits.
plc-left-bottom	Left Bottom / Bas gauche	At the bottom left of the page. For print texts, the bottom is the forme work area. For manuscripts, use your judgement about what constitutes the bottom of the page. Allowed in print and manuscript texts. Dans la marge inférieure gauche de la page. Pour les textes imprimés, désigne le blanc de pied. Pour les manuscrits, à l’appréciation de l’éditeur. Autorisé pour imprimés et manuscrits.
plc-centre	Centre / Centre	A generic place value for anything centered roughly horizontally in a line or area on the page. Use this value in any print text (regardless of anthology policy) if you want to indicate that a compositorial line is centered (e.g., Finis). Use this value for transcriptions of print or manuscript texts if your anthology is not using the more granular values of centre-top and centre-bottom. Allowed in print and manuscript texts. Valeur générique pour l’emplacement de tout élément centré horizontalement sur une ligne ou zone de la page. Utiliser cette valeur dans tout texte imprimé (quelle que soit la politique éditoriale de l’anthologie) si vous souhaitez indiquer qu’une ligne de la composition est centrée (par ex: Finis). A utiliser pour les transcriptions d’imprimés ou manuscrits si l’anthologie n’utilise pas les valeurs spécifiques de haut-centre et bas- centre. Autorisé pour imprimés et manuscrits.
plc-centre-top	Centre Top / Centre haut	At the top centre of the page. For print texts, the top is the forme work area. For manuscripts, use your judgement about what constitutes the top of the page. Note that running titles are assumed to be centre-top, so you do not need to add a place attribute and value. Allowed in print and manuscript texts. En haut de la page et centré. Pour les imprimés, il s’agit du blanc de tête. Pour les manuscrits, à l’appréciation de l’éditeur. Notez que les titres courants sont centre-haut par défaut, il n’est pas nécessaire de leur assigner un attribut ou une valeur d’emplacement. Autorisé pour imprimés et manuscrits.
plc-centre-bottom	Centre Bottom / Centre bas	At the bottom centre of the page. For print texts, the bottom is the forme work area. For manuscripts, use your judgement about what constitutes the bottom of the page. Note that signature numbers are assumed to be centre-bottom, so you do not need to add a place attribute and value. Allowed in print and manuscript texts. Dans la marge inférieure de la page. Pour les textes imprimés, désigne le blanc de pied. Pour les manuscrits, à l’appréciation de l’éditeur. Notez que les signatures sont centre-bas par défaut, il n’est pas nécessaire d’ajouter un attribut et une valeur d’emplacement. Autorisé pour les imprimés et les manuscrits.
plc-bottom	Bottom / Bas	A generic place value for anything at the bottom of the page. For print texts, the bottom is the forme work area. For manuscripts, use your judgement about what constitutes the bottom of the page. Use this value for transcriptions of print or manuscript texts if your anthology is not using the more granular values of centre-bottom, left-bottom, and right-bottom. Allowed in print and manuscript texts. Valeur générique pour désigner l’emplacement de tout élément en bas de page. Pour les imprimés, le bas de la page désigne le blanc de pied. Pour les manuscrits, c’est à l’appréciation de l’éditeur. A utiliser pour les transcriptions d’imprimés ou manuscrits, si l’anthologie n’utilise pas les valeurs spécifiques de centre-bas, bas-gauche et bas-droite. Autorisé pour imprimés et manuscrits.
plc-top	Top / Haut	A generic place value for anything at the top of the page. For print texts, the top is the forme work area. For manuscripts, use your judgement about what constitutes the top of the page. Use this value for transcriptions of print or manuscript texts if your anthology is not using the more granular values of centre-top, left-top, and right-top. Allowed in print and manuscript texts. Valeur générique pour tout élément situé en haut de la page. Pour les textes imprimés, le haut de la page désigne le blanc de tête. Pour les manuscrits, c’est à l’appréciation de l’éditeur. A utiliser pour les transcriptions d’imprimés ou manuscrits si l’anthologie n’utilise pas les valeurs spécifiques de centre-haut, haut-gauche et haut-droite. Autorisé pour imprimés et manuscrits.
plc-inline	Inline	A generic place value for anything on its own compositorial line but not aligned right, left, or centre.
plc-right-above	Right Above (manuscript) / Droite dessus	Above and to the right of the text, floating (possibly added at a later stage). Allowed only in manuscript texts. Prohibited in print texts. Au-dessus à droite du texte, flottant (possiblement un ajout ultérieur). Autorisé seulement dans les manuscrits, proscrit dans les textes imprimés.
plc-right-below	Right Below (manuscript) / Droite dessous	Below and to the right of the text, floating (probably added at a later stage). Allowed only in manuscript texts. Prohibited in print texts. Au-dessous et à droite du texte, flottant (possiblement un ajout ultérieur). Autorisé seulement dans les manuscrits, proscrit dans les textes imprimés.
plc-left-above	Left Above (manuscript) / Gauche dessus	Above and to the left of the text, floating (possibly added at a later stage). Allowed only in manuscript texts. Prohibited in print texts. Au-dessus à gauche du texte, flottant (possiblement un ajout ultérieur). Autorisé seulement dans les manuscrits, proscrit dans les textes imprimés.
plc-left-below	Left Below (manuscript) / Gauche dessous	Below and to the left of the text, floating (probably added at a later stage). Allowed only in manuscript texts. Prohibited in print texts. Au-dessous et à gauche du texte, flottant (possiblement un ajout ultérieur). Autorisé seulement dans les manuscrits, proscrit dans les textes imprimés.
plc-centre-above	Centre Above (manuscript) / Centre dessus	Centered above the text, floating (probably added at a later stage). Allowed only in manuscript texts. Prohibited in print texts. Centré et au-dessus du texte, flottant (possiblement un ajout ultérieur). Autorisé seulement dans les manuscrits, proscrit dans les textes imprimés.
plc-centre-below	Centre Below (manuscript) / Centre dessous	Centered below the text, floating (probably added at a later stage). Allowed only in manuscript texts. Prohibited in print texts. Centré en dessous du texte, flottant (possiblement un ajout ultérieur). Autorisé seulement dans les manuscrits, proscrit dans les textes imprimés.
plc-above	Above (manuscript) / Dessus	A generic place value for anything above the text and floating (probably added at a later stage). Allowed only in manuscript texts. Prohibited in print texts. Valeur générique pour tout élément placé au-dessus d’un élément textuel, flottant (possiblement un ajout ultérieur). Autorisé seulement dans les manuscrits, proscrit dans les textes imprimés.
plc-below	Below (manuscript) / Dessous	A generic place value for anything below the text and floating (probably added at a later stage). Allowed only in manuscript texts. Prohibited in print texts. Valeur générique pour tout élément placé sous un élément textuel, flottant (possiblement un ajout ultérieur). Autorisé seulement dans les manuscrits, proscrit dans les textes imprimés.
plc-opposite	Opposite (manuscript) / En face	A generic place value for anything on the opposite [i.e., facing] page (possibly added at a later stage). Allowed only in manuscript texts. Prohibited in print texts. Valeur générique pour tout élément placé sur la page opposée (en face) (possiblement un ajout ultérieur). Autorisé seulement dans les manuscrits, proscrit dans les textes imprimés.
plc-overleaf	Overleaf (manuscript) / page d’après	A generic place value for anything on the other side of the leaf (possibly added at a later stage). Allowed only in manuscript texts. Prohibited in print texts. Valeur générique pour tout élément placé de l’autre côté de la feuille (possiblement un ajout ultérieur). Autorisé seulement dans les manuscrits, proscrit dans les textes imprimés.
plc-inspace	Inspace (manuscript) / Intercalé	In a predefined space, [i.e., left by an earlier scribe]. Allowed only in manuscript texts. Prohibited in print texts. Intercalé dans un espace prédéfini (laissé par un scripteur précédent, par exemple). Autorisé seulement dans les manuscrits, proscrit dans les textes imprimés.
plc-overwritten	Overwritten (manuscript) / Réécrit	A generic place value for any additional material written over deleted material. Allowed only in manuscript texts. Prohibited in print texts. Valeur générique pour tout élément ajouté par-dessus un ou plusieurs éléments supprimés. Autorisé seulement dans les manuscrits, proscrit dans les textes imprimés.
plc-CHECK	THIS VALUE NEEDS TO BE CHECKED AND REASSIGNED.	Used where there is no direct conversion from old values, so human intervention is required. Utilisé lorsqu’il n’y a pas de conversion directe des anciennes valeurs possible, ce qui nécessite une intervention humaine.

Understanding LEMDO’s Placement Value

Examples

Further Reading

While LEMDO no longer encourages anthologies to tag glyphs and ligatures in their semi-diplomatic transcriptions, older LEMDO editions tagged glyphs using the values documented on this page. To learn about LEMDO’s current practices for encoding glyphs, see Encode Glyphs and Ligatures in Semi-Diplomatic Transcriptions.

Typographical Glyph Values

@xml:id	Glyph name	Mappings	Note
g_UNKNOWN	Unknown	standard: � unicode: U+FFFD	This indicates something that needs investigation by an editor, and a better encoding solution. It is a temporary option.
g_caret	Caret	modern: ^ standard: ^ unicode: U+2038
g_doubleHyphen	Double Oblique Hyphen	modern: - standard: ⸗ unicode: U+2E17
g_amacron	Latin Small Letter a with Macron	modern: a[nm] standard: ā iml: {_a} unicode: U+0101	The expansion of this glyph depends on its context; in most cases it involves the addition of a nasal, but each case must be handled manually. See also Latin Small Letter “a” with Tilde.
g_emacron	Latin Small Letter e with Macron	modern: e[nm] standard: ē iml: {_e} unicode: U+0113	The expansion of this glyph depends on its context; in most cases it involves the addition of a nasal, but each case must be handled manually. See also Latin Small Letter “e” with Tilde.
g_imacron	Latin Small Letter i with Macron	modern: i[nm] standard: ī iml: {_i} unicode: U+012B	The expansion of this glyph depends on its context; in most cases it involves the addition of a nasal, but each case must be handled manually. See also Latin Small Letter “i” with Tilde.
g_mmacron	Latin Small Letter m with Macron	modern: m[nm] standard: m̄ iml:	The expansion of this glyph depends on its context; in most cases it involves the addition of a nasal, but each case must be handled manually. See also Latin Small Letter “o” with Tilde.
g_nmacron	Latin Small Letter n with Macron	modern: n[nm] standard: n̄ iml:	The expansion of this glyph depends on its context; in most cases it involves the addition of a nasal, but each case must be handled manually. See also Latin Small Letter “o” with Tilde.
g_omacron	Latin Small Letter o with Macron	modern: o[nm] standard: ō iml: {_o} unicode: U+014D	The expansion of this glyph depends on its context; in most cases it involves the addition of a nasal, but each case must be handled manually. See also Latin Small Letter “o” with Tilde.
g_umacron	Latin Small Letter u with Macron	modern: u[nm] standard: ū iml: {_u} unicode: U+016B	The expansion of this glyph depends on its context; in most cases it involves the addition of a nasal, but each case must be handled manually. See also Latin Small Letter “u” with Tilde.
g_wmacron	Latin Small Letter w with Macron	modern: w[nm] standard: w̄ iml: {_w} unicode: w U+0304
g_ymacron	Latin Small Letter y with Macron	modern: y[nm] standard: ȳ iml: {_y} unicode: U+0233	The expansion of this glyph depends on its context; in most cases it involves the addition of a nasal, but each case must be handled manually.
g_e	Combining Latin Small Letter e	modern: e standard: e unicode: U+0364	Usually in combination with y, and the ye combination will need to be tagged with choice, abbr, and expan to expand the y into th.
g_u	Combining Latin Small Letter u	modern: u standard: u unicode: U+0367	Usually in combination with y, and the yu combination will need to be tagged with choice, abbr, and expan to expand the y into th. The editor will need to determine if the word should be expanded to thou or you.
g_t	Combining Latin Small Letter t	modern: t standard: t unicode: U+036D	Usually in combination with y, and the yt combination will need to be tagged with choice, abbr, and expan to expand the y into th.
g_atilde	Latin Small Letter a with Tilde	modern: a[nm] standard: ã iml: {~a} unicode: U+00E3	The expansion of this glyph depends on its context; in most cases it involves the addition of a nasal, but each case must be handled manually. See also Latin Small Letter a With Macron.
g_etilde	Latin Small Letter e with Tilde	modern: e[nm] standard: ẽ iml: {~e} unicode: U+1EBD	The expansion of this glyph depends on its context; in most cases it involves the addition of a nasal, but each case must be handled manually. See also Latin Small Letter e With Macron.
g_itilde	Latin Small Letter i with Tilde	modern: i[nm] standard: ĩ iml: {~i} unicode: U+0129	The expansion of this glyph depends on its context; in most cases it involves the addition of a nasal, but each case must be handled manually. See also Latin Small Letter i with Macron.
g_ocircumflex	Latin Small Letter o with Circumflex	modern: o standard: ô unicode: U+00D4
g_otilde	Latin Small Letter o with Tilde	modern: o[nm] standard: õ iml: {~o} unicode: U+00F5	The expansion of this glyph depends on its context; in most cases it involves the addition of a nasal, but each case must be handled manually. See also Latin Small Letter o with Macron.
p_macron	Latin small letter p with macron	modern: p̄ standard: p̄ unicode: U+0070U+0304
g_utilde	Latin Small Letter u with Tilde	modern: u[nm] standard: ũ iml: {~u} unicode: U+0169	The expansion of this glyph depends on its context; in most cases it involves the addition of a nasal, but each case must be handled manually. See also Latin Small Letter u with Macron.
g_ntilde	Latin Small Letter n with Tilde	modern: ñ standard: ñ iml: {~n} unicode: U+00F1
g_udiaeresis	Latin Small Letter u with Diaeresis	modern: u standard: ü unicode: U+00FC
g_longS	Latin Small Letter Long s	modern: s standard: ſ iml: {s} unicode: U+017F
g_thorn	Latin Capital Letter Thorn	modern: th standard: þ iml: {th} unicode: U+00FE
g_wynn	Latin Letter Wynn	modern: w standard: ƿ unicode: U+01BF
g_eth	Latin Small Letter Eth	modern: th standard: ð unicode: U+00F0
g_vv	Lowercase Double v for w	modern: w standard: w typeset: vv iml: {vv} iml: {w}
g_VV	Uppercase Double V for W	modern: W standard: W typeset: VV iml: {VV} iml: {W}
g_rotunda	Latin Small Letter r Rotunda	modern: r standard: ꝛ iml: {r} unicode: U+A75A
g_zeroWidthSpace	Zero Width Space	modern: standard: ​​ iml: {#} unicode: U+200B
g_cutp	Latin Small Letter p with Stroke Through Descender	modern: ꝑ standard: ꝑ unicode: U+A751
g_cutP	Latin Capital Letter P with Stroke Through Descender	modern: Ꝑ standard: Ꝑ unicode: U+A750
g_que	Latin Small Letter et, meaning que	modern: ꝫ standard: ꝫ unicode: U+A76B
g_con	Latin Small Letter Con	modern: con standard: ꝯ unicode: U+A76F
g_us	Modifier Small Letter us Superscripted	modern: us standard: ꝰ unicode: U+A770
g_us_Eng	Modifier Letter us in English MS Not Superscript	modern: us standard: Ꝯ unicode: U+A76E
g_ye	Modifier y Small e Above	modern: ye standard: ye
g_yt	Modifier y Small t Above	modern: yt standard: yt

While LEMDO no longer encourages anthologies to tag glyphs and ligatures in their semi-diplomatic transcriptions, some semi-diplomatic files (mostly inherited from other projects) tagged ligatures using the values documented on this page. To learn about LEMDO’s current practices for encoding ligatures, see Encode Glyphs and Ligatures in Semi-Diplomatic Transcriptions.

Typographical Ligature Values

@xml:id	Glyph name	Mappings
lig_AE	Latin Capital Letter/Ligature AE	modern: ae standard: AE precomposed: Æ iml: {AE} unicode: U+00C6
lig_ae	Latin Small Letter/Ligature ae	modern: ae standard: ae precomposed: æ iml: {ae} unicode: U+00E6
lig_as	Latin Small Ligature as	modern: as standard: as iml: {as}
lig_ct	Latin Small Ligature ct	modern: ct standard: ct iml: {ct}
lig_ee	Latin Small Ligature ee	modern: ee standard: EE iml: {ee}
lig_es	Latin Small Ligature es	modern: es standard: es
lig_ess	Latin Small Ligature e Long s Short s	modern: ess standard: eſs iml: {e{s}s}
lig_fa	Latin Small Ligature fa	modern: fa standard: fa iml: {fa}
lig_fe	Latin Small Ligature fe	modern: fe standard: fe iml: {f}
lig_ff	Latin Small Ligature ff	modern: ff standard: ff precomposed: ff iml: {ff} unicode: U+FB00
lig_ffa	Latin Small Ligature ffa	modern: ffa iml: {ffa}
lig_ffe	Latin Small Ligature ffe	modern: ffe iml: {ffe}
lig_ffi	Latin Small Ligature ffi	modern: ffi standard: ffi precomposed: ffi iml: {ffi} unicode: U+FB03
lig_ffl	Latin Small Ligature ffl	modern: ffl standard: ffl precomposed: ffl iml: {ffl} unicode: U+FB04
lig_ffr	Latin Small Ligature ffr	modern: ffr iml: {ffr}
lig_fi	Latin Small Ligature fi	modern: fi standard: fi precomposed: fi iml: {fi} unicode: U+FB01
lig_fl	Latin Small Ligature fl	modern: fl standard: fl precomposed: fl iml: {fl} unicode: U+FB02
lig_fo	Latin Small Ligature fo	modern: fo standard: fo iml: {fo}
lig_fr	Latin Small Ligature fr	modern: fr standard: fr iml: {fr}
lig_ft	Latin Small Ligature ft	modern: ft standard: ft iml: {ft}
lig_fu	Latin Small Ligature fu	modern: fu iml: {ffu}
lig_IJ	Latin Capital Ligature IJ	modern: IJ standard: IJ precomposed: IJ iml: {IJ} unicode: U+0132
lig_ij	Latin Small Ligature ij	modern: ij standard: ij precomposed: ij iml: {ij} unicode: U+0133
lig_is	Latin Small Ligature is	modern: is standard: is iml: {is}
lig_ll	Latin Small Ligature ll	modern: ll standard: ll iml: {ll}
lig_oe	Latin Small Letter/Ligature oe	modern: oe standard: OE precomposed: œ iml: {oe} unicode: U+1053
lig_oo	Latin Small Letter/Ligature oo	modern: oo standard: oo iml: {oo}
lig_os	Latin Small Ligature os	modern: os standard: os iml: {os}
lig_Qu	Latin Ligature Capital Q Small u	modern: Qu standard: Qu
lig_Que	Latin Ligature Capital Q Small u Small e	modern: Que standard: Que
lig_Qui	Latin Ligature Capital Q Small u Small i	modern: Qui standard: Qui
lig_longS_a	Latin Small Ligature Long s a	modern: sa standard: ſa iml: {{s}a}
lig_longS_b	Latin Small Ligature Long s b	modern: sb standard: ſb iml: {{s}b}
lig_longS_c	Latin Small Ligature Long s c	modern: sc standard: sc iml: {{s}c}
lig_longS_e	Latin Small Ligature Long s e	modern: se standard: ſe iml: {s{e}}
lig_longS_g	Latin Small Ligature Long s g	modern: sg standard: ſg iml: {{s}g}
lig_longS_h	Latin Small Ligature Long s h	modern: sh standard: ſh iml: {{s}h}
lig_longS_i	Latin Small Ligature Long s i	modern: si standard: ſi iml: {{s}i}
lig_sk	Latin Small Ligature sk	modern: sk standard: sk iml: {sk}
lig_sl	Latin Small Ligature sl	modern: sl standard: sl iml: {sl} unicode: U+FB06
lig_longS_k	Latin Small Ligature Long s k	modern: sk standard: ſk iml: {sk}
lig_longS_l	Latin Small Ligature Long s l	modern: sl standard: ſl iml: {{s}l}
lig_longS_m	Latin Small Ligature Long s m	modern: sm standard: ſm iml: {{s}m}
lig_longS_n	Latin Small Ligature Long s n	modern: sn standard: ſn iml: {{s}n}
lig_longS_o	Latin Small Ligature Long s o	modern: so standard: ſo iml: {{s}o}
lig_sp	Latin Small Ligature sp	modern: sp standard: sp iml: {sp}
lig_longS_p	Latin Small Ligature Long s p	modern: sp standard: ſp iml: {{s}p}
lig_longS_q	Latin Small Ligature Long s q	modern: sq standard: ſq iml: {{s}q}
lig_longS_longS	Latin Small Ligature Long s Long s	modern: ss standard: ſſ iml: {{s}{s}}
lig_longS_longS_a	Latin Small Ligature Long s Long s a	modern: ssa standard: ſſa iml: {{s}{s}a}
lig_longS_longS_e	Latin Small Ligature Long s Long s e	modern: sse standard: ſſe iml: {{s}{s}e}
lig_longS_longS_i	Latin Small Ligature Long s Long s i	modern: ssi standard: ſſi iml: {{s}{s}i}
lig_longS_longS_l	Latin Small Ligature Long s Long s l	modern: ssl standard: ſſl iml: {{s}{s}l}
lig_longS_longS_o	Latin Small Ligature Long s Long s o	modern: sso standard: ſſo iml: {{s}{s}o}
lig_st	Latin Small Ligature st	modern: st standard: st precomposed: st iml: {st} unicode: U+FB06
lig_longS_t	Latin Small Ligature Long s t	modern: st standard: ſt precomposed: ſt iml: {{s}t} unicode: U+FB05
lig_ss	Latin Small Ligature Long s Short s	modern: ss standard: ſs iml: {{s}s}
lig_longS_u	Latin Small Ligature Long s u	modern: su standard: ſu iml: {{s}u}
lig_longS_w	Latin Small Ligature Long s w	modern: sw standard: ſw iml: {{s}w}
lig_sz	Latin Small Letter Sharp s (Eszett)	modern: ss standard: ss iml: {&szlig} unicode: U+00DF
lig_us	Latin Small Ligature us	modern: us standard: us iml: {us}
lig_Wt	Latin Ligature Wt	modern: with standard: Wt iml: {Wt}
lig_wt	Latin Ligature wt	modern: with standard: wt iml: {wt}

Every play in the LEMDO repository has an abbreviated ID. These IDs are used across the site in a variety of places: LEMDO normally uses the IDs created for the Bibliography of Editions of Early English Drama (BEEED), except for a few legacy editions. IDs for mayoral pageant books match those of the Map of Early Modern London (e.g., The Triumphs of Truth is TRIU1).