Media handling integration with DAM and ECM

Owned by Chris Hoffman
Last updated: Apr 20, 2011Version comment
2 min read

Needed by whom and when

Basic statements about who needs the functionality and by when.

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

Overview

Many UCB collections have broader image and other media file handling needs than a collection management system can provide, and it is recognized that collections owners need the services provided by content management systems, digital asset management systems, archives and repositories.  Currently, most of the integration among these systems is done by hand, requiring that museum staff keep track separately of what is stored where.  Occasionally point-to-point integration programs are used to coordinate and track images that are stored in one place and occasionally copied elsewhere.  There is growing acceptance of using the OAI-PMH protocol for repository interoperability.

Media handling integration with DAM and ECM UCB user stories for prioritization

Media handling integration with DAM and ECM: User can upload a new image file from disk and then mark image as ready for deposit in an external DAM, ECM or repository system.  System will kick off workflow to deposit image and metadata in external system.  Stable URL and transaction details sent back to and stored in CollectionSpace.

Media handling integration with DAM and ECM: System will reconcile metadata stored in CollectionSpace about media files with metadata about media files stored in an external DAM, ECM or repository.

Media handling integration with DAM and ECM: User can batch upload a set of media files stored in an external system using a listing of stable URLs.  CollectionSpace will create media file records pointing to stable URL, creating derivatives as needed.  Imported media file records will contain relevant metadata that can be used to create object records or link to existing object records.

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