SPIKE Investigate why some items are not included in the hold shelf clearance report

Description

Overview:

Massey reported that some items were not showing up in the hold shelf clearance report that should have been in the report. I have been looking into this and trying to test out what could be going wrong. It seems like for the item to show up in the report it must meet these requirements: item status = 'Awaiting pickup' request status = 'Closed - cancelled' or 'Closed - Pickup expired' no other request in the queue OR no other requests in the request queue with status = 'Open - awaiting pickup' pick up service point must be the current service point that is logged in I am pretty sure these rules are correct but they could be slightly incorrect or there could be additional rules that I am unaware of.

Brooks Travis did some testing and found that the hold shelf clearance report was working correctly for Kiwi-bugfest but for Massey he found an example of where it was working incorrectly. For the Online Service Point for Massey, item 1061736581 and item 1002022571 meet all the above requirements and should show up in the hold shelf clearance report but do not.

Here is the api call: https://okapi-massey.folio.ebsco.com/circulation/requests-reports/hold-shelf-clearance/3bc7c5a4-b18d-43b7-8075-3d8245b9a69a this is returning: { "requests" : [ ], "totalRecords" : 0 } Can someone take a look and see why these two items are not showing up in the hold shelf clearance report? This is hard to test for other more active service points for Massey since the requests and status for these items changes frequently. It could be that the hold shelf clearance report is working properly and there is a rule that I do not know about?

Acceptance Criteria: find out why items are not included into the report

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Mykyta Varenyk June 1, 2022 at 2:41 PM
Edited

The problem consisted in that the job is being called for all of the tenants, and so when the timer is being fired for okapi for two tenants at the same time, two update transactions are executed at the same time and unrepeatable read phenomena occurs. This can be fixed by running the job just for a specific tenant in the code.

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Vega

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created May 16, 2022 at 8:33 AM
Updated June 2, 2022 at 8:44 AM
Resolved June 1, 2022 at 2:41 PM
TestRail: Cases
TestRail: Runs