From f3c9560aeab1a74dfd175d2e379ee232220079b9 Mon Sep 17 00:00:00 2001 From: Kyle M Hall Date: Fri, 21 Feb 2020 09:41:27 -0500 Subject: [PATCH] Bug 24705: Holds placed via SIP will be given first priority Content-Type: text/plain; charset=utf-8 The SIP server does not calculate and pass a priority to AddReserve, which causes the hold to be given priority 1. Test Plan: 1) Place a hold via SIP for a record with existing holds 2) Note the new hold is top priority 3) Apply this patch 4) Restart SIP 5) Repeat step 1 6) New hold should be last priority Signed-off-by: Christofer Zorn Signed-off-by: Jonathan Druart Signed-off-by: Martin Renvoize Signed-off-by: Marcel de Rooy --- C4/SIP/ILS/Transaction/Hold.pm | 2 ++ 1 file changed, 2 insertions(+) diff --git a/C4/SIP/ILS/Transaction/Hold.pm b/C4/SIP/ILS/Transaction/Hold.pm index ecf8416640..d51ebde199 100644 --- a/C4/SIP/ILS/Transaction/Hold.pm +++ b/C4/SIP/ILS/Transaction/Hold.pm @@ -66,8 +66,10 @@ sub do_hold { return $self; } + my $priority = C4::Reserves::CalculatePriority($item->biblionumber); AddReserve( { + priority => $priority, branch => $branch, borrowernumber => $patron->borrowernumber, biblionumber => $item->biblionumber -- 2.11.0