In our solution we’ve been using Bagit as an archive format to handle complex objects – ie multi file objects and collections, which neatly allows us to keep descriptive material and data together as well as being able to handle large datasets being stored elsewhere by reference.
So I was interested to see today that Omeka have added support for Bagit, and doubly so to see that they suggest moving the data with Dropbox.
One of our ingest models is to use curl to initiate an ingest request by transferring a load of metadata to a listener process and then initiating an upload in a quasi dropbox manner – basically using dropbox as an active filestore
The obvious trick would be generecize our process even further by using the dropbox and bagit plugins for omeka as a means of captring content (exhibitions etc) stored in omeka and archiving them …
Building an archive solution 