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: