Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
EPAM-Veg Sprint 131
-
0.5
-
Vega
-
Lotus R1 2022
-
!!!ALL!!!, Chalmers
Description
Overview:
When creating a request using the basic TLR implementation, only ten items associated with the indicated instance are checked for availability. This leads to situations where holds are being placed on items rather than creating pages for available items (or, I assume, holds on items with longer queues).
Steps to Reproduce:
- Log in to https://folio-snapshot.dev.folio.org
- Create more than 10 items associated with a single instance
- Arrange it so that the first ten items returned by /inventory/items?query=(instance.id==<instanceId>) all have a status other than "Available" (checked out is best), and that one of the remaining is status "Available"
- Attempt to create a "title-level request" via mod-patron (eg. /patron/account/<userId>/instance/<instanceId>/hold ) for the above instance record.
Expected Results:
The request results in a Page of an available item.
Actual Results:
A hold request is created for one of the first 10 items.
Additional Information:
It's unclear, to me, how the items are being retrieved to determine which will fill the request in this case. Chalmers was able to verify the behavior in their production environment (Juniper), and I duplicated in snapshot. Best guess is a "limit=10" issue.
Workaround:
Manually reviewing request queues and moving requests to available items (labor-intensive).
URL:
Interested parties: MarieWi
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-3409 Vega - Lotus Enhancements/Bugfixes/Tech Debt
-
- Closed
-