We are developing the map functionality of this site to serve multiple purposes. It is designed to help the user to understand the geography of the Viola Muse Digital Edition, as well as function as a visual interface into the collection. In a broader sense, we hope to develop a tool for exploring the geography of nineteenth-century and early twentieth century and interrogating relationships between race and the management of urban space.

Our approach remains in development, but we outline below our initial plan.

Data structure

individual documents document-place-instance-list place-list map-place-instance-list map-list
Each instance of a place  tagged manually   A list, generated via an XSLT transformation, of all instances of all places across the documents. This file contains the identifier of the corresponding document and the id of the place assigned in place-list. A list, maintained manually, of all places mentioned in the collection. For each place, this file contains a unique id, canonical name, and address and description where appropriate. A list, maintained manually, of instances of a place to which we direct users on the maps. This file contains the id of the map and the id of the place, as well as the coordinate/grid information needed to locate the place on the map in question.   A list, maintained manually, of all the maps used to visualize the geography of the collection. This file contains a unique id and the bibliographic data for each map.
A list, generated via an XSLT transformation, of all places, with links to all textual and map instances

We are using several maps, including a contemporary GIS-based map, nineteenth-century maps by Augustus Koch (1876) and J. Francis Le Baron (1885 and 1887), as well the 1930 planning map by George Simmons. Metadata regarding these maps, along with a unique identifier for each, is stored in the master file map-list.xml.We likewise have created a list of canonical entries and metadata, including unique identifiers, for all places mentioned across the collection. This master list is contained in the file place-list.xml.In the XML files that contain the editions of the individual documents, all place names are tagged as discussed above under Semantic Markup and each contains a <ptr> element, relating it to the corresponding entry in place-list-xml.Another master file, map-place-instance-list.xml, associates each item in place-list.xml to the occurrences we wish to highlight on the various maps. We use a series of XSLT transformations to produce from the aforementioned files an index relating each canonical place in place-list-xml to all of its occurrences in both the documents and the maps. The transformation contained in create-document-place-instance-list.xsl generates a list of all occurrences of places names across the collection, which is placed in the intermediate file document-place-instance-list.xml. The transformation contained in create-place-index.xsl merges the contents of place-list.xml, document-place-instance-list.xml, and map-place-instance-list.xml, which results in a complete list of all places containing links to the items in the collection where each place is mentioned, as well as links the map or maps where that location can be viewed. That resulting file is place-index.xml.When changes need to be made, we do not edit directly any of the files produced through the XSLT transformations: document-place-instance-list.xml, map-place-instance-list.xml, and place-index.xml. We instead make the modifications in the master files listed above, and then re-run the XSLT transformations.We generate the contemporary GIS-based map by extracting the necessary information from place-list.xml and map-place-instance-list.xml, using the transformation contained in map-locations-for-upload.xsl and importing those locations into the map. While we are not using an open–source platform for this map, we retain control of our data, and if needed, can switch platforms by changing a limited number of items in the xslt transformations and re-uploading the location information elsewhere.We have created georeferenced versions of the historical maps, and handle the correlation of place names to locations on those map through a mostly manual, custom process. Where appropriate, we have divided locations on each map into layers. On our GIS-based map, for instance, we place in a separate layer the homes of Muse's interviewees and informers. We have provided the categories needed for this separation using @type on the entries in place-list.xml. The nomenclature of types used here differs from that used for @subtype on the &lt;name type="place"&gt; entries in the individual XML files of the documents, as this division is done to indicate how they should be displayed on the maps, not to describe the nature of the references themselves.


individual documents place-index maps

With respect to examining the geography of the collection, the documents, the place-index, and the map themselves can all serve as points of entry. By clicking on a reference to a place in a document, the user arrives at the corresponding entry in the place index, from where they can navigate to other documents that mention that same place, as well as to maps where the location is represented. Such multi-directional navigation can also originate from the place-index itself or from any of the maps.