Attachment 28328 Details for Bug 12287 – Bug 12287 - Hold priority for new hold incorrect if record has holds in transit

[patch] Bug 12287 - Hold priority for new hold incorrect if record has holds in transit

Bug-12287---Hold-priority-for-new-hold-incorrect-i.patch (text/plain), 1.19 KB, created by Kyle M Hall (khall) on 2014-05-19 11:05:37 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Kyle M Hall (khall)

Created: 2014-05-19 11:05:37 UTC

Size: 1.19 KB

patch

obsolete

>From c9f55cda5b050a49b2d9e3a7ac8770682637f0a1 Mon Sep 17 00:00:00 2001
>From: Kyle M Hall <kyle@bywatersolutions.com>
>Date: Mon, 19 May 2014 07:01:58 -0400
>Subject: [PATCH] Bug 12287 - Hold priority for new hold incorrect if record has holds in transit
>
>When placing a new hold, the listed priority for the hold will be
>incorrect if there are any holds with items in transit ( i.e. found = T ).
>
>Test Plan:
>1) Place 3 holds on a record with at least 2 items
>2) Fill one hold so it is marked as waiting
>3) Fill on hold so it is marked as in transit
>4) Begin placing a new hold
>5) Note the expected priority would be 2, but is actually 3
>6) Apply this patch
>7) Reload the patch, now the expected priority shows correctly
>---
> reserve/request.pl |    2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
>diff --git a/reserve/request.pl b/reserve/request.pl
>index 1b303c7..3749091 100755
>--- a/reserve/request.pl
>+++ b/reserve/request.pl
>@@ -203,7 +203,7 @@ foreach my $biblionumber (@biblionumbers) {
>     my $alreadyreserved = 0;
> 
>     foreach my $res (@$reserves) {
>-        if ( defined $res->{found} && $res->{found} eq 'W' ) {
>+        if ( defined $res->{found} ) {
>             $count--;
>         }
> 
>-- 
>1.7.2.5

Actions: View | Diff | Splinter Review

Attachments on bug 12287: 28328 | 28634 | 29911 | 29912