[As Adam Soroka described in his last post, we made a shift to Omeka early in the Neatline project in order to speed development and put our work in the hands of end users already thinking about the relationship of archival collections to scholarly analysis and presentation. Omeka’s plugin architecture also allows us to share individual components of the project (such as EAD import or robust SIMILE Timeline integration) with people who might not be interested in the whole geospatial workflow of Neatline proper, and to capitalize on other Omeka-related work happening in the Scholars’ Lab. Here, Adam gives a quick update on work in progress. In a future post I’ll describe the kinds of iterative scholarly work and geo-temporal interpretive activity that Neatline is designed to promote. — Bethany]
The Neatline technical crew is hurtling onwards in our Omeka plugin rampage.
Ethan Gruber is now finishing work on his EAD Importer. This will allow folks to bring an Encoded Archival Description XML finding aid to an Omeka instance and have the documents in that archival description sprout right into the Omeka field as manipulable, annotate-able, curate-able items. We’ve successfully applied it to our two test cases (H.P. Lovecraft and Jedediah Hotchkiss) and are working through other examples.
I have been madly thrashing a geospatially-enabled duo of plugins: Neatline Maps and Neatline Features. Neatline Maps connects the powerful open-source Web GIS engine GeoServer to Omeka. It permits a user to upload georeferenced images and have them immediately available as interactive maps. Neatline Features allows users to use a simple but powerful graphical editor built on the OpenLayers library to attach sophisticated georeferenced shape information to Omeka items. This could include anything from an outline of a building to the path taken by an army brigade through a battle.
We’re well on our way to our expected May public release. — Adam