Bulk load images and metadata

Needed by whom and when

PAHMA: Some functions needed by the time they move to CollectionSpace as their production system

Overview

PAHMA (and presumably other collections) sometimes need to load a large number ("hundreds") of images into their collection management system and associate them with object records.  Metadata about the specimens would exist as a spreadsheet or list of information.  Note that Michael said that while this capability is needed on day one, he thought initially it would be fine if a programmer could do this for them. Eventually they would like a user interface however.

Question: Are we talking about existing objects, new objects, or both? Which is most important?

Question: Does this include only identifiers or some link between file name and object identifier or might it contain other object metadata?

Prioritization of user stories

As definitions and priorities are clarified, the user stories above should be moved into relative order below.

Must have for 1.x-MUSEUM (when they go live in system)

Placeholder for required functionality.  As a general rule, functionality that you need and use now should go here or where you have existing data.  However, this is up to the museum.  We will have to balance requirements against resources and timelines.

Placeholder

MUSEUM could wait six to twelve months

What could wait?  These will be re-prioritized at a later date.

Placeholder

MUSEUM would like to have this eventually

These are nice to have but not a near term requirement.

Placeholder