Ordering functionality that FOLIO needs to stay competitive
(UXPROD-3440)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Sunflower (R3 2024) | Parent: | Ordering functionality that FOLIO needs to stay competitive |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Dennis Bridges | Assignee: | Dennis Bridges |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | SolutionArchitecture, acquisitions, lc-priority4, loc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Release: | Sunflower (R3 2024) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Ordering functionality that FOLIO needs to stay competitive | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimate: | XL < 15 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front-End Confidence factor: | 70% | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | XXL < 30 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back-End Confidence factor: | 70% | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Estimation Notes and Assumptions: | Confidence factor will increase after orders history has been implemented. Could be less than expected if a lot of that work can be reused. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Thunderjet | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 133 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Current situation or problem: Not enough metadata is captured regarding record activity. Some records (eg. order) are edited frequently and often by different users OR integrations. Currently it is only possible to see who last edited the organization and who created it. This can make it difficult to troubleshoot organizations over time and uncover why something is not as expected. In scope Follow implementation approach laid out for orders in
Out of scope Use case(s) A library is performing an audit and notices that correspondence does not match with organizational information on file. Tracking the organization record's version history will confirm which information is the most current. A library needs to know the organizational contact person who last negotiated the library's contract, as it was not a current contact. Proposed solution/stories Follow the implementation approach as laid out in
Links to additional info Miro board: https://miro.com/app/board/uXjVMauMKGo=/?share_link_id=157479086509 Organization change log analysis in wiki at https://folio-org.atlassian.net/wiki/x/uwhU (Related) Order change log analysis in wiki at https://folio-org.atlassian.net/wiki/x/agVU |