[Koha-bugs] [Bug 13165] New: Active Hold Limit

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

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

            Bug ID: 13165
           Summary: Active Hold Limit
 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: cbrannon at cdalibrary.org
        QA Contact: testopia at bugs.koha-community.org
                CC: gmcharlt at gmail.com

I would love to see holds updated to act kind of like the Netflix DVD queue
system.  The system could be configured for individual library control or
global control where a limit is set of how many holds can be active for an
individual patron.  All other hold requests are queued.  Patrons can go in to
their accounts and rearrange the order of priority on their holds queue.

The only question would be, should the holds queue advance when a hold has been
filled or picked up, or should it wait until a held item has been returned?  

The first method would simply stagger delays in holding, and not really help
with hording of items.  The patron would be picking up groups of holds
separately rather than all together.

The second method would mean that holds would need to be marked in the issues
table somehow, in order to keep track of how many holds the patron has on hand,
and to differentiate from regular checkouts.

So maybe instead the limit should be based off the total number of items and
holds the patron has altogether.  For example, the patron has a limit of 25
items that can be checked out/held.  They currently have 15 items checked out,
and therefore can only have 10 active holds.  Maybe 8 items come in and are
checked out, resulting in 23 items checked out and 2 items on hold.  Nothing
moves in the queue until something is checked back in or an active hold that
hasn't been filled is cancelled.

Just an idea.  Would love to hear input on this.

Christopher

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