Functionality and Gap Analysis for UCB Museums

Owned by MarlitaK (Unlicensed)
Last updated: Jul 04, 2011 by Michael T. BlackVersion comment

The early deployers of CollectionSpace are working together to perform a functionality and gap analysis.  The goal of this is to identify capabilities needed by one or more collections that are not available in the CollectionSpace 1.0 release. In some cases, the functionality identified is on the CollectionSpace 2.0 roadmap or relates very closely to existing or planned work.  In other cases, however, these capabilities will need to be built as part of local or partnered development projects.

Steps

  • Get high level definition followed by use cases and diagrams so we understand these better. Follow CollectionSpace dev/design process so it is easier to fit into the work stream.  (Start with level of detail and kind of information in the requirements template.)
  • Prioritize different parts of these.  In most cases, it is expected that where existing data need to be migrated, those areas will be given highest priority.   However, it is really up to the customer.
  • Talk with other IMLS deployment teams about whether this is needed by other deployments.
  • Work with CollectionSpace technical lead to do a high level architecture and technical assessment (service/app/UI, big/medium/small).
  • Talk with CollectionSpace core team (via project manager) about how this relates to the general CollectionSpace 2.0 roadmap.
  • Add work streams to a project plan, balancing against available resources and project time allotted to custom development.

Goals

  • Identify enough about each area so we understand the kind of work needed.
  • Assess reuse: What is truly unique vs needed by others.
  • Determine relative priority of different needs.
  • Gather this information in a way that it can feed into design and development cycles smoothly.

Requirements

While organized by the institution that initially identified this in discussions with them, many of these overlap with requirements for other deploying collections.  In some cases, overlapping stories for multiple collections have already been combined into a single document (e.g., data import and data export).  Other collections are welcome to add their user stories to existing requirements documents, or add questions and notes to those documents to help us decide whether this is part of the same requirement or something new. 

The order below is not meant to imply priorities or sequencing of actual work.

Phoebe A. Hearst Museum of Anthropology

UCJEPS museum-specific requirements

History of Art Visual Resource Collection

  • Visual resource collections information model (i.e., work-image aspect for image-based collections)
  • Getty vocabularies (to be written) -- incorporate AAT, ULAN, and TGN vobacularies (HAVRC subscription), and handle local extensions
  • Bibliography and citations
  • Web site for collections (to be written) -- access levels based on UC (or UCB) membership, faculty harvesting of images for teaching
  • Data export -- VRA Core 4 metadata interoperability
  • Media handling integration with DAM and ECM
  • pre-VRC images - cataloging and access (to be written, less structured metadata for an older set of records)
  • Faculty image ordering procedure (to be written and compared to Intake and Acquisition procedures)
  • Subject authority
  • Web statistics for viewing of images

UCB-other museum-specific requirements