Bug 5912 - Hold queue 'jump'
Summary: Hold queue 'jump'
Status: CLOSED WONTFIX
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: 3.4
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Srdjan Jankovic
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks: 5609
  Show dependency treegraph
 
Reported: 2011-03-21 00:23 UTC by Srdjan Jankovic
Modified: 2014-12-07 20:02 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Srdjan Jankovic 2011-03-21 00:23:37 UTC

    
Comment 1 Srdjan Jankovic 2011-03-21 00:24:32 UTC
A setting should be configurable which permits the library to establish a point in the holds queue when a patron may get a copy of the item requested because it has been returned to their specified pick-up location even if they are not the top name on the holds queue.

Use case: Many libraries are spending hundreds of thousands of dollars moving material between libraries so a balance needs to be found between what is fair to patrons and what is economically manageable for libraries. If a patron is number 30 in a queue of 100 people waiting for the newest Harry Potter and a copy is returned to that patron’s pick-up location, the patron doesn’t get it. The item will only be made available to the person specified as #1 on the holds list. This seems fair. But what if that patron was #5 on the list, would it be reasonable to save the library money in delivery and let the #5 patron have it? This is the idea behind allowing libraries to specify a setting which would permit a patron to get the next copy that becomes available at their pick-up location. Each library needs to be able to figure out what they can justify. Some will want to say, you can jump the queue if you item is returned to your pick up location as long as you are in the top 10, others might say you have to be the top 2 or 3.
Comment 2 Paul Poulain 2012-09-06 12:28:16 UTC
Hi Srdjan,

This bug entry is 18 months old. Is there some code coming, or is it abandonned ? (we -BibLibre- are listing all pending improvements we could work on -see bug 8362- and try to find dependencies/conflicts)
Comment 3 Chris Cormack 2012-09-06 20:52:38 UTC
This is is work that was never funded.
Comment 4 Srdjan Jankovic 2012-09-06 23:33:59 UTC
Yes, it was meant to be a post-5911 enhancement.