Encode Persons

roseList documents mentioning Encode Persons

The Personography File

All personography entries are contained in a single XML file named PERS1.xml. This file is contained in the data folder of the subversion repository. All teams members occasionally edit PERS1.xml. Before you edit the file, make sure no one else is working in the file. If you are in HCMC, talk to the other MoEML team members in HCMC. If you are not in the lab, send an email to all team members 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.

Add a Historical or Literary Person to the Personography

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 made to the information in the Personography file (PERS1.xml). The value of the @xml:id should be comprised of the "mol:" pointer plus a unique four digit and one letter identifier. Use the Transformation Scenario Retrieve Next Free Id in oXygen, or use Ctrl+F on the A-Z Index on the Jenkins site to find the next unused id.
For historical persons, you must also add a @sex attribute to the <person> element. Enter a value of "0" if the person’s sex is unknown, "1" if the person is male, "2" if the person is female, or "9" if the person’s sex is not applicable. If a person is mentioned in Stow and nowhere else, you must add a @source attribute with a value of "mol:stow_1598" to the <person> element. Note that this attribute should be used sparingly, only when you are sure that no further sources exist for a person.
Here are some examples of how to encode the <person> root element:
<person xml:id="THRO4" sex="1">
[…]
</person>
<person xml:id="HUNG7" sex="2" source="mol:stow_1598">
[…]
</person>
Nested within the <person> element should be the following second-tier elements: <persName>, <birth> (if known), <death> (if known), <floruit> (if birth and death are not known), and <note>. The following sections describe how to encode these elements.

Encode Names

Nest a <persName> tag inside the <person> element. We use the <persName> element to tag the various names (forename, surname, etc.) associated with a person. Before tagging these names, add a @type attribute to the <persName> element. We use this attribute to identify a person as a historical figure or a literary figure. If a person is historical, supply a @type value of "hist". If a person is literary, supply a @type value of "lit". Note that some literary persons may be based on historical persons. For example, the literary character Elizabeth I who appears in many post-1603 plays is not the same as the historical queen Elizabeth I. We therefore encode one entry for the historical person and one entry for the literary person.
Nest name tags within the <persName> element. There are six name tags that you can use when encoding a person’s name: <reg>, <forename>, <surname>, <roleName>, <genName>, and <addName>. More details about each one follow:
  • 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 (e.g., <reg>William Shakespeare</reg>). In special cases, however, the regularized version of a person’s name may contain only certain components of their1 name or components in a certain order. The following table outlines a number of special cases in which a person’s regularized name does not follow the usual Forename + Surname format:
    Type of Person Template Example
    Monarch of England Forename + Ordinal
    <reg>Elizabeth I</reg>
    Monarch of a country other than England Forename + Ordinal + of + Dominion
    <reg>Charles I of Spain</reg>
    Member of the peerage Forename + Surname [No Title]
    <reg>Thomas Howard</reg>
    Member of the gentry Sir or Dame + Forename + Surname
    <reg>Sir William Roch</reg>
    Pope Forename + Ordinal
    <reg>Innocent III</reg>
    Saint St. [Not Saint] + Forename + Surname
    <reg>St. Augustine of Canterbury</reg>
    Bishop or priest Forename + Surname [No Title]
    <reg>Thomas Arundel</reg>
    Doctor Dr. [Not Doctor] + Forename + Surname
    <reg>Dr. William Chichele</reg>
    Person with a different birth name Forename + Surname + (née [in the case of woman] + Surname at Birth + )
    <reg>Anne Farrant (née Bower)</reg>
    Person with an alias or well known nickname Forename + Surname + (alias + Alias or Nickname + )
    <reg>Mary Frith (alias Moll Cutpurse)</reg>
    Person with no known surname Mr. or Ms. + Forename
    <reg>Mr. Robert</reg>
    Person with no known forename Mr. or Ms. + Surname
    <reg>Mr. Randoll</reg>
  • Use the <forename> element to tag a person’s forename or given name (e.g., <forename>William</forename>). 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> tag (e.g., <forename>Henry</forename> <forename>Frederick</forename>). We also use the <forename> element to tag the names of allegorical or mythological figures (e.g., <forename>Truth</forename> or <forename>Zeus</forename>).
  • Use the <surname> element to tag a person’s surname or family name (e.g., <surname>Shakespeare</surname>). Sometimes, a person’s surname will contain a preposition (e.g., Catherine of Aragon, Humphrey de Bohun, or Chet van Duzer). Tag these prepositions using the <nameLink> element nested within the <surname> element (e.g., <surname><nameLink>de</nameLink> Bohun</surname>). Note that some people, often married women, may be known by more than one surname. As with people who have multiple forenames, we tag each surname separately (e.g., <surname>Farrant</surname> <surname>Bower</surname>).
  • Use the <roleName> element to tag any titles or roles associated with a person’s name. Often, a role name will be the first component in a person’s name (e.g., <roleName>Sir</roleName>, <roleName>St.<roleName>, <roleName>Pope</roleName>, etc.). Note that each of these tags identify a person as occupying a particular station or rank within society. Sometimes, a role name will be the last component in a person’s name (e.g., <roleName>King of England and Scotland</roleName>, <roleName>Earl of Oxford</roleName>, <roleName>Bishop of Ely</roleName>). These kinds of role names are usually titles or offices that a person holds. If the person is a monarch, we list their <roleName> as the last component of their name (e.g., we tag Elizabeth I as <forename>Elizabeth</forename> <roleName>Queen of England and Ireland</roleName> and not <roleName>Queen</roleName> <forename>Elizabeth</forename>). It is important to note that not everyone who holds an office/title should have a <roleName> tag. As a general rule, we tag the role names of monarchs and other members of royalty, religious officials, members of the nobility, lord mayors, and sheriffs. Conversely, we do not tag the role names of aldermen, livery company directors, etc.
  • Use the <genName> element to tag any ordinals in a person’s name. Usually, only monarchs or popes will have ordinals in their names (e.g., Elizabeth I or Innocent III). We write ordinals as roman numerals and, accordingly, nest a <num> tag with a @type value of "roman" within the <genName>. We also add a @value attribute to the <num> tag with a value that corresponds to that of the roman numeral being tagged. For example, we would encode Inocent III as <forename>Innocent</forename> <genName><num type="roman" value="3">III</num><genName>. When a person has more than one ordinal in their name, we tag each ordinal separately (e.g., <forename>James</forename> <genName><num type="roman" value="1">I</num></genName> <genName><num type="roman" value="3">III</num></genName>).
  • Use the <addName> element to tag any aliases, nicknames, or epithets associated with a person’s name. Most of the time, the <addName> tag should be one of the last components in a person’s name (e.g., <forename>Mary</forename> <surname>Frith</surname> <surname>Moll Cutpurse</surname>, <forename>Ivan</forename> <genName><num type="roman" value="4">IV</num></genName> <surname>the Terribe</surname> <roleName>Czar of Russia</roleName>). Other times, when functioning as a leading epithet, the <addName> tag should precede the other components in a person’s name (e.g., <surname>Black</surname> <forename>Will</forename>, <surname>Old</surname> <forename>Hobson</forename>). In rare cases, the <addName> tag will be the only known component (other than the always-necessary <reg> tag) in a person’s name (e.g., <surname>Whipping Tom</surname>).
In total, the <persName> tag and its nested components should provide a comprehensive record of the various names used to identify a person, as well as an authority name (in the form of the <reg> tag) based on this information. Here are some examples of how to encode the <persName> element:
<persName type="hist">
<reg>William Jaggard</reg>
<forename>William</forename>
<surname>Jaggard</surname>
</persName>
<persName type="hist">
<reg>Ivan <num type="roman" value="4">IV</num></reg>
<forename>Ivan</forename>
<genName><num type="roman" value="4">IV</num></genName>
<addName>the Terrible</addName>
<roleName>Czar of Russia</roleName>
</persName>
<persName type="lit">
<reg>Peace</reg>
<forename>Peace</forename>
</persName>

Encode Life Dates

If known, important life dates such as a person’s date of birth, date of death, and/or flourish dates can be can be encoded following the <persName> element. Three self-closing dating elements may be used:
  • Use the <birth/> element to encode information about a person’s date of birth.
  • Use the <death/> element to encode information about a person’s date of death.
  • Use the <floruit/> element to encode information about the dates a person was active (i.e., their flourish dates).
Choose which dating elements to include. You will often only have enough information to use one or two of the above dating elements. Because death records were far more common than birth records in early modern England, it is easier find information about a person’s date of death. Baptism records often serve as the only primary sources for determining a person’s date of birth. As infants were customarily baptised a few days after they were born, baptism records can provide an approximation of when someone was born. We record flourish dates only if both a person’s date of birth and date of death are unknown.
Next, add attributes with values to the dating elements. Every element must declare (1) a date or duration and (2) the calendar system being used. To declare a date or duration, follow these guidelines:
  • Use the @when-custom attribute to express a single date of birth or date of death. This attribute may not be used in combination with any other dating attributes.
  • Use the @from-custom attribute to express the start date of a duration. This attribute may only be added to the <floruit> element. It must be used in combination with either the @to-custom attribute or the @notAfter-custom attribute.
  • Use the @from-custom attribute to express the start date of a duration. This attribute may only be added to the <floruit> element. It must be used in combination with either the @to-custom attribute or the @notAfter-custom attribute.
  • Use the @notBefore-custom attribute to expresses the earliest possible date of an event. Unlike the value of the @from-custom attribute, the value of the @notBefore-custom attribute is not assumed to be a definitive start date of a duration. In fact, the @notBefore-custom attribute may express any duration that begun after the specified date or any single date that occurred after the specified date. Accordingly, it may be added to any dating element and it may be used by itself or in combination with the @notAfter-custom attribute or the @to-custom attribute.
  • Use the @notAfter-custom attribute to express the latest possible date of an event. Unlike the value of the @to-custom attribute, the value of the @notAfter-custom attribute is not assumed to be a definitive start date of a duration. The @notAfter-custom attribute may express any duration that finished before the specified date or any single date that occurred before the specified date. Accordingly, it may be added to any dating element and it may be used by itself or in combination with the @notBefore-custom attribute or the @from-custom attribute.
  • Values for the @when-custom, @from-custom, @to-custom, @notBefore-custom, and @notAfter-custom attributes must be entered in standard ISO format. Reference particular days as "YYYY-MM-DD", months as "YYYY-MM", and years as "YYYY". Use zeros to fill extra digits in years that are less than four digits (e.g., 0012 [C.E.]). Use negative values when referring to a year before the common-era (e.g., -0008 [B.C.E.]).
To declare the calendar system being used, add a @datingMethod attribute to the dating element, then choose one of the following values:
  • Enter a value of "mol:julianMar" if your source uses a Julian calendar and considers March 25th the beginning of the new year. Any dates taken based on information from Stow should have this value.
  • Enter a value of "mol:julianJan" if your source uses the Julian calendar and considers January 1st the beginning of the new year. Although March 25th traditionally marked the new year in the Julian calendar, some early modern writers (e.g., Samuel Peyps) had already begun using January 1st as the new year to replicate the new style of the Gregorian calendar, which was used by Catholic countries in mainland Europe.
  • Enter a value of "mol:julianSic" if your source uses the Julian calendar, but you are unsure whether January 1st or March 25th is considered the beginning of the new year. In most cases, you will likely use this value as many sources, including the ODNB, are not entirely clear about the calendar system they use.
  • Enter a value of "mol:gregorian" if your source uses the Gregorian calendar. Because England did not begin using the Gregorian calendar until 1752 (well after the period our project studies), you will rarely encounter a source that uses the Gregorian calendar. Nonetheless, it is possible that a source may use a proleptic Gregorian calendar, so the appropriate value is listed here.
In addition to the attributes and values outlined above, there are two optional attributes that can be added to dating elements in special cases:
  • Use the @cert attribute with a value of "low" to express when you are uncertain about the accuracy of a date. This may happen when your information is based on an unreliable resource (e.g., Wikipedia) or when two or more sources give conflicting information.
  • Use the @evidence attribute with a value of "baptism" to express when a date of birth is based on a baptism record. Accordingly, the @evidence attribute should only be added to the <birth/> element.
Here are some examples of how to encode life dates in a personography entry:
<death when-custom="1509" datingMethod="mol:julianMar"/>
<birth notAfter-custom="1560" evidence="baptism" datingMethod="mol:julianSic"/> <death when-custom="1633" datingMethod="mol:julianSic"/>
<floruit from-custom="1648" to-custom="1658" datingMethod="mol:julianSic"/>

Note Biographical Information

A <note> element should always follow the <persName> element. When known, life dates may be inserted between the <persName> and <note> elements. We use the <note> element to encode a short biographical statement and link to one or two external resources about a person.

Write a Bio Statement

Nest a <p> element immediately within the <note> element. We use this <p> element to tag a short biographical statement of one or two sentences about the person. A biographical statement should summarize the salient facts pertaining to a person’s life, including their important roles, titles, and/or relations. For example, here is the biographic statement for Geoffrey de Mandeville:
<p>First earl of Essex. Constable of the <ref target="mol:TOWE5">Tower of London</ref> and sheriff during the <date from-custom="1135" to-custom="1154" datingMethod="mol:julianJan" calendar="mol:regnal">reign of <name ref="mol:STEP1">King Stephen</name></date>. Son of <name ref="mol:MAND4">William de Mandeville</name>.</p>
Note that references to dates, locations, and other people in the biographical statement are marked up using the appropriate TEI-XML tags. Because certain types of people will have similar biographical statements, we have developed a set of templates for common biographical statements:
Type of Person Template Example
Member of the peerage Ordinal(s) [if applicable] + name of title(s) + . + Other biographical information + .
<p>First earl of Oxford and count of Guînes. Grandson of <name ref="mol:VERE1">Aubrey de Vere</name>.</p>
Actor Actor with + name of playing company + .
<p>Actor with the <name ref="mol:KIME1" type="org">King’s Men</name>.</p>
Lord mayor Sheriff of London from + first year as sheriff [in YYYY format] + — + last year as sheriff [in YYYY format] + CE + . + Mayor from + first year as mayor [in YYYY format] + — + last year as mayor [in YYYY format] + CE + . Member of the + Livery company to which he belonged + .
<p>Sheriff of <ref target="mol:LOND5">London</ref> from <date datingMethod="mol:julianSic" from-custom="1489" to-custom="1490">1489—1490</date> CE. Mayor from <date datingMethod="mol:julianSic" from-custom="1503" to-custom="1504">1503—1504</date> CE and from <date datingMethod="mol:julianSic" from-custom="1509" to-custom="1510">1509—1510</date> CE. Member of the <name type="org" ref="mol:DRAP3">Drapers’ Company</name>.</p>
Lay sheriff Sheriff of London from + first year as sheriff [in YYYY format] + — + last year as sheriff [in YYYY format] + CE + . Member of the + Livery company to which he belonged + .
<p>Sheriff of <ref target="mol:LOND5">London</ref> from <date datingMethod="mol:julianSic" from-custom="1442" to-custom="1443">1442—1443</date> CE. Member of the <name type="org" ref="mol:SALT3">Salters’ Company</name>.</p>
Monarch Queen [or] King + of + dominion(s) + , first year of reign [in YYYY format] - last year of reign [in YY format in most cases] + .
<p>Queen of England, <date from-custom="1553" to-custom="1603" datingMethod="mol:julianSic" calendar="mol:julianSic">1533-1603</date>.</p>
Dramatic character Character [or more specific description of role] + in+ Author’s Name + ‘s + Name of Play or Work + .
<p>Constable in <name ref="mol:SHAK1">William Shakespeare</name>’s <title level="m">Much Ado about Nothing</title>.</p>
Allegorical character in a mayoral show Personification of + concept the character represents + . Appears as an allegorical character in mayoral shows.
<p>Personification of purity. Appears as an allegorical character in mayoral shows.</p>
In addition to the special cases outlined in this table, there are a number of universal rules that should be followed when formatting any biographical statement. They are listed here with examples:
  • Biographic statements should be written in fragments rather than complete sentences (e.g., Chaplain. Buried in the parish church of St. Olave’s in Coleman Street Ward.). Separate fragments using periods; avoid using semicolons.
  • As per the MoEML Guide to Editorial Style, any office or title that a person holds should be referred to with down-style capitalization (e.g., lord mayor, sheriff, king, queen, alderman, etc.).
  • Spell out ordinals in titles (e.g., first duke of Bedford).
  • When describing a person’s relationship with another person, use the preposition of rather than to (e.g., husband of Katherine Augustine, mother of Eleanor Writhesley, etc.).
  • Express date ranges that occur in the same century in YYYY-YY format (e.g., 1601-02). Express date ranges that span across two centuries in YYYY-YYYY format (e.g., 1598-1601). Note that we use a hyphen instead of a preposition in date ranges.
  • When noting where a person was buried, insert a separate fragment beginning with Buried in… (e.g., Buried in St. John Parish.).

Example Entries

Examples of fully encoded historical or literary <person> entries in PERS1.xml can be found by searching The Map of Early Modern London CodeSharing Service.

Research a Historical or Literary Person

Biographical research is often required in order to add a historical or literary (especially mythological) person to the personography. The following table outlines the resources we recommend for researching different types of people.
Monarchs
  • The Oxford Dictionary of National Biography (ODNB) contains full-length, scholarly biographies for every monarch of England and many monarchs of France, Spain, and other countries. Unfortunately, ODNB is behind a paywall. The University of Victoria has purchased a subscription to the ODNB, so you can access it on any campus computer or via the library’s proxy server.
  • Encylopedia Britannica contains short, scholarly biographies for every monarch of England and many monarchs of France, Spain, and other countries. Longer biographies are available to those who pay for a subscription (which UVic Libraries does not). Because the free biographies are so short, they are unlikely to contain any information that the ODNB does not.
  • Wikipedia contains an extensive collection of biographies for almost every monarch in the world. Because Wikipeda entries are written and edited by common users, we reccommend that you cross-reference any information you take from Wikipedia with a more reliable source like the ODNB or Encyclopedia Britannica.
Members of the peerage
  • The Oxford Dictionary of National Biography (ODNB) contains full-length, scholarly biographies for most members of the peerage.
  • If a member of the peerage served in the House of Lords, see the History of Parliament Online (HPO) for their full-length biography and family tree. Note that certain time periods (e.g.,1422-1504) are not yet available. HPO is open content, meaning anyone can access it from any internet connection.
  • Wikipedia is another useful resource for researching members of the peerage (especially lesser-known peers). Wikipedia is particularly helpful when you want to search by a person’s title (e.g., fifth earl of Oxford or earls of Oxford).
Members of the gentry
Religious figures
Lord mayors and sheriffs
Stationers
  • The British Book Trade Index (BBTI) contains records of every printer, publisher, and bookseller mentioned in the English Short Title Catologue (ESTC). Entries include the name of the stationer, their date of birth and date of death, locations where they worked, and their roles. Note that there are many duplicate or near-duplicate entries in the BBTI database. To gather all the important information about a stationer, you may need to refer to multiple entries for the same person.
  • The Oxford Dictionary of National Biography (ODNB) and Wikipedia contain encyclopedia articles for some well-known stationers. When available, these articles can provide valuable context for the facts listed in BBTI entries.
Common people
Mythological figures
  • Encyclopedia Mythica is a fairly comprehensive online encyclopedia of Greek, Roman, Celtic, and other ancient mythologies. Enyclopedia articles tend to be short, but reliable.
  • Many mythological figures can also be found in Oxford Reference, a searchable database of reference works published by Oxford University Press. Because the database includes titles such as A Dictionary of Britsh History, A Dictionary of English Folklore, and Encyclopedia/Dictionary of Phrase and Fables, it is a particularly good resource for researching the mythology of London and Britain.
  • Former research assistants have found Theseus and Wikipedia to be useful resources. As both are not necessarily scholarly, we advise you to cross-reference any information gleaned from these resources with a more scholarly resource.
Note that, due to early modern spelling variations, it is sometimes difficult to find the particular person you are looking for in these databases. For example, __X___ is entered in the Mayors and Sheriffs of London (MASL) database as ___Y____. If you were to search for ___X___, you would not find ___Y____. To get around this problem, we recommend that you include many variant spellings of a person’s name in your search.

Add Modern Contributors to the Personography

The basic structure of a personography entry for a modern contributor is the same as for a historical or literary person. Entries consist of a root element (<person>), which contains a <persName> element and a <note> element. We do not encode life dates (i.e., <birth>, <death>, or <floruit> elements) for modern contributors.

Encode the Root Element

The <person> element is the root of every personography entry. To distinguish one personography entry from another, we add an @xml:id attribute to the <person> element with a unique value composed of four letters and one number (e.g., "JENS1"). For more information about @xml:ids, see documentation about generating an @xml:id.
Unlike entries for historical or literary persons, we do not add a @sex attribute to the root element in entries for modern contributors.
Here are some examples of how to encode the root element in a personography entry for a modern contributor:
<person xml:id="ABCD1">
[...]
</person>
<person xml:id="ABCD2">
[...]
</person>

Encode Names

Nest a <persName> tag immediately inside the <person> root element. Add a @type attribute with a value of "cont" to the <name> tag. Inside the <name> tag, nest a <reg> tag. Use the <reg> element to tag a regularized version of the contributor’s name. For a modern contributor, a regularized name should consist of the person’s forename folllowed by their middle name(s) (if applicable) and their surname. Please leave out any suffixes such as Dr. or M.A.
Here are some examples of how to encode the <persName> element in a personography entry for a modern contributor:
<person xml:id="JENS1000">
[...]
<persName type="cont">
<reg>Janelle Jenstad</reg>
<forename>Janelle</forename>
<surname>Jenstad</surname>
<abbr>JJ</abbr>
</persName>
</person>
<person xml:id="HOLM1000">
 [...]     
<persName type="cont">
<reg>Martin D. Holmes</reg>
<forename>Martin</forename>
<forename>D.</forename>
<surname>Holmes</surname>
<abbr>MDH</abbr>
</persName>
</person>

Note Biographical Information

Type of contributor Template Example
Research assistant Research assistant, + years working for MoEML [in YYYY-YY format] + . + One or two sentences about the contributor’s degree program and/or academic interests.
<person xml:id="DUNC33">
[...]
<note><p>Research assistant, 2014 to present. Catriona is an MA candidate at the University of Victoria. Her primary research interests include medieval and early modern literature with a focus on book history, spatial humanities, and technology.</p></note>
</person>
Programmer or technical assistant Programmer [or more specific job title] + at the University of Victoria Humanities Computing and Media Centre (HCMC) [or other place of work, if applicable] + . + One to three sentences about the contributor’s career and/or contributions to MoEML.
<person xml:id="HOLM333">
[...]
<note><p>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.</p></note>
</person>
Pedagogical partner (instructor) Contributor’s full name + is a MoEML pedagogical partner. + Two or three sentences about the contributor’s career. + One sentence about the contributor’s contribution to MoEML.
<person xml:id="HOGA2">
[...]
<note><p>Sarah Hogan is a <title level="m">MoEML</title> Pedagogical Partner. She is Assistant Professor of English Literature at <ref target="http://college.wfu.edu/">Wake Forest University</ref>. Her work has appeared in <title level="j">JMEMS</title>, <title level="j">JEMCS</title>, and <title level="j">Upstart</title>, and she is currently at work on a book-length project, <title level="m">Island Worlds and Other Englands: Utopia, Capital, Empire (1516-1660)</title>. Her class on sixteenth-century British literature will be composing an entry on <ref target="mol:LUDG1">Ludgate</ref>.</p></note>
</person>
Pedagogical partner (student) Student contributor enrolled in + calendar code for pedagogical partnership course + : + name of pedagogical partnership course [in title case] + at + name of their university + in the + season [as determined by their university calendar] + year [in YYYY format] + session, working under the guest editorship of + name of instructor + .
<person xml:id="GARD1">
[...]
<note><p>Student contributor enrolled in <emph>ENGL 534: Historicizing Shakespeare and the Blackfriars Theater</emph> at San Diego State University in the Spring 2014 session, working under the guest editorship of <name ref="mol:HERM3">Peter C. Herman</name>.</p></note>
</person>
Member of the editorial board [...]
Member of the advisory board [...]
Sometimes, a contributor will have had multiple roles with MoEML. If s/he has had multiple roles over the course of months or years, list each role chronologically (including corresponding dates) at the beginning of his/her biographical statement. Tye Landels-Gruenewald’s biographical statement serves as an example:
<person xml:id="LAND22">
              [...]
              <note><p>Research assistant, 2013-15, data manager, 2015-16, and consultant, 2016 to present. Tye completed his undergraduate honours degree in English at the University of Victoria in 2015.</p></note>
            </person>
Conversely, if a contributor has muliple roles at the same time, list each role as though one job title at the start of his/her biographical statement. For example, see Katie McKenna’s biographical statement:
<person xml:id="MCKE44">
              [...]
              <note><p>Encoder and research assistant, 2014-15. Katie McKenna is a third-year English literature major at the University of Victoria with an interest in the digital humanities, particularly digital preservation and typography. Other research interests include philosophy, political theory, and gender studies.</p></note>
            </person>
See Kevin Quarmby’s biographical statement for another example of how to represent a contributor who has multiple roles at the same time:
<person xml:id="QUAR11">
              [...]
              <note><p><name ref="mol:QUAR1">Kevin A. Quarmby</name> is a <title level="m">MoEML</title> Pedagogical Partner and a member of <title level="m">MoEML</title>’s Editorial Board. He is Assistant Professor of English at <ref target="http://oxford.emory.edu/">Oxford College of Emory University</ref>. [...]</p></note>
            </person>

Example Entries

Examples of fully encoded <person> entries for modern contributors in PERS1.xml can be found by searching The Map of Early Modern London CodeSharing Service.

Further Resources

For instructions on naming practices not addressed in this guide, see the National Council on Archives’s Rules for the Construction of Personal Names.

Notes

  1. In 2018, MoEML retired its use of gendered language such as his/her. MoEML uses the singular, gender-neutral pronouns they, their, and them in cases where gender is irrelevant or unknown. (JJ)↑

Cite this page

MLA citation

Landels-Gruenewald, Tye, Janelle Jenstad, and Kate LeBere. Encode Persons. The Map of Early Modern London, edited by Janelle Jenstad, U of Victoria, 20 Jun. 2018, mapoflondon.uvic.ca/encode_persons.htm.

Chicago citation

Landels-Gruenewald, Tye, Janelle Jenstad, and Kate LeBere. Encode Persons. The Map of Early Modern London. Ed. Janelle Jenstad. Victoria: University of Victoria. Accessed June 20, 2018. http://mapoflondon.uvic.ca/encode_persons.htm.

APA citation

Landels-Gruenewald, T., Jenstad, J., & LeBere, K. 2018. Encode Persons. In J. Jenstad (Ed), The Map of Early Modern London. Victoria: University of Victoria. Retrieved from http://mapoflondon.uvic.ca/encode_persons.htm.

RIS file (for RefMan, EndNote etc.)

Provider: University of Victoria
Database: The Map of Early Modern London
Content: text/plain; charset="utf-8"

TY  - ELEC
A1  - Landels-Gruenewald, Tye
A1  - Jenstad, Janelle
A1  - LeBere, Kate
ED  - Jenstad, Janelle
T1  - Encode Persons
T2  - The Map of Early Modern London
PY  - 2018
DA  - 2018/06/20
CY  - Victoria
PB  - University of Victoria
LA  - English
UR  - http://mapoflondon.uvic.ca/encode_persons.htm
UR  - http://mapoflondon.uvic.ca/xml/standalone/encode_persons.xml
ER  -

RefWorks

RT Web Page
SR Electronic(1)
A1 Landels-Gruenewald, Tye
A1 Jenstad, Janelle
A1 LeBere, Kate
A6 Jenstad, Janelle
T1 Encode Persons
T2 The Map of Early Modern London
WP 2018
FD 2018/06/20
RD 2018/06/20
PP Victoria
PB University of Victoria
LA English
OL English
LK http://mapoflondon.uvic.ca/encode_persons.htm

TEI citation

<bibl type="mla"><author><name ref="#LAND2"><surname>Landels-Gruenewald</surname>, <forename>Tye</forename></name></author>, <author><name ref="#JENS1"><forename>Janelle</forename> <surname>Jenstad</surname></name></author>, and <author><name ref="#LEBE1"><forename>Kate</forename> <surname>LeBere</surname></name></author>. <title level="a">Encode Persons</title>. <title level="m">The Map of Early Modern London</title>, edited by <editor><name ref="#JENS1"><forename>Janelle</forename> <surname>Jenstad</surname></name></editor>, <publisher>U of Victoria</publisher>, <date when="2018-06-20">20 Jun. 2018</date>, <ref target="http://mapoflondon.uvic.ca/encode_persons.htm">mapoflondon.uvic.ca/encode_persons.htm</ref>.</bibl>

Personography