Make receiving data available through RTAC for Unbound issues
Description
Priority
Fix versions
Development Team
Dreamliner
Assignee

Solution Architect
None
NoneParent Field Value
None
Parent Status
None
continues
defines
Checklist
hideTestRail: Results
Activity
Show:

Elli Bruce October 10, 2024 at 6:41 PM
This work was completed, being led by w/ Dreamliner. We tracked it Rally via F82789

Khalilah Gambrell October 9, 2024 at 8:33 PM
[like] Khalilah Gambrell reacted to your message:

Dennis Bridges October 9, 2024 at 6:31 PM
The only change tJet have made to RTAC were made under to support serials workflows. This feature was intended to support Location implementation that will display piece data for material that is not yet bound and thus doesn’t not have accurate item representation.

Dennis Bridges October 9, 2024 at 6:28 PM
no this has not been completed. Locate POs are analyzing how to retrieve piece data from FOLIO but no work has be done in RTAC to expose this data. They may now be planning to use the piece APIs directly but I am not certain.
This feature was assigned to Dreamliner for analysis.

Khalilah Gambrell October 8, 2024 at 12:54 PM
Hey - is this work complete?
Details
Details
Reporter

PO Rank
148
Release
Ramsons (R2 2024)
Rank: Cornell (Full Sum 2021)
R2
Rank: MI State-Lib of MI (Sum 2021)
R2
Rank: Chicago (MVP Sum 2020)
R2
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created January 23, 2024 at 3:26 PM
Updated October 10, 2024 at 6:43 PM
TestRail: Cases
TestRail: Runs
Current situation or problem:
Pieces received with no item record in inventory can now be represented on Holdings records. In this case there is STILL no indication in the public interface that these materials have been received. This information is important for patron workflows.
In scope
Retrieve all Holdings for a given instance
Retrieve all pieces for each given Holdings that are flagged as "Display to public" = true and “Bound" = false. Follow on feature for Locate to display them in public interface
Out of scope
Use case(s)
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 may 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.
Proposed solution/stories
Call pieces API for a given Holdings UUID and retrieve all pieces that are "Display on holdings" = true AND "Suppress from discovery" = false AND "Bound" = false
-Store needed detail in Holding record so system get all info in 1 call - Then manage data synchronization via messaging service between orders and inventory-
Links to additional info
https://folio-org.atlassian.net/wiki/x/VCQV
Updated MIRO design analysis https://miro.com/app/board/uXjVMkjOlnc=/?share_link_id=843393418514
Questions
What public facing services are these use cases relevant for? VuFind, EDS, Locate, Blacklight etc.