- UXPROD-204Getting issue details... STATUS
Problem(s):
- Order numbers in FOLIO can live for multiple fiscal years. Ongoing orders have a tendency to change over time and ideally users can edit things like publish and vendor reference numbers. Not knowing what the recent edit are can make orders confusing and delete old numbers etc means sacrificing historical information that could be valuable for acquisitions workflows.
Use Cases & Requirements:
Requirement | Status | Use cases |
---|---|---|
User is shown what field was edited and when it was edited, in local timezone | PENDING | When updating vendor reference number on account of a publisher or platform change the library needs to know what is the most current vendor number. When managing integrations having multiple numbers that could be a match point would be problematic. Users should be able to replace these without loosing the original historical information. |
User is shown what the original value was and what new value was input | PENDING | When non-repeatable fields are changed we loose track of what the original value was. Perhaps the publisher changes or the assignee changes etc. knowing who was originally assigned to the order makes it easier to recover knowledge |
User can filter through list of changes | PENDING | Over time many things can change on an order. After ten years it can be difficult to navigate the edit history, making it possible to loose information that you actually have in the system. |
Proposed workflow:
Option 1
The "change log" live in an accordion on the record (Possible performance issue)
Option 2
User clicks records action menu
Action menu includes "Change log"
User is presented the change log in a full screen overlay
Questions:
Question | Status | Conclusion | Comments |
---|---|---|---|
Should change log include user information? Would it need to be masked in some cases? | OPEN |