Copyright held by
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Further details of licences are available from our
Licences page. For more
information, contact the project director,
Provider: University of Victoria
Database: The Map of Early Modern London
Content: text/plain; charset="utf-8"
TY - ELEC
A1 - Jenstad, Janelle
A1 - Landels-Gruenewald, Tye
A1 - Butt, Cameron
A1 - Holmes, Martin
ED - Jenstad, Janelle
T1 - Create a MoEML TEI Header
T2 - The Map of Early Modern London
ET - 7.0
PY - 2022
DA - 2022/05/05
CY - Victoria
PB - University of Victoria
LA - English
UR - https://mapoflondon.uvic.ca/edition/7.0/encode_teiHeader.htm
UR - https://mapoflondon.uvic.ca/edition/7.0/xml/standalone/encode_teiHeader.xml
ER -
Cuckold’s Haven or Cuckold’s Point and the horn-topped pole that stood on the banks of the Thames were notorious in early modern London. The location was known for adultery both committed and threatened, and was referred to widely in the period’s literature. The Horne Faire of Charlton celebrated the association of the site with an act of cuckoldry involving
The Julian calendar, in use in the British Empire until September 1752. This calendar is used for dates where the date of the beginning of the year is ambigious.
The Julian calendar with the calendar year regularized to beginning on 1 January.
The Julian calendar with the calendar year beginning on 25 March. This was the calendar used in the British Empire until September 1752.
The Gregorian calendar, used in the British Empire from September 1752. Sometimes
referred to as
The Anno Mundi (year of the world
) calendar is based on the supposed date of the
creation of the world, which is calculated from Biblical sources. At least two different
creation dates are in common use. See Anno Mundi (Wikipedia).
Regnal dates are given as the number of years into the reign of a particular monarch.
Our practice is to tag such dates with
Programmer, 2018-present. Junior Programmer, 2015-2017. Research Assistant, 2014-2017. Joey Takeda was a graduate student at the University of British Columbia in the Department of English (Science and Technology research stream). He completed his BA honours in English (with a minor in Women’s Studies) at the University of Victoria in 2016. His primary research interests included diasporic and indigenous Canadian and American literature, critical theory, cultural studies, and the digital humanities.
Data Manager, 2015-2016. Research Assistant, 2013-2015. Tye completed his undergraduate honours degree in English at the University of Victoria in 2015.
Research Assistant, 2012–2013. Cameron Butt completed his undergraduate honours degree in English at the University of Victoria in 2013. He minored in French and has a keen interest in Shakespeare, film, media studies, popular culture, and the geohumanities.
Director of Pedagogy and Outreach, 2015–2020. Associate Project Director, 2015. Assistant Project Director, 2013-2014. MoEML Research Fellow, 2013. Kim McLean-Fiander comes to
Janelle Jenstad is Associate Professor of English at the University of Victoria, Director of
Programmer at the University of Victoria Humanities Computing and Media Centre (HCMC). Martin ported the MOL project from its original PHP incarnation to a pure eXist database implementation in the fall of 2011. Since then, he has been lead programmer on the project and has also been responsible for maintaining the project schemas. He was a co-applicant on MoEML’s 2012 SSHRC Insight Grant.
Clergyman.
Historian and author of
Most MoEML documents, or significant fragments with mol:
prefix and accessed through the web application
with their id + .xml
.
The molagas prefix points to the shape representation of a location on MoEML’s OpenLayers3-based rendering of the Agas Map.
Links to page-images in the Chadwyck-Healey
Links to page-images in the
The mdt (MoEML Document Type) prefix used on
The mdtlist (MoEML Document Type listing) prefix used in linking attributes points to a listings page constructed from a category in the central MDT taxonomy in the includes file. There are two variants, one with the plain _subcategories
, meaning all subcategories of the category.
The molgls (MoEML gloss) prefix used on
This molvariant prefix is used on
This molajax prefix is used on
The molstow prefix is used on
The molshows prefix is used on
The sb prefix is used on
Our editorial and encoding practices are documented in detail in the Praxis section of our website.
The
Responsibility statements are encoded in the PERS1.xml
file. Each
We do not combine multiple
If Quinn MacDonald also serves as encoder for this file, then there should be two separate Markup Editor
inside the
The responsibility statements included in a particular document will depend on the type of the document and the amount of information available about the document. Primary source files and born-digital files have slightly different patterns for the order of
Responsibility statements for transcriptions of primary sources will normally include authors, printers, and book sellers, as well as the transcriber(s), encoder(s), and toponymist(s) who make the text function in the MoEML environment. Consult MoEML’s guidelines for encoding dates to determine which dating method is applicable. In summary, dates before 1752 should be encoded with
Responsibility statements should be listed in the following order:
Printed by Nicholas Okes for Thomas Archer, and are to be sold at his shop in Popes-head Palace
tells us that the printer is Nicholas Okes and Thomas Archer is both the publisher and the bookseller.
The responsibility statements for EIRE1.xml (
Responsibility statements for born digital documents will normally include authors, encoders, copy editors, proofreaders.
Responsibility statements should be listed in the following order:
Encoder
. The encoder is the person who adds TEI tags to the file, including structural tags, Markup Editor
. The markup editor is the person who checks and corrects the encoder’s tagging.
The responsibility statements for CUCK1.xml (location article on
Make sure to include PERS1.xml
and BIBL1.xml
. In addition to the values listed
above like
For a complete list of available responsibilities, consult. the
PERS1.xml
.
Our document collection is large and disparate; we have everything from digital editions of substantial primary source documents such as
Our document type taxonomy is encoded in /db/data/boilerplate/includes.xml
, a file which includes other generic header information which is shared among many documents. It appears as a
The
There is one other feature of categories we need to notice: they can nest inside other categories.
Here is a small extract from further down the
This shows that there is a document type with
As you can see, the includes.xml
file.
You can also browse a simple rendering of the entire taxonomy on the Document Types page, which shows it in the form of a nested list.
Now you understand how the system is set up, how do you actually use it when you’re
encoding a document? Documents are
assigned to categories through a special section of the
There are five important points to note:
mdtprefix (
MoEML document type).
So what this says is: this is a born-digital document describing a street in the location section of the encyclopedia.
There is a long list of categories, many of which have nothing to do with each other. For instance,
there’s a category called
The schema should help you by prompting you with a list of the values and their meanings
when you create a
Many of the index and listing pages throughout the website are constructed automatically from
categories. You can, for instance, replace the filename in a regular URL on the site with any category
id + .htm
:
and you will see a list of all the documents in that category which are publicly available, formatted in a table
with columns appropriate to the document type. You can also see the subcategories of a category by doing this:
Categories are also used to determine how a document should be rendered; primary source documents obviously need to be rendered differently from born-digital documents, for instance.
Obviously they’re not, because we’ve been adding to them and changing them throughout the process of developing the taxonomy. So if you think there’s something missing, or something is wrong, you can let the programmers know about it. It’s relatively easy to change the taxonomy, but it takes a little work; the taxonomy itself has to be changed, but then the same changes have to be carried over into the ODD file, and a new schema has to be generated. In the case of any substantive change, some of the existing documents in the database may need to be updated too.
For a complete list of document types within the MoEML document collection, please refer to the MoEML Document Type Taxonomy.
Revision descriptions are encoded in the
The revision description for contact.xml serves as an example:
See documentation on general encoding practices for information about how to add draft content to a published page.