Quickstart: Adding PlacesAuthorLucas SimpsonAuthorKate LeBereCopy EditorJamie ZabelEncoderKate LeBereProgrammerJoey TakedaProgrammerMartin HolmesProject DirectorJanelle JenstadThe Map of Early Modern Londonhttp://mapoflondon.uvic.ca/includes.xmlVictoria, BC, CanadaDepartment of EnglishP.O.Box 3070 STNC CSCUniversity of VictoriaVictoria, BCCanadaV8W 3W12016University of Victoria978-1-55058-519-3Janelle Jenstadlondon@uvic.ca
Copyright held by
The Map of Early Modern London on behalf of the contributors.
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, Janelle Jenstad, for
specific information on the availability and licensing of content
found in files on this site.
Born digital.
Most MoEML documents, or significant fragments with xml:id attributes, can
be addressed using the 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
Early English Books Online (EEBO)
repository. Note that this is a subscription service, and may not be accessible to those
accessing it from locations outside member institutions.
Links to page-images in the
English Broadside Ballad Archive (EBBA).
The mdt (MoEML Document Type) prefix used on catRef/target points
to a central taxonomy in the includes file.
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 xml:id of the category, meaning all documents in the specified category, and one with the suffix _subcategories, meaning all subcategories of the category.
The molgls (MoEML gloss) prefix used on term/corresp points
to a a glossary entry in the GLOSS1.xml file.
This molvariant prefix is used on ref/target attributes during automated
generation of gazetteer index files. It points to an element in the generated variant spellings
listing file which lists all documents which contain a particular spelling variant for a
location.
This molajax prefix is used on ref/target attributes during the static build
process, to specify links which point to MoEML resources which should not be loaded into the source
page during standalone processing; instead, these should be turned into links to the XML source
documents, and at HTML page load time, these should be turned into AJAX calls. This is to handle
the scenario in which a page such as an A-Z index of the whole site would end up containing
virtually the whole site inside itself.
The molstow prefix is used on facs attributes to link to the HCMC verison of the Stow facsimiles.
Usually the first group is the year (1633) and then last is the image number (0001).
The molshows prefix is used on facs attributes to link to the copies of page-images
from mayoral shows stored in the london account on the HCMC server.
The first group is the year (1633), the second is the source repository, and then last is the image
file name.
The sb prefix is used on ref/target attributes to link to
Stow’s Books URLs at UToronto.
Our editorial and encoding practices are documented in detail in the Praxis section of our website.
Proofed and published.Created document.Quickstart: Adding Places
Introduction
When you come across a place that has not yet been added to MoEML, you may need to create a new location page. This document outlines how to (1) determine what constitutes a place for our project, (2) create a location file, (3) reroute a place from another place, (4) add temporal data to a location file, (5) write an abstract, and (6) cite sources within an abstract.
Determining whether to Add a Place
MoEML is concerned with documenting representations of space in the early modern social imaginary. Our temporal scope is roughly bounded by the moment just before the dissolution of the monasteries (1536) and just before the Great Fire of London (1666), two events that caused major toponymic and platial change in the city. (Note: changes resulting from the dissolution of the monasteries are significant to our project, while changes resulting from the fire are considered to be beyond the project scope.)
The representation of place in early modern London is not, however, limited to places that were physically present between 1536 and 1666. As a document like Stow’s
Survey of London makes evident, the past of a place is in many cases inseparable from its significance in the early modern social imaginary. To account for this broader conception of an early modern place, MoEML uses the following decision tree to determine whether a place should be added to our Placeography:
Two characteristics of a place (with some exceptions) determine its uniqueness within the MoEML project scope. Those are coordinates and function. A change to either of these characteristics warrants the creation of a new place (a new location document with unique xml:id). Other characteristics (e.g., name, ownership, building materials, paint colour) are considered non-essential or accidental. Changes to non-essential characteristics do not warrant the creation of a new place in our Placeography. For example, the timbers of the Theatre were moved and used in the construction of the Globe. Although the two places share certain accidental characteristics (in this case, the building material) the coordinates of the two locations are different. The two locations are therefore considered distinct and have their own unique location files. Similarly, although the Globe burned down and was rebuilt, the rebuilt Globe is not given its own location file because its essential characteristics (function and location) remain the same, even if the buildings themselves are different.
As another example, the initial headquarters of the Stationers’ Company was on Milk Street but then moved to the site of St. Peter’s College Rents in 1554 and then to the site of Pembroke’s Inn in 1611. The three halls thus have a common function and common owner but different coordinate locations. Therefore, we have separate ids and location files for the three distinct locations—Stationers’ Hall (Milk Street), Stationers’ Hall (St. Paul’s), and Stationers’ Hall (Ave Maria Lane).
Researching a place begins with determining whether to add it to the Placeography. Be sure to record this research if you determine it necessary to add the place to the Placeography so work is not repeated . See Researching Locations and Writing Abstracts for a list of helpful resources to get started.
Creating New Location Documents
Once you have determined that you need to add a new location file, follow these
steps: Determine an authority name and unique xml:id for the location.Create a new XML file in Oxygen, and save it into the appropriate alphabetical folder in
db/data/locations.Copy the text from the locations template, found in db/data/templates.
Paste it to your new XML document.Change the value of the xml:id attribute in the TEI element to your chosen xml:id for the new location (do not include the mol: prefix).Ctrl + F and replace [Add Place Name Here] with
your authority name.Follow the instructional comments. Delete the comments as you
go.Update the status attribute of the revisionDesc to draft. Another team member will proofread
the document before the next release.When writing a stub (a short encyclopedia article, around one paragraph
long), use the same text for both the abstract and the main body. Encode
dates, places, and people mentioned in your writeup. If writing a stub, in order to ensure
consistency, fully encode your abstract and then copy the
whole p element into the main body.In Terminal, navigate to locations and type svn add
FILENAME.xml. Then commit.Leave a reminder to check the page for any major problems on the Jenkins site once it goes through the build, keeping in mind that the page will still undergo
further revision by other team members before publication.Add any relevant LINKS1 entries. This will appear under the Related documents / disambiguation link at the top of the document. See Linksography (LINKS1.xml) for further details.
See Location Documents for further details on how to create location files and Location Document Template for a template of a location document.
Rerouting Closely Related Places
Our principle of adding new locations based on change of function or location sometimes means that two places whose histories are inseparably connected will still require two different location documents. In such a case, one article will contain all of the information relevant to the place and its related places, including aspects of that history that are technically about a different place in our Placeography. We call this rerouting
For example, the physical site of Charterhouse (Residence) was later used as a more general site, Charterhouse (Site). The history of these places are so interconnected that both places are best understood within the broader history of the physical site. However, because they have different functions, the two places must have different location documents. Charterhouse (Residence) is given a full-length encyclopedia entry, with different div elements describing different phases in the site’s broader history, including the information about Charterhouse (Site):
Private Residence, c. 1541–1609
Following the departure of the Carthusians, purchased the land in 1545 and began
Hospital, School, and Pensioners’ Home, 1609–Present
In 1609, Thomas Sutton, one of the wealthiest commoners in London, purchased the land
The other location file, Charterhouse (Site), is only a stub. A back element after the main body links to the relevant div in the Charterhouse (Site) article:
For a full history of the site, see the full-length article on Charterhouse (Residence).
A linkGrp with corresponding note in LINKS1 gives a succinct statement of the relation between the places. See Linksography (LINKS1.xml) for further details.
Adding Temporal Data
MoEML’s Temporal Range
The temporal range of a place is encoded in the location element of the place document’s div with a type attribute and placeInfo value. Temporal boundaries on a place means that, outside of that boundary, the place no longer exists according to MoEML’s definition of a place. This may be because of a change of function (e.g., the building was repurposed or abandoned) or a change of coordinates (relocated). Though we may record founding dates of churches and other institutions that are prior to 1536, we generally only record the dates bounding the temporal existence of a place when those boundaries land within our temporal scope. MoEML’s definition of places and their functions are particular to its own temporal scope and do not necessarily apply to all periods. For example, hospitals had evolved so drastically between 1536 and the Victorian period that the same hospital (e.g., St. Bartholomew’s Hospital, which stood through both times) might be said to have gained an entirely new function as time progressed. Therefore, changes to the existence of a place that occur outside of MoEML’s scope are left to be determined by other projects with their own conceptions of platial ontology suited to their own temporal scope.
Temporal Range Encoding Examples
Bridewell Palace was built as a royal estate in 1510. It was repurposed as a prison and
hospital in 1553. This latter change is an essential change and warrants a different location
in our Placeography, Bridewell. According to MoEML’s definition of platial existence, therefore, Bridewell Palace
existed between 1510 and 1553. The place’s location element in its div with typeplaceInfo is as follows:
Bridewell Palace
Bridewell Palace
Bridewell, the hospital and prison into which the site of Bridewell Palace was converted, was destroyed in the fire of 1666 but rebuilt and persisted into the eighteenth and nineteenth centuries. Although the building was destroyed and rebuilt, the site itself did not cease to exist under its pre-fire function after 1666. Although it eventually ceased to function as a prison in the eighteenth century, we do not encode this information. Instead, we just leave an open upper bound on the location element, as follows:
Bridewell
Researching Locations and Writing Abstracts
The following list offers helpful resources for researching places and writing encyclopedia entries. In addition to these, our major source
for all location entries are our editions of Stow’s
Survey.
General Contributors’ GuideSpecific Contributors’ Notes on Streets and SitesMoEML’s Guide for ResearchHarben (helpful resource with detailed descriptions of London places)Carlin and Belcher and 1520 Map (British Historic Towns Atlas) (helpful resource, but keep in mind that the map is from before our temporal scope. Many places may have moved between 1520 and Stow’s time)Oxford English DictionaryBritish History OnlineSugdenMoEML’s MapographyLayers of London ProjectLondon Topographical Society (see especially the websites linked from here)Museum of LondonGuildhall LibraryCollage: The London Picture ArchiveCrace Collection of Maps
Citing Sources
For a full breakdown of how to create in-text citations and link them to BIBL1.xml, see Link to Reference Material in BIBL1.xml. Below is a summary of the most important points.
These are the elements, attributes, and values you will use to tag in-text citations in location articles and abstracts:
Element: refAttributes: target, typeValues: mol:xml:id, bibl
Tag the entire parenthetical reference (excluding the parentheses themselves) with the ref element:
Throughout the early modern period, Ludgate held a number of celebrity inmates, detained for their extravagances (Heminges 8).
Always include the author’s name in the in-text citation, even if they are mentioned within the sentence:
According to Haynes, at its greatest extent the sculpture collection is said to have comprised no less than thirty-seven statues, one hundred and twenty-eight busts and two hundred and fifty inscriptions, as well as a large number of sarcophagi, altars and fragments (Haynes 10).
If the author is a historical person, tag their name with the name element and their xml:id:
Stow asserts that Ludgate was constructed by King Lud who named the gate after himself for his owne honor (Stow 1:1).
To reference a MoEML page as a bibliographic item within another MoEML page, use the ref element with a type value of mol:bibl:
Shoreditch followed Roman roads near Kingsland Road, a continuation of Ermine Street, and Old Street, a continuation of Waitling or Watling Street (Campbell).
To reference one of MoEML’s editions of Stow’s
Survey, find the xml:id of the page you want to cite in the pb element:
Then cite the page by pointing directly to the xml:id:
(Stow 1598, sig. B6v)
Make sure to include the date of the edition (1598, 1603, 1618, 1633) and signature number in your in-text citation, as done in the example above.
When citing from Harben, Sugden, or Carlin and Belcher, include the headword of the entry in your in-text citation if your information is from a different entry than the location you are writing about or if the title of the entry is notably different from MoEML’s authority name:
Fagswell was a natural well in the Clerkenwell area and a source of fresh water for inhabitants of the City of London (Harben, Water Supply of London).
For documentation on how to encode block quotations, see Encode Block Quotations.