From e3ff5ceb430c6f09273151074049369ed4dbb98a Mon Sep 17 00:00:00 2001 From: Jeff Godin Date: Tue, 22 May 2012 09:44:21 -0400 Subject: [PATCH] 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 --- Open-ILS/src/perlmods/lib/OpenILS/Application/Circ/Holds.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 2a3a4e37d8..4bc6632566 100644 --- 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) { -- 2.11.0