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: | P3 |
| Reporter: | Joseph Reimers | Assignee: | Joseph Reimers |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | IC_review, LC-priority3, acq-sig-topics, loc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Potential Workaround: | Joe Reimers: This could be worked in stages. Adding a simple "bindery" flag with a True/False value would be a stopgap until everything else is built up. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Release: | Ramsons (R2 2024) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Receiving functionality that FOLIO needs to stay competitive | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimate: | XL < 15 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimator: | Yury Saukou | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front-End Confidence factor: | 80% | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | XXL < 30 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimator: | Serhii_Nosko | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back-End Confidence factor: | 90% | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Thunderjet | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Report Functional Area(s): |
Resource Management
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 145 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Current situation or problem: Some libraries would like a mechanism for managing bindery operations, including identifying materials to be bound, updating holdings to reflect bound vs. unbound status, interfacing with third party bindery software and communicating the status of materials that are unavailable due to being bound. In scope: Process for identifying materials to be bound, updating holdings, creating items and managing associated statuses throughout the process. Out of scope: Bound-withs Use case(s): https://folio-org.atlassian.net/wiki/x/KhJU Proposed solution/stories
Links to additional info https://folio-org.atlassian.net/wiki/x/NwNU Line 54: Capturing binding information for order and receiving so records can be filtered by this data Miro board: https://miro.com/app/board/uXjVMavxnKk=/?share_link_id=362920099675 Initial report by 5 Colleges. Questions Potential Dependencies Inventory - Holdings Circulation - Item statuses |