Receiving and Checking-in Materials based on Purchase Orders and Purchase Order Lines (UXPROD-1146)

[UXPROD-2373] Allow for the display of piece information on Holding records in inventory Created: 31/Mar/20  Updated: 05/Apr/22  Resolved: 25/Nov/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Kiwi (R3 2021)
Parent: Receiving and Checking-in Materials based on Purchase Orders and Purchase Order Lines

Type: New Feature Priority: P1
Reporter: Dennis Bridges Assignee: Dennis Bridges
Resolution: Done Votes: 0
Labels: acquisitions, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by MODORDERS-575 No way to create piece for pending or... Closed
is defined by MODORDERS-576 Holding is created for piece when Cre... Closed
is defined by MODORDERS-577 Unopen doesn't remove pieces Closed
is defined by MODORDERS-578 Holding is created for order line whe... Closed
is defined by MODORDERS-579 POL Quantity not updated when piece i... Closed
is defined by MODORDERS-580 POL location not updated when piece l... Closed
is defined by MODORDERS-606 Pieces with no location can be delete... Closed
is defined by UIOR-821 Creating order for Electronic only re... Closed
is defined by UIOR-836 Update manually add pieces for receiv... Closed
is defined by UIREC-172 Display Holding OR Location name in l... Closed
is defined by UIREC-174 Disable add and remove piece when ord... Closed
is defined by UIREC-175 Confirm if user would like to delete ... Closed
is defined by UIREC-181 Confirm user would like to delete hol... Closed
is defined by UIREC-182 Display "Invalid reference" when Hold... Closed
is defined by UIREC-186 Receiving: Update manually add pieces... Closed
is defined by UISACQCOMP-59 Support: Display "Invalid reference" ... Closed
is defined by MODORDERS-534 Define and implement business API for... Closed
is defined by MODORDERS-535 Take into consideration "holdingId" o... Closed
is defined by MODORDERS-572 Piece update/receive : support locati... Closed
is defined by MODORDERS-583 Item not created when editing piece Closed
is defined by MODORDERS-584 User can remove last unit of quantity... Closed
is defined by MODORDERS-604 Display 0 value when order quantity is 0 Closed
is defined by MODORDERS-607 Can't edit caption or enumeration etc... Closed
is defined by MODORDSTOR-240 Add new fields to receiving history v... Closed
is defined by MODORDSTOR-244 Update piece schema to include Copy n... Closed
is defined by UIIN-1502 Retrieve and display select Piece inf... Closed
is defined by UIIN-1632 Update Received piece table columns Closed
is defined by UIOR-824 User can't edit opened POL when last ... Closed
is defined by UIREC-133 Allow user to select holding or locat... Closed
is defined by UIREC-135 Update create, edit and receive piece... Closed
is defined by UIREC-152 Connect items created for pieces to h... Closed
is defined by UIREC-158 Update Received/Expected piece table ... Closed
is defined by UIREC-159 Save piece toast message Closed
is defined by UIREC-160 Display Copy number, Enumeration AND ... Closed
is defined by UIREC-162 Piece location/holding field adjustments Closed
is defined by UIREC-163 Display order line locations on piece... Closed
is defined by UISACQCOMP-40 Component to handle holdings and loca... Closed
is defined by UISACQCOMP-53 Support: Display order line locations... Closed
is defined by UIOR-795 `useLineHoldings` hook usage from `st... Closed
is defined by MODORDSTOR-235 Add field to Piece schema for support... Closed
Gantt End to Start
has to be done after UXPROD-1925 Holdings: Display of POL number, Orde... Closed
Relates
relates to UIREC-178 Do not show "Display on holdings" whe... Closed
relates to UXPROD-1647 Theme: Ability to maintain relationsh... Open
relates to UXPROD-1608 Inventory. Holdings record, Accordion... Closed
relates to UXPROD-194 Checkin Maintenance (managing pieces ... In Refinement
Epic Link: Receiving and Checking-in Materials based on Purchase Orders and Purchase Order Lines
Front End Estimate: XXL < 30 days
Front-End Confidence factor: Low
Back End Estimate: XXL < 30 days
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
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:

  1. 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
  2. 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.
  3. 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.
  4. 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
  5. Librarian my reference the receipt date as a means of troubleshooting why nothing has been received recently.
  6. 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://folio-org.atlassian.net/wiki/display/FOLIJET/Display+piece+information+on+Inventory+holdings+record



 Comments   
Comment by Martina.Schildt [ 23/Apr/20 ]

The GBV ranking refers to the display of piece information in discovery from Receiving App.
Display in Inventory is not necessary for us. In discovery, the information on received pieces should be displayed via the information available in Receiving App.

Comment by Dennis Bridges [ 12/May/21 ]

Now that we have defined the work for completing UXPROD-1925 Closed it is clear that this feature will need to be moved to the Kiwi release. As described by the linked feature this work has to be done after UXPROD-1925 Closed .

Comment by Dennis Bridges [ 25/Nov/21 ]

All issue resolved and verified in bugfest-kiwi

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