Upgrade to new releases
- Chris Hoffman
Needed by whom and when
Basic statements about who needs the functionality and by when.
PAHMA and UCJEPS and UCB in general: Some capabilities needed by the time they move to CollectionSpace as their production system
Overview
At UCB, we expect to take advantage of new releases but need to be able to bring along customizations created earlier.
User stories for definition
Please feel to rewrite these or eliminate completely! Then move to the prioritized headings below.
CollectionSpace upgrade paths: When a new release of CollectionSpace is available, programmers can upgrade an existing CollectionSpace deployment and maintain schema customizations.
CollectionSpace upgrade paths: When a new release of CollectionSpace is available, programmers can upgrade an existing CollectionSpace deployment and maintain user interface customizations.
CollectionSpace upgrade paths: When a new release of CollectionSpace is available, programmers can upgrade an existing CollectionSpace deployment and maintain customized reports and data extracts.
CollectionSpace upgrade paths: When a new release of CollectionSpace is available, programmers can upgrade an existing CollectionSpace deployment and maintain interoperability capabilities and more complex extensions and customizations.
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