Forums » Data Migration, Import/Export, Interoperability

Associating Metadata With Batch Uploaded Files

(5 posts)
  • Started 3 months ago by AJMillion
  • Latest reply from TomScheinfeldt
  1. 3 months ago # | |

    I have been toying around with the Omeka dropbox plugin and would like to thank the support staff for providing it. The tool provides an easy way to batch import files; something very useful. :) That said, I was wondering if there is a way to quickly associate metadata with batch uploads? I know that Omeka associates unique item id keys to new uploaded items (I assume this has to do with the underlying database) so associating files and information should be as simple as mapping the correct information. But, this doesn't necessarily make it easy.

    Anyone have a clue on this?

  2. 3 months ago # | |

    Hi AJMillion. There is currently no way to associate metadata with individual items during batch uploads, but it's a good idea and one that should be implemented. We're currently working on a CSV Import plugin that will import items from a CSV file into Omeka (although for the moment it's taking a back seat to our upcoming OAI-PMH harvester). Maybe we can somehow tie in the CSV plugin to the Dropbox plugin, which would allow simultaneous file and metadata import.

    In the meantime I think you're limited to using the Dropbox plugin to batch upload files and separately editing the individual items. Not quite an efficient process, but It'll get the job done. Do you have any other ideas?

  3. 3 months ago # | |

    Jsafley,

    Thanks for responding. The CSV support would be a good step, because anyone exporting/importing metadata will likely be able to convert other formats into this one. Another idea would be to enable the use of XML, but as with all of these formats I suspect the issue of precise mapping might come up.

    The CSV / batch idea is a good one. I used something similar last year while working on an archival project but it was much less flexible. A tech rigged it up so we could import a bunch of old files. We used the .jpg file names to associate the two prior to our uploading. It worked fine.

    I'm just interested in finding ways to batch process large amounts of images (to see how Omeka handles). I know it's designed to be "museum like," but if the style sheets are configured correctly and images are properly arranged, then I don't see how it couldn't start to cross over into "archive-land."

  4. 2 months ago # | |

    I too am interested in the possibility of batch uploading at least image files and associated metadata. So, I would second Jsafley's comments. In my case, I am already a CONTENTdm user, but the presentation interface for Omeka makes is very attractive. However, the process of adding metadata, one field, one item at a time would really be a painful method, IMHO.

    Is there documentation on how the OAI-PMH harvester is designed to function? I'm thinking that might make some sort of viable way to use my Cdm collections and frontend them with Omeka. (maybe I'm all wet here.

  5. 2 months ago # | |

    Hi bethnicol --

    In addition to a CSV importer and the generalized OAI-PMH harvester (we're still too deep in research and development to provide any documentation), we are working towards a specialized a set of CONTENTdm migration tools. We cannot provide a firm date for when these tools will be ready, but they are high on our list of priorities for the spring and early summer. We will make an announcement as soon as a beta version is ready.

    Thanks for using Omeka and letting us know how you're making out.

    Tom

RSS feed for this topic

Reply

You must log in to post.