History of changes
- Chris Hoffman
Needed by whom and when
Basic statements about who needs the functionality and by when.
PAHMA: Some functions needed by the time they move to CollectionSpace as their production system
Overview
PAHMA needs to be able to obtain information about who made what changes and when to all records (objects, procedures, vocabularies).
Question: Are there specific fields on records that also need to be audited?
Question: Do ALL records need to be audited in this manner?
Audit and History of Changes UCB user stories for prioritization
History of changes: System retains history of create and change dates and IDs on all records (objects, procedures, vocabularies).
History of changes: Programmer can produce a listing of changes for certain time periods and/or certain record types.
History of changes: User with appropriate permissions can view history of changes for records.
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