Showing posts with label omeka. Show all posts
Showing posts with label omeka. Show all posts

Tuesday, July 28, 2015

An Archival Conundrum

I am nearing the finish line. At least, the finish line of uploading our backlog of photographs onto the baltimoreuprising2015.org website. When the Maryland Historical Society (MdHS) originally put out the call for photographs, they received an overwhelming response, but they had nowhere to put the astounding contributions. Contributors were instructed to send images to MdHS via dropbox. When I arrived on the scene, the Historical Society dropbox had over a thousand images shared to their account. The first things I had to do when I began my work, was download the files off dropbox to a physical hard drive and catalog each person's contributions and corresponding metadata. In a couple of days, I was able to do this. The Hard drive contained every contribution and were organized into files for each contributor. Once all of the images were stored offline and documented, I had to start uploading those images to the baltimoreuprising2015.org website.
The baltimoreuprising2015.org site is built using Omeka. Omeka is a Content Management System (CMS). Collections, series, and exhibits can all be constructed through Omeka, but it all starts with a digital archive of “items” stored on the Omeka site. For each photograph on the hard drive, I had to upload it to the website and provide the necessary metadata such as description, title, creator, date, etcetera. Making sure each image, audio file, or video is uploaded correctly, has the correct provenance information, and is organized within the archive in a way that it can be retrieved by users has been my most time consuming task.
I am pleased with the number of contributors and the magnitude of the contributions. The size of the archive is larger than my most optimistic projections at the start. It is not enough, however, for the archive to simply be large. It also must be usable. Most descriptions, titles, and subjects for items that were provided by contributors were vague and confusing. There was little continuity from one collection to the next, which made it difficult for the whole archive to be searched. Although we wanted to preserve the artistic intention of the content creators, we also want the site to be a resource. Our compromise has been to keep the title and description of photos how the creator indicated, but to limit the subjects of items to a controlled vocabulary. Now, when users contribute to the archive, they have to select from a limited list of subjects. What this means for researchers is that they can click on the subject of any one item, and be able to see all the items with that same subject.
Our decision to limit subjects at first might seem minute, but it actually represents a continuous struggle for archives both digital and physical. What is the right balance between preservation and accessibility? In one sense, the item subject could be seen as an important interpretive component that needs to be preserved to reflect the contributors complete artistic vision. On the other hand, the purpose of preservation is almost always to ensure long term usefulness for future generations. Consistent categories and labels are the only way a repository of almost 2,000 items can be made searchable for future users. Ultimately, we tried to find a balance between the two ideals, but tended to favor access.