Bug 5785 - Holds should catch new acquisitions
Summary: Holds should catch new acquisitions
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement with 1 vote (vote)
Assignee: Kyle M Hall
QA Contact: Bugs List
URL:
Keywords:
: 10440 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-02-21 19:33 UTC by Jared Camins-Esakov
Modified: 2023-12-28 20:43 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jared Camins-Esakov 2011-02-21 19:33:02 UTC
When a new item is added to a bib with bib-level holds, the holds system is not triggered by the new item, even though it should be (if the item type permits holds according to the circulation rules).
Comment 1 Katrin Fischer 2019-04-10 00:33:56 UTC
I am not sure about what was the intended behavior here. We display information about holds in acq. Once an item is ready for checkout, it's usually returned and triggers the hold. The checkin can also be used to remove a 'processing' status.

I am not sure when the hold should be caught otherwise - on receive would be too early as getting items ready might take a few days depending on workflows.
Comment 2 Katrin Fischer 2022-02-19 18:30:27 UTC
*** Bug 10440 has been marked as a duplicate of this bug. ***
Comment 3 Katrin Fischer 2023-01-07 23:26:15 UTC
I imagine Jared meant that the item should show up on the holds queue and I assume with RealTimeHoldsQueue it will now as every change to the record/items will trigger an update.

See:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29346#c15