About

Producer

Sharon M. Leon is an Associate Professor of History at Michigan State University, where she is developing projects on digital public history and digital networking projects related to enslaved communities in Maryland. She is the director of the Omeka suite of web publishing platforms. She is a principle participant in MSU’s Consortium on Critical Diversity in a Digital Age Research initiative. Leon received her bachelors of arts degree in American Studies from Georgetown University in 1997 and her doctorate in American Studies from the University of Minnesota in 2004. Her first book, An Image of God: the Catholic Struggle with Eugenics, was published by University of Chicago Press (May 2013). Prior to joining the History Department at MSU, Leon spent over thirteen years in George Mason University’s History Department at the Roy Rosenzweig Center for History and New Media as Director of Public Projects, where she oversaw collaborations with library, museum, and archive partners from around the country.

Collections Consulted

Research was conducted in the following collections, housed at the Booth Family Center for Special Collections at Georgetown University Library:

Research Goals

In contrast to the approach that an individual genealogist or descendant might take to the materials, I am working to understand the community as a whole across all the Jesuit-owned farms during the period before the major sale in 1838. In addition to the traditional historical methods of archival research, I am using linked data, digital visualizations, and perhaps social network analysis to provide both a micro and macro view of the community and its experiences. Thus, I am experimenting with visualization techniques to offer a macro-level entry point to these individuals and their relationships that will allow both scholars and members of the interested public to get a sense of the whole community over time. I am approaching this work with several key questions:

Audience

I have been conducting this work with a number of key audiences in mind. First, there is a clear public audience who has a deep interest in the specific stories of the enslaved community owned by the Maryland Province Jesuits: the descendants of that enslaved community. As the process moves forward to identify and connect with the descendants, I want this material to be clearly accessible to them so they have, as much as possible, an understanding of their ancestors time in Maryland. The larger community of Georgetown University alumni and students form a related public audience for the work. Second, I view the project as making a major contribution to the larger effort of universities studying their history with slavery. In addition to the specific data and history of this community, the work offers a sample data model for describing and publishing data about enslaved individuals and their activities that any university could use with their own archival materials. Finally, given the depth of documentary evidence available about this community, I envision this work being useful to scholars of slavery in the Chesapeake and scholars of U.S. Catholicism.

Data Processing

I am creating a derived (meso-level) data set that will hopefully yield significant findings about the lives of this particular community of enslaved people. In reviewing the records, I have been in search of evidence of family status and formation, life cycle events such as birth, marriage, and death, shifts in freedom status and ownership, travel, health events, daily conditions, and labor and economic transactions. The individual farm and Georgetown College account ledgers have been particularly fruitful because they list individual day-to-day transactions about supplies, clothing, hiring, and healthcare in minute detail. They also occasionally include inventory lists of the people present at the various sites. The ledgers are necessarily uneven in their coverage and detail because they were created by many, many hands as the Jesuit personnel who managed the farms changed over time. Additionally, there a good number of contractual documents to support major transactions, such as sales and inheritances. The proceedings of the Corporation of Roman Catholic Clergyman include any resolutions approved by the directors, which include planned sales, dispute resolutions, and other kinds of major transactions. These proceedings are sometimes confirmed and expanded through individual correspondence among individual Jesuits. Finally, the archival collections contain extremely important sacramental records, which provide the bulk of the data for reconstructing family and kinship networks. Having combed through these materials, I have extracted every instance of an event involving an enslaved person and I am in the process of building a linked open data repository that includes those events and the people involved in them.

Site Infrastructure

This project uses Omeka S as its core infrastructure. Omeka S offers the ability to use the URIs for other Omeka S Resources as descriptive values within metadata fields, in essence linking one Omeka S Resource to another (i.e. using a Person type Resource for Martha Washington as the value for the Creator field in the description of a Text type Resource). Alternatively, a user could input a URI for an external resource (i.e. Martha Washington's DBPedia page). Omeka also makes it possible for users to attach media to Resources in three ways: through a simple file upload, through the use of an embed code from an outside resource, or use of a URI for an existing resource. Users creating many Items using the same LOD vocabulary properties can create a Resource Description Template to make the description process more efficient.

Thus, in preparation for importing my data, I created three resource templates that represented the data model for my content types (people, events, and locations). Resource template can be formed by selecting properties from any existing linked data schema. My templates combine properties from DCMI Terms and Type, FOAF, and from Bio, Relationship, and Schema, which I imported for this project.

 

Prev Next