Ordering functionality that FOLIO needs to stay competitive
(UXPROD-3440)
|
|
| Status: | Analysis Complete |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Quesnelia (R1 2024) | Parent: | Ordering functionality that FOLIO needs to stay competitive |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Joseph Reimers | Assignee: | Joseph Reimers |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | loc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Potential Workaround: | Acquisition units | ||||||||||||||||||||||||||||||||||||||||||||||||
| Release: | Quesnelia (R1 2024) | ||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Ordering functionality that FOLIO needs to stay competitive | ||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimate: | XL < 15 days | ||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimator: | Alisher Musurmonov | ||||||||||||||||||||||||||||||||||||||||||||||||
| Front-End Confidence factor: | 70% | ||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | Medium < 5 days | ||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimator: | Serhii_Nosko | ||||||||||||||||||||||||||||||||||||||||||||||||
| Back-End Confidence factor: | 80% | ||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Thunderjet | ||||||||||||||||||||||||||||||||||||||||||||||||
| UX Lead: | Joseph Reimers | ||||||||||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Current situation or problem: Libraries often associate funds with specific locations (including campuses, libraries, and library locations.) Additionally, many FOLIO users are members of consortia or similar shared systems and need to associate funds with their collections. Acquisitions units provide an alternative, but can be overly complex and cumbersome and apply more restrictions than needed In scope
Out of scope
Use case(s) Library has funds exclusively designated to be used in specific places or collections (e.g. Architecture funds exclusively for Architecture purposes). Library wishes to avoid mis-application of Architecture funds to non-Architecture locations, so library location-restricts these funds to the Architecture library. Library consortium on shared system needs to align their own funds with their own institutions but each institution requires additional, more complex uses of acquisition units. Associating funds to institutions will help streamline overall management while respecting institutional autonomy. Existing records should not be impacted Proposed solution/stories
Links to additional info https://miro.com/app/board/uXjVMh40l4w=/?moveToWidget=3458764566655555829&cot=14 Questions |