UCB requirements Feb 2011

Owned by Chris Hoffman
Last updated: Aug 16, 2011Version comment

Note: The following user stories are in draft form.  They represent several high priority areas based on discussions with PAHMA, UCJEPS, and HAVRC.  These are being described so that local development teams can work on design and ask questions.  See the note below about the broader set of deployment-related needs.

  1. Image media viewing: On Media record, File Name is a link (or has a link displayed) to the original file (e.g., the tiff or larger jpeg) so that user can bring up the original image in the same or new window or tab using browser controls.
  2. Interim custom authority for scientific name: For UCJEPS-Seaweed project, initially, a non-hierarchical vocabulary is needed to hold about 1000 names; they need to be able to add terms; it would be very helpful to be able to add fields to the authority such as parent term, author, and so on.  This is not intended to be a full taxonomy authority, but a placeholder for what is needed for the project.
  3. Saved sets or groups: User can import a list of object numbers (or paste them into CollectionSpace) to create a saved set of objects. The saved set will have a user-defined name (or be called "shopping cart" or "favorites") and will persist for the login session.
  4. Saved sets or groups: User can view a saved set and its members.
  5. Batch processing: For a saved set of objects, user can initiate a loans out transaction that will include relation links to the objects in the saved set.
  6. Saved sets or groups: User can add or remove items from a saved set.
  7. Saved sets or groups: User can save the results of a search to a saved set.
  8. Saved sets or groups: User can export the object numbers from a saved set to a text file.
  9. Image media viewing: Media snapshot in right pane (e.g., of Cataloging screen) is a link (or has a link displayed) to the original file (e.g., the tiff or larger jpeg) so that user can bring up the original image in the same or new window or tab using browser controls.
  10. Image media viewing: On Media record, user can specify a link to an image file stored in a separate system (e.g., a digital asset management system or repository).  This field should be repeatable and have associated attributes to be determined (e.g., date, type, note).  Therefore, the Image Record should not need to have an Image File uploaded. However, an Image Record that does have an Image File could use this field to identify where other versions of this image are deposited (e.g., CollectionSpace could have a JPEG while a repository has the TIFF).  CSpace not expected to pass authn credentials; user will authenticate if needed.
  11. Image media viewing: User can view large images in a pan-and-zoom image viewer (like tilepic, zoomify, GoogleMaps, or IIPImage).

The user stories above are a subset of the high priority requirements for UCB deployments.  Here are some notes on other areas:

  • Import: Data import is very high priority and is being worked on by the core CollectionSpace team in the 1.5 release.
  • Performance: We are testing performance with large data volumes in two CSpace 1.0 instances, and we are beginning to test performance on a 1.3 instance.  Jiras have been submitted related to performance when there are many relationships, and some work seems to be in scope on CSpace 1.5.
  • Authority bug (links to records in custom authorities not working): Some work is underway on this problem though timing of the fix is unclear (see Jiras CSPACE-3580 v1.x, CSPACE-3578 fixed in v1.8, 3579 v1.x, 3588 v1.12)
  • Hierarchical vocabularies: Many high priority requirements depend on hierarchical vocabulary capabilities (scientific taxonomy and specimen identification, place authority, storage locations, and perhaps even sub-objects).  Work on hierarchical vocabularies and storage location authority is scheduled for 1.7 and 1.8.  Because this is estimated to be in May or June, we want to accelerate this work.  At UCB, we will start with UI and design work.
  • There are additional user stories in the functional areas represented above.  Individual user stories will be prioritized in a next round.
  • Additional areas that were rated as very high priorities include those below.  Individual user stories will be prioritized in a next round.