...
Document business expectations? Where do we differ from AcquistionsAcquisitions? Some examples:
ECS handling - change ownership
Setting record for deletion
Default display (sort, number to display, how to go through more history) - endless scroll? More?
Document some user workflows (i.e. Single record overlay)
Work with Kimie to revise UX (
)Lref gdrive file url https://drive.google.com/drive/folders/17ghSSy1kvLOVGO8JzFyFJXfjbJHt8mo6 Remove “sort by”
Remove examples where the app is identified as the trigger for the change
Write user stories
...
Ability to rollback to and/or view previous versions
Ability to sort
Including the app that triggered the change
Exporting version history
Tech design
Requirements overview
Requirement | Notes | Jira(s) | |
|---|---|---|---|
| 1 | Feature toggle so that libraries can set whether the feature is enabled (applies to both FOLIO and MARC source records) |
| |
| 2 | Include version history on:
| ||
| 3 | Display the date and time of the change in local timezone | ||
| 4 | Display the source of the change (user vs system) | ||
| 5 | Identify as a “Change”, and indicate whether the field was:
| ||
| 6 | Indicate the field changed on Instances detail view for both FOLIO and MARC source records. Note: for MARC source records, the field changed should reflect the Instance field changed (see other requirement for Source view) | ||
| 7 | In Source view for MARC source records, identify the specific MARC fields (not to the point of indicators or subfields) changed | ||
| 8 | If a MARC field is changed that does NOT map to a FOLIO instance, do not include the change in the Instance detail view log | ||
| 9 | Record changes after the record has been opened (edited) for the first time | ||
| 10 | Ignore changes to metadata | ||
| 11 | Only include 20 changes in the log at a time | ||
| 12 | Present a toast message that loading additional changes may take time |
...