Receiving functionality that FOLIO needs to stay competitive
(UXPROD-3438)
|
|
| Status: | In Refinement |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Ramsons (R2 2024) | Parent: | Receiving functionality that FOLIO needs to stay competitive |
| Type: | New Feature | Priority: | P2 |
| Reporter: | Dennis Bridges | Assignee: | Dennis Bridges |
| Resolution: | Unresolved | Votes: | 4 |
| Labels: | IC_review, LC-priority1, SolutionArchitecture, acquisitions, crossapp, loc, patron-ux, rtac | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Release: | Ramsons (R2 2024) | ||||||||||||||||
| Epic Link: | Receiving functionality that FOLIO needs to stay competitive | ||||||||||||||||
| Front End Estimate: | Medium < 5 days | ||||||||||||||||
| Front End Estimator: | Yury Saukou | ||||||||||||||||
| Front-End Confidence factor: | 90% | ||||||||||||||||
| Back End Estimate: | Medium < 5 days | ||||||||||||||||
| Back End Estimator: | Serhii_Nosko | ||||||||||||||||
| Back-End Confidence factor: | 100% | ||||||||||||||||
| Estimation Notes and Assumptions: | RTAC development has been split out into a separate feature. UI estimate accounts for issue that may arise in other teams UI module | ||||||||||||||||
| Development Team: | Thunderjet | ||||||||||||||||
| PO Rank: | 148 | ||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R2 | ||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||||||||||
| Rank: Duke (Full Sum 2021): | R4 | ||||||||||||||||
| Rank: MI State-Lib of MI (Sum 2021): | R2 | ||||||||||||||||
| Description |
|
Current situation or problem: Pieces received with no item record in inventory can now be represented on Holdings records. In this case there is STILL no indication in the public interface that these materials have been received. This information is important for patron workflows. In scope Retrieve information for pieces that are flagged as "Display on holdings" and NOT "Suppress from discovery" and display them in public interface Out of scope Use case(s) Use cases:
Proposed solution/stories Expose pieces API in edge-orders module Store needed detail in Holding record so system get all info in 1 call - Then manage data synchronization via messaging service between orders and inventory Links to additional info https://folio-org.atlassian.net/wiki/x/VCQV Updated MIRO design analysis https://miro.com/app/board/uXjVMkjOlnc=/?share_link_id=843393418514 Questions What public facing services are these use cases relevant for? VuFind, EDS, Locate, Blacklight etc. |
| Comments |
| Comment by Dennis Bridges [ 08/Sep/23 ] |
|
Blocked because it needs to be discussed with other development teams. Inventory/OAIPMH/locate etc. |
| Comment by Dennis Bridges [ 25/Sep/23 ] |
|
Discussing with Dev teams has revealed that this will require work both on FOLIO side and third party side. Need to evaluate how this data can be surfaced. |
| Comment by Dennis Bridges [ 19/Oct/23 ] |
|
Release assignment updated to Ramsons as the initial phase of deployment will not include discovery |