Bug 10243: (follow-up) prevent TransportCostMatrix from overriding library holds policy
Using the TransportCostMatrix can cause the same issue. Removing the last ditch use of the first item causes the the subroutine to continue with the traditional matching, which will respect the hold policies. Signed-off-by: Galen Charlton <gmc@esilibrary.com>
This commit is contained in:
parent
e74b91165d
commit
06ea76c3c2
1 changed files with 0 additions and 1 deletions
|
@ -448,7 +448,6 @@ sub MapItemsToHoldRequests {
|
|||
$itemnumber = $item->{itemnumber};
|
||||
last;
|
||||
}
|
||||
$itemnumber ||= $holding_branch_items->[0]->{itemnumber};
|
||||
}
|
||||
else {
|
||||
warn "No transport costs for $pickup_branch";
|
||||
|
|
Loading…
Reference in a new issue