[Koha-bugs] [Bug 14514] New: LocalHoldsPriority and the HoldsQueue conflict with each other

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

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

            Bug ID: 14514
           Summary: LocalHoldsPriority and the HoldsQueue conflict with
                    each other
 Change sponsored?: ---
           Product: Koha
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: Hold requests
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: kyle at bywatersolutions.com
        QA Contact: testopia at bugs.koha-community.org
                CC: gmcharlt at gmail.com

It appears that the LocalHoldsPriority feature and the Holds Queue are
fundamentally at odds with each other.

The problem appears to be that both are attempting to choose the best way to
fill holds. When you are using the holds queue and you check in an item that
has been selected by the holds queue builder, that part of Koha where the
LocalHoldsPriority feature lives doesn't get to see all the holds in order to
pick the best one. Instead only the hold selected by the holds queue builder is
returned so to the LocalHoldsPriority feature, that is only one hold to pick
from!

The solution *may* be to add the similar logic that appears
C4::Reserves::CheckReserves for handling local hold priority to
C4::HoldsQueue::MapItemsToHoldRequests at the very beginning before it even
attempts to match item level requests.

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