Receiving functionality that FOLIO needs to stay competitive (UXPROD-3438)

[UXPROD-4093] Support for physical materials to be bound Created: 23/Feb/23  Updated: 05/Feb/24

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: PNG File 1-receiving-detail-view.png     PNG File 2-select-items-to-bind (1).png     PNG File 4-receiving-success.png     PNG File 5-inventory.png    
Issue links:
Defines
is defined by MODINV-958 Add new item status like "At bindery" Open
is defined by MODORDERS-1014 Add "Bindery active" flag in POL with... Open
is defined by MODORDERS-1015 Implement endpoints to bind multiple ... Open
is defined by MODORDERS-1016 Implement bind_piece_item table and A... Open
is defined by MODORDSTOR-375 Implement endpoint to get bound piece... Open
is defined by MODORDSTOR-376 Create "Bound" flag for receiving pieces Open
is defined by UIIN-2760 Display receiving titles in bound ite... Draft
is defined by UIOR-1211 Create "Bindery active" flag in POL Draft
is defined by UIREC-321 Bind items screen Draft
is defined by UIREC-322 Create Bound items accordion in recei... Draft
is defined by UIREC-323 Add bindery active facet to receiving Draft
is defined by UIREC-263 Create "Bound" flag for receiving pieces In Refinement
is defined by UIREC-264 Bound filtering actions in receiving app In Refinement
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

  • Modify existing receiving app
  • Create new Bindery app
  • Identify unbound materials based on receiving history
  • Library determines issues to bind together
  • Holdings management
  • Binding and re-binding of monographs
  • Creation of "At bindery" status

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


Generated at Fri Feb 09 00:37:13 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.