Visual resource collections information model
Needed by whom and when
Basic statements about who needs the functionality and by when.
Visual resource collections: Some functions needed by the time they move to CollectionSpace as their production system
Overview
HAVRC and other visual resource collections differ from other collections in that they are primarily concerned with the digital images that are the center of their collection. Whether they have slides or work with borne-digital, the digital images are increasingly their emphasis. So the user interface should be based on the image. At the same time, visual resource collections also "catalog" the works that are pictured in an image. For example, an image could depict a statue and a building. In addition to the image itself, visual resource collections staff will need catalog records for the statue and the building. The images and the works are related in a many-to-many way (i.e., the same statue could be the work depicted in another image, perhaps a painting.) Also, the standard data exchange format for visual resource collections (VRA Core) uses the same records to describe images and works. For an acquisition workflow for the History of Art Visual Resource Collection, see the HAVRC use case on the CollectionSpace wiki.
In a discussion with Megan, Penelope, and Jan Eklund on October 20, this all seemed feasible.
User stories for definition
Please feel to rewrite these or eliminate completely! Then move to the prioritized headings below.
Visual resource collections information model: User interface for CollectionSpace can be configured to facilitate visual resource collection image-based workflows. Question: What would this look like? Would the Create New Records screen need to be adjusted to facilitate creating image records (and retitled Cataloging Images)? Would Cataloging Records need to be retitled to be something like Cataloging Works? Would similar changes be needed on the MyCollectionSpace page?
Visual resource collections information model: Question: What other workflows should be identified?
Visual resource collections information model: Images and works can be mapped to the VRA Core standard.
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