Details
-
Type:
New Feature
-
Status: In Review (View Workflow)
-
Priority:
P1
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: Kiwi (R3 2021)
-
Component/s: None
-
Labels:
-
Template:
-
Epic Link:
-
Front End Estimate:XXL < 30 days
-
Back End Estimate:XXL < 30 days
-
Confidence factor:Low
-
Estimation Notes and Assumptions:FE now includes changes in 3 different modules so this could be very large. BE also involves a lot of logic in different areas to update the way order handles location.
-
Development Team:Thunderjet
-
Calculated Total Rank:38
-
PO Rank:102
-
Cap Plan Fix Version (DO NOT CHANGE):R2 2021
-
Rank: Chicago (MVP Sum 2020):R2
-
Rank: Cornell (Full Sum 2021):R2
-
Rank: Duke (Full Sum 2021):R1
-
Rank: 5Colleges (Full Jul 2021):R4
-
Rank: GBV (MVP Sum 2020):R4
-
Rank: hbz (TBD):R4
-
Rank: MI State-Lib of MI (Sum 2021):R2
-
Rank: MO State (MVP June 2020):R2
-
Rank: TAMU (MVP Jan 2021):R2
-
Rank: U of AL (MVP Oct 2020):R5
Description
Problem: Some pieces are received with no items in inventory to represent them. In this case there is no indication that those materials have been received in any other application. This information may be important for discovery, managing inventory and other workflows.
Note: this feature will include an update to the interaction logic between orders and inventory regarding Holdings. Receiving pieces to a new location can in some cases result in unwanted Holdings being created. When the perm location of a Holding is change it may need to update expected pieces such that they can be received to the correct location.
Use cases:
- Print Journals (Only Physical Pieces) are checked-in for a periodical and the system is not set to create items to represent them. The librarian might be waiting to bind those things until they have enough pieces to bind and creating items may require them to be deleted once bound. The librarian wants these pieces to show in discovery as expected and ultimately as received until 1 item is created to represent them. These items would live on the self and be available for use even though there is no item record. These many be for circulation or for internal use.
- When the librarian receives these pieces they might add a public note when they indicate they want them piece to display publicly
- Patron comes to reference desk because they can't find something. Librarian wants to confirm it has been received, identify what bound volume it is included (If it has been bound yet) in and find out where that bound volume or loose issue is in the library. These librarian often will not be accessing the ILS system and Acquisitions data as they may not have creds/perms/training.
- Patron wants to confirm a material has been received, identify what bound volume it is included (If it has been bound yet) in and find out where that bound volume or loose issue is in the library.
- For some legal materials (Integrated materials) there will never be an item representing the piece being received. It may be a pocket part etc. and librarians will still need to be able to identify whether it has been received or not. This information is also displayed in discovery
- Librarian my reference the receipt date as a means of troubleshooting why nothing has been received recently.
- Patron wants to see info for a particular title. Item may have been created for piece but holding with provide additional information about what makes up that item. Eg. Current years version of chapter two has been received and added to it.
Approach:
https://wiki.folio.org/display/FOLIJET/Display+piece+information+on+Inventory+holdings+record
TestRail: Results
Attachments
Issue Links
- has to be done after
-
-
- In Review
-
- is defined by
-
MODORDERS-534
Define and implement business API for retrieving pieces information
-
- Closed
-
-
MODORDERS-535
Take into consideration "holdingId" or "locationId" when check-in/unreceive/receive pieces
-
- Closed
-
-
MODORDERS-572
Piece update : support location/holding field adjustments
-
- In Progress
-
-
MODORDSTOR-235
Add field to Piece schema for support holding
-
- Closed
-
-
MODORDSTOR-240
Add new fields to receiving history view: displayOnHolding, enumeration, chronology, discoverySuppress
-
- Closed
-
-
MODORDSTOR-244
Update piece schema to include Copy number, Enumeration AND Chronology
-
- Closed
-
-
UIIN-1502
Retrieve and display select Piece information on Holding
-
- Closed
-
-
UIIN-1632
Update Received piece table columns
-
- Closed
-
-
UIOR-795
`useLineHoldings` hook usage from `stripes-acq-components`
-
- Closed
-
-
UIREC-133
Allow user to select holding or location at point of receipt
-
- Closed
-
-
UIREC-135
Update create, edit and receive piece forms with additional fields
-
- Closed
-
-
UIREC-152
Connect items created for pieces to holdings
-
- Closed
-
-
UIREC-158
Update Received/Expected piece table columns
-
- Closed
-
-
UIREC-159
Save piece toast message
-
- Closed
-
-
UIREC-160
Display Copy number, Enumeration AND Chronology in Piece form
-
- Closed
-
-
UIREC-162
Piece location/holding field adjustments
-
- In Code Review
-
-
UIREC-163
Display order line locations on piece form
-
- Closed
-
-
UIREC-172
Display Holding OR Location name in location column in search results
-
- In Progress
-
-
UISACQCOMP-40
Component to handle holdings and locations
-
- Closed
-
-
UISACQCOMP-53
Support: Display order line locations on piece form
-
- Closed
-
- relates to
-
-
- Analysis Complete
-
-
-
- Draft
-
-
UXPROD-1647 Theme: Ability to maintain relationships between other apps when holdings/items are moved
-
- Open
-
- mentioned in
-
Page Loading...