[Koha-bugs] [Bug 31557] New: Hold queue/home vs. holding library/transport cost matrix complications

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

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31557

            Bug ID: 31557
           Summary: Hold queue/home vs. holding library/transport cost
                    matrix complications
 Change sponsored?: ---
           Product: Koha
           Version: 21.11
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: Circulation
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: sbrown at bywatersolutions.com
        QA Contact: testopia at bugs.koha-community.org
                CC: gmcharlt at gmail.com, kyle.m.hall at gmail.com

It would be helpful if build_holds_queue.pl either 1) checked items' holding
libraries in addition to home when items float, or 2) used the Transport Cost
Matrix instead when systems have it enabled. Using home library only/first
results in higher 'costs' and in holds being filled more slowly than necessary,
and can be confusing for libraries.

Home/holding:
If I understand correctly, build_holds_queue.pl looks for items whose home
library matches the hold's pickup library (plus accounting for any preferences
set in StaticHoldsQueueWeight/HoldsQueueSkipClosed/RandomizeHoldsQueueWeight). 
For example, in a system where items float, a hold to be picked up at West
library has the following items:
Item 1: Home library West, holding library East
Item 2: Home library West, holding library West
Item 3: Home library North, holding library West

If build_holds_queue.pl sees Item 1 first, it will be placed on East's queue to
send to West even though Item 2 is already at West and could fill the hold more
efficiently.

Then since the Transport Cost Matrix is only consulted if no available items
have a home library matching the hold's pickup library, holds are filled in a
more 'expensive' way than libraries may expect. Using the Transport Cost Matrix
directly would address this.

For example, in a system where items float and a hold is to be picked up at
South:
Item 1: Home library East, holding library South
Item 2: Home library West, holding library West
Item 3: Home library South, holding library West

build_holds_queue.pl will see that Item 3 has a home library matching the
pickup library and will place it on West's queue to send to South. If
build_holds_queue.pl consulted the Transport Cost Matrix, Item 1 would be
placed on South's queue with no transfer necessary.

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