Saved groups or sets

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

Needed by whom and when

Basic statements about who needs the functionality and by when.

PAHMA: This is probably critical for PAHMA on day one.  They use a TMS functionality called "object packages".

Overview

PAHMA and UCJEPS (and presumably other collections) need to create and save sets of records and then perform operations on those sets.  There is therefore a relationship to batch processing.  PAHMA uses a capability called object packaging in their current system to work with sets of "5 things or 5000".  Create a set and apply a note to all objects in the set, or to move them to an exhibit, loan, etc.

Saved sets can alternatively be implemented as a shopping cart metaphor.

Unknown macro: {multi-excerpt}

Saved Groups or Sets UCB user stories for prioritization

Saved groups or sets: User may identify and save a set of object records.

Saved groups or sets: User may identify and save a set of procedure records (e.g., loan out transactions). Question: Do we need saved sets for image records?

Saved groups or sets: User may add other records (objects or procedures) to the set.  User may remove records from the set.

Saved groups or sets: While browsing a list of object records (e.g., following a search), user can select objects (multi-select checkboxes) and save them to a saved set or shopping cart or favorites.

Saved groups or sets: User may share sets with other users.

Saved groups or sets: User may remove their own set.

Saved groups or sets: Administrative user may manage sets belonging to other users.

Saved groups or sets: User may perform some action on the saved set.  See the batch processing page.

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