[Bug 32778] New: Auto-unsuspended holds do do not trigger realtime holds
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32778 Bug ID: 32778 Summary: Auto-unsuspended holds do do not trigger realtime holds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs@lists.koha-community.org Reporter: Laura.escamilla@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com Auto-unsuspended holds, or future holds, do not trigger the RealTimeHolds queue updates. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32778 Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emily.lamancusa@montgomeryc | |ountymd.gov -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32778 Lisette Scheer <lisette.scheer@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lisette.scheer@bywatersolut | |ions.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32778 koha-US bug tracker <bugzilla@koha-us.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugzilla@koha-us.org -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32778 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Auto-unsuspended holds do |Auto-unsuspended holds do |do not trigger realtime |not trigger realt-ime holds |holds |queue update -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32778 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|minor |normal -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32778 Sally <sally.healey@cheshiresharedservices.gov.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sally.healey@cheshireshared | |services.gov.uk -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32778 Liz Rea <wizzyrea@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wizzyrea@gmail.com --- Comment #1 from Liz Rea <wizzyrea@gmail.com> --- An easy fix for this is to add a single forced run of the holds queue to the early morning hours after the auto-unsuspend job runs, to force these onto the list. We should add that to our default cron.daily/koha-common cron definition. And also fix the unsuspend job to tickle the real time hold queue. Just belt and bracers. Cheers, Liz -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32778 Sarah Cornell <sbcornell@cityofportsmouth.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbcornell@cityofportsmouth. | |com --- Comment #2 from Sarah Cornell <sbcornell@cityofportsmouth.com> --- This is happening more and more often as our patrons get used to setting hold start dates and suspending holds. I'd love to get this fixed ASAP! We discover the hold when another patron brings the item to the desk, and that is very disconcerting for everyone involved. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32778 Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> --- Hi Sarah! A new cron job option was added on bug 32565 that should address this. *** This bug has been marked as a duplicate of bug 32565 *** -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32778 Pedro Amorim <pedro.amorim@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pedro.amorim@ptfs-europe.co | |m --- Comment #4 from Pedro Amorim <pedro.amorim@ptfs-europe.com> --- (In reply to Liz Rea from comment #1)
We should add that to our default cron.daily/koha-common cron definition.
I agree, bug 32565 implements the new cron options but does not actually add the cron entry to the default koha-common cron definition. I believe the new cron entry needs to be added manually. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32778 --- Comment #5 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Pedro Amorim from comment #4)
(In reply to Liz Rea from comment #1)
We should add that to our default cron.daily/koha-common cron definition.
I agree, bug 32565 implements the new cron options but does not actually add the cron entry to the default koha-common cron definition. I believe the new cron entry needs to be added manually.
I think if we add the unallocated param, we also need to make sure that the RealTimeHoldsQueue is activated in new installations by default as they "play together". Should we do that? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32778 Pedro Amorim <pedro.amorim@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nick@bywatersolutions.com --- Comment #6 from Pedro Amorim <pedro.amorim@ptfs-europe.com> --- (In reply to Katrin Fischer from comment #5)
I think if we add the unallocated param, we also need to make sure that the RealTimeHoldsQueue is activated in new installations by default as they "play together".
Should we do that?
That's a good point, I was of the mindset that having the new cron entry added by default would never cause harm, RTHQ or not, but I believe Nick explained why that isn't the case in bug 32565. I like the idea of having RTHQ on by default on new installations but I'm not entirely sure of the possible consequences of this. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32778 --- Comment #7 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Pedro Amorim from comment #6)
(In reply to Katrin Fischer from comment #5)
I think if we add the unallocated param, we also need to make sure that the RealTimeHoldsQueue is activated in new installations by default as they "play together".
Should we do that?
That's a good point, I was of the mindset that having the new cron entry added by default would never cause harm, RTHQ or not, but I believe Nick explained why that isn't the case in bug 32565. I like the idea of having RTHQ on by default on new installations but I'm not entirely sure of the possible consequences of this.
Maybe something we should discuss with Nick. I think we either keep the "total rebuild" and RTHQ off or we turn it on and add the --unallocated to the nightly rebuild. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org