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

[UXPROD-4087] Create Routing List for physical pieces in receiving Created: 22/Feb/23  Updated: 06/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: P2
Reporter: Joseph Reimers Assignee: Joseph Reimers
Resolution: Unresolved Votes: 0
Labels: IC_review, LC-priority3, SolutionArchitecture, acq-sig-topics, galileo, loc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File 4-new-routing-list-save.png     PNG File 5-pol-routing-list-view-mode-success.png     PNG File 7-receiving-routing-list-detail-view.png     PNG File screenshot-1.png    
Issue links:
Defines
is defined by MODORDERS-1006 Create Routing Lists API Open
is defined by MODORDSTOR-364 Create routing_list table and API for it Open
is defined by MODORDSTOR-367 Create routing_address table and API ... Open
is defined by UIREC-328 Create accordion for Routing Open
is defined by UIOR-1113 Add notes to routing list Closed
is defined by UIOR-1112 Prioritize users in a routing list Draft
is defined by UIOR-1109 Create accordion for Routing In Refinement
is defined by UIOR-1111 Add Users to routing list In Refinement
is defined by UIOR-1191 Create routing list In Refinement
is defined by UIREC-299 Routing behavior in receiving In Refinement
is defined by UIREC-300 Routing configuration In Refinement
Relates
relates to UXPROD-4088 Print routing list for physical piece... Draft
Release: Ramsons (R2 2024)
Epic Link: Receiving functionality that FOLIO needs to stay competitive
Front End Estimate: XL < 15 days
Front End Estimator: Alisher Musurmonov
Front-End Confidence factor: 90%
Back End Estimate: Large < 10 days
Back End Estimator: Serhii_Nosko
Back-End Confidence factor: 90%
Development Team: Thunderjet
Report Functional Area(s):
Resource Management
PO Rank: 147
Rank: Cornell (Full Sum 2021): R5

 Description   

Current situation or problem: Some libraries receive materials to be routed to assorted users or departments outside the normal scope of circulation, and without necessarily adding these pieces to the collection or making them otherwise discoverable. Similarly, libraries may need to route materials to alternate locations for in-processing or other special handling. Libraries need to manage routing of those materials.

In scope

Designate materials for routing
Create the list of Users for routing
Manage Holdings to display or suppress routed materials
Account for materials acquired and routed but not added to the library's collection

Out of scope

Receiving pieces, printing the list, managing publication patterns

Use case(s)

https://folio-org.atlassian.net/wiki/x/NBJU

Proposed solution/stories

https://miro.com/app/board/uXjVPmkrKfI=/

Links to additional info

 

Questions


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