Consider 100 holds instead of 10 at op-capture

when using fifo holds strategy and rules which limit which copies can
transit for holds (such as age hold protection), your 10 next holds
may all be unsuitable for capture.

TADL had previously run with this change in production without issue
(though we had limited it to "only when fifo is in use" since others
in the consortium were not using fifo holds.

Signed-off-by: Jeff Godin <jgodin@tadl.org>

diff --git a/Open-ILS/src/perlmods/lib/OpenILS/Application/Circ/Holds.pm b/Open-ILS/src/perlmods/lib/OpenILS/Application/Circ/Holds.pm
index 2a3a4e3..4bc6632 100644 (file)
--- a/Open-ILS/src/perlmods/lib/OpenILS/Application/Circ/Holds.pm
+++ b/Open-ILS/src/perlmods/lib/OpenILS/Application/Circ/Holds.pm
@@ -2678,7 +2678,7 @@ sub find_nearest_permitted_hold {
        # search for what should be the best holds for this copy to fulfill
        my $best_holds = $U->storagereq(
         "open-ils.storage.action.hold_request.nearest_hold.atomic", 
-               $user->ws_ou, $copy->id, 10, $hold_stall_interval, $fifo );
+               $user->ws_ou, $copy->id, 100, $hold_stall_interval, $fifo );
 
        unless(@$best_holds) {