[Koha-bugs] [Bug 14549] New: Reserve not removed when issued to member that is not in Priority # 1 position and comes via the “invalid” reserve queue

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14549

            Bug ID: 14549
           Summary: Reserve not removed when issued to member that is not
                    in Priority # 1 position and comes via the “invalid”
                    reserve queue
 Change sponsored?: ---
           Product: Koha
           Version: 3.14
          Hardware: PC
                OS: Windows
            Status: NEW
          Severity: major
          Priority: P5 - low
         Component: Hold requests
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: amanda.kelly at charteredaccountantsanz.com
        QA Contact: testopia at bugs.koha-community.org
                CC: gmcharlt at gmail.com

Created attachment 41048
  -->
http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=41048&action=edit
shows AU member is Priority #1 and NZ member in #2 position

This is not the issue described in this bug: (2830
Hold not removed when "trapped" item on hold shelf is checked out to a
different patron in the holds queue
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2830 / [Signed off]
bug_2830: Remove reserve when checking out if the borrower is not the first one
in the reserve queue (13.54 KB, patch) 
2011-11-17 16:57 UTC, Liz Rea
http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=6329 
)
 It is a new “bug” that comes about, I believe, because we have an “invalid”
reserves queue.  

We have a library in Australia and a library in New Zealand.  We have merged
our biblio records and commissioned work to make Koha differentiate between a
reserve placed by an AU member and a reserve placed by a NZ member.  They sit
in the one reserve queue and are numbered 1,2,3 with the Pickup Library matched
to where the member lives.  The system knows to match AU book with AU member
and same with NZ. 

All works perfectly fine when the reserve is known because the book is
returned– this flags that a reserve is waiting and we confirm the reserve. 

The problem occurs because we have a new feature called the “Invalid Reserves
Queue”.  It is a report to show where a reserve is a mismatch, ie. An AU member
reserves a NZ book and vice versa.

So problem occurs when the reserve is found via the “Invalid Reserves Queue"
then it behaves differently.  If it is a NZ book we choose the next NZ member. 
However because they are not in Priority # 1 the reserve remains behind even
though we have issued the book to them.  

So it is similar to these other bugs in that the checkout of the book does not
remove the reserve because it is not in Priority No. 1 but it only happens if
the reserve comes up via the Invalid queue as it works perfectly fine in all
other circumstances.    

Hoping there are libraries that operate in this fashion and if so has anyone
seen and resolved this issue?

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.