Holds Queue vs Holds to Pull
Hi all, What is the purpose of the "Holds Queue" page? As far as I can tell, it duplicates "Holds to Pull" but requires a separate cronjob and extra database tables and so on. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595
For a single-branch system, they should be the same. For a multi-branch system, Holds Queue first looks for an item already at the pickup branch and puts the hold in that branch's queue (possibly even jumping priority order if LocalHoldsPriority), or if there isn't one already at the pickup branch depending on prefs it either looks for the cheapest available item according to the Transport Cost Matrix if UseTransportCostMatrix, or chooses the first branch listed in StaticHoldsQueueWeight with an available item if StaticHoldsQueueWeight and not RandomizeHoldsQueueWeight, or chooses a random branch from those listed in StaticHoldsQueueWeight with an available item if StaticHoldsQueueWeight and RandomizeHoldsQueueWeight, or chooses a random branch from all branches with an available item if not StaticHoldsQueueWeight and RandomizeHoldsQueueWeight, or if you mess your prefs up badly enough with not StaticHoldsQueueWeight and not RandomizeHoldsQueueWeight, chooses the alphabetically-first branch with an available item, thus piling all the load on poor Aaron Aardvark Library, in each case possibly checking whether that branch is open or closed that day if HoldsQueueSkipClosed, and puts the hold in whatever branch's queue falls out of that. Phil Ringnalda Chetco Community Public Library On 3/2/2020 3:44 PM, dcook@prosentient.com.au wrote:
Hi all,
What is the purpose of the “Holds Queue” page?
As far as I can tell, it duplicates “Holds to Pull” but requires a separate cronjob and extra database tables and so on.
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St
Ultimo, NSW 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Thanks for that, Phil! The majority of my libraries are single-branch, so that explains my experiences more. I imagine that must only apply to bib-level holds and not specific item holds. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Phil Ringnalda Sent: Wednesday, 4 March 2020 10:32 AM To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Holds Queue vs Holds to Pull For a single-branch system, they should be the same. For a multi-branch system, Holds Queue first looks for an item already at the pickup branch and puts the hold in that branch's queue (possibly even jumping priority order if LocalHoldsPriority), or if there isn't one already at the pickup branch depending on prefs it either looks for the cheapest available item according to the Transport Cost Matrix if UseTransportCostMatrix, or chooses the first branch listed in StaticHoldsQueueWeight with an available item if StaticHoldsQueueWeight and not RandomizeHoldsQueueWeight, or chooses a random branch from those listed in StaticHoldsQueueWeight with an available item if StaticHoldsQueueWeight and RandomizeHoldsQueueWeight, or chooses a random branch from all branches with an available item if not StaticHoldsQueueWeight and RandomizeHoldsQueueWeight, or if you mess your prefs up badly enough with not StaticHoldsQueueWeight and not RandomizeHoldsQueueWeight, chooses the alphabetically-first branch with an available item, thus piling all the load on poor Aaron Aardvark Library, in each case possibly checking whether that branch is open or closed that day if HoldsQueueSkipClosed, and puts the hold in whatever branch's queue falls out of that. Phil Ringnalda Chetco Community Public Library On 3/2/2020 3:44 PM, dcook@prosentient.com.au <mailto:dcook@prosentient.com.au> wrote: Hi all, What is the purpose of the "Holds Queue" page? As far as I can tell, it duplicates "Holds to Pull" but requires a separate cronjob and extra database tables and so on. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Thx Phil, great explanation! On 04.03.20 00:32, Phil Ringnalda wrote:
For a single-branch system, they should be the same.
For a multi-branch system, Holds Queue first looks for an item already at the pickup branch and puts the hold in that branch's queue (possibly even jumping priority order if LocalHoldsPriority), or if there isn't one already at the pickup branch depending on prefs it either looks for the cheapest available item according to the Transport Cost Matrix if UseTransportCostMatrix, or chooses the first branch listed in StaticHoldsQueueWeight with an available item if StaticHoldsQueueWeight and not RandomizeHoldsQueueWeight, or chooses a random branch from those listed in StaticHoldsQueueWeight with an available item if StaticHoldsQueueWeight and RandomizeHoldsQueueWeight, or chooses a random branch from all branches with an available item if not StaticHoldsQueueWeight and RandomizeHoldsQueueWeight, or if you mess your prefs up badly enough with not StaticHoldsQueueWeight and not RandomizeHoldsQueueWeight, chooses the alphabetically-first branch with an available item, thus piling all the load on poor Aaron Aardvark Library, in each case possibly checking whether that branch is open or closed that day if HoldsQueueSkipClosed, and puts the hold in whatever branch's queue falls out of that.
Phil Ringnalda Chetco Community Public Library
On 3/2/2020 3:44 PM, dcook@prosentient.com.au wrote:
Hi all,
What is the purpose of the “Holds Queue” page?
As far as I can tell, it duplicates “Holds to Pull” but requires a separate cronjob and extra database tables and so on.
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St
Ultimo, NSW 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website :http://www.koha-community.org/ git :http://git.koha-community.org/ bugs :http://bugs.koha-community.org/
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
participants (3)
-
dcook＠prosentient.com.au -
Katrin Fischer -
Phil Ringnalda