Summary: | Items should show on the Holds Queue and Holds to Pull even if they have requested transfers | ||
---|---|---|---|
Product: | Koha | Reporter: | Andrew Fuerste-Henry <andrew> |
Component: | Hold requests | Assignee: | Martin Renvoize (ashimema) <martin.renvoize> |
Status: | Failed QA --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | gmcharlt, hebah, lisette, lisettepalouse+koha, madamyk, marie-luce.laflamme, martin.renvoize, rcoert, staceyk |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34596 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36762 |
||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 23092 | ||
Bug Blocks: | |||
Attachments: |
Bug 30581: Allow requested but not sent items to appear in holds to pull
Bug 30581: Exclude unsent transfers from HoldsQueue |
Description
Andrew Fuerste-Henry
2022-04-21 13:25:37 UTC
Staff should be alerted to holds on these items, so I agree with Andrew that they should show items in the Holds Queue and Holds to Pull if they have transfers that are requested but not sent. Agreed... this causes a lot of problems since the item in question is really in limbo, similar to an orphaned hold. I 'think' this is a duplicate of bug 33761.. any chance someone could test with that and confirm my suspicions? (In reply to Martin Renvoize from comment #3) > I 'think' this is a duplicate of bug 33761.. any chance someone could test > with that and confirm my suspicions? I can confirm that this issue still exists in master after bug 33761. To recreate: 1 - have a bib with an available item 2 - place a hold on that bib 3 - confirm your item shows up on the holds queue 4 - use the Transfers interface to send the item to another branch (you'll be asked to confirm that you want to send it even though there's a hold) 5 - log into the SQL server and delete datesent from your transfer to kick it back to Pending (in the real world, an item would end up in this state due to stock rotation) 6 - confirm that the holdings table on your bib shows the item has a pending transfer 7 - confirm the title isn't on the holds queue anymore (run build_holds_queue if not using the realtime queue) 8 - check the item in and confirm that it does trigger the hold We use the stock rotation feature, and books that are in transit pending status will not show up on the Holds report. This is an issue as our branches can have delays in pulling books for stock rotation. (In reply to stacey kingsbury from comment #5) > We use the stock rotation feature, and books that are in transit pending > status will not show up on the Holds report. This is an issue as our > branches can have delays in pulling books for stock rotation. The 'Transfers to send' report was actually designed specifically for the stock rotation use case Created attachment 166064 [details] [review] Bug 30581: Allow requested but not sent items to appear in holds to pull This patch adds datesent to the exclusions in holds to pull report. Created attachment 166065 [details] [review] Bug 30581: Exclude unsent transfers from HoldsQueue This adds an exclusion to remove requested but not yet sent transfers from the filter when using the Holds Queue Need testing and feedback here before I write the unit tests for it for QA. Bug 36762 is making this harder to test in that it's making it harder to transfer an item with a pending hold. I think one should still be able to test this by generating transfers-to-send with the stock rotation tool. I'll just have to remember how stock rotation works. I'm not sure if I missed a step, but Koha doesn't seem to process transfers when there is a hold at bib record or item level. So I've placed a hold, tried to copy and paste the item barcode directly into the transfer page (Circulation > Transfers) without a prior checkin attempt, and Koha hasn't processed the transfer. Notes: I've tested with the main branch and the ByWaters sandbox, and both environments failed to save the transfer. |