Needed by whom and when
Basic statements about who needs the functionality and by when.
UCB: Several museums need to track the status of sub-loans, i.e., individual objects that are part of a set of objects in a loan transaction. Often, subsets of the loan will come back at different time (if they come back at all).
Overview
UCMP, Essig, HAVRC, and PAHMA all have mentioned this need.
| Wiki Markup |
|---|
{multi-excerpt:name=subobjects-ucb}
h3. Sub-loan UCB user stories for prioritization
Sub-loans: For individual objects that are part of a loan-out transaction, the institution can track
* Requirements (e.g., no destructive sampling)
* Status (e.g., returned, extended)
* Sub-loan status date
* and possibly other domain-specific fields
{multi-excerpt} |
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