Bug 13924 - LocalHoldsPriority needs dateaccessioned limits.
Summary: LocalHoldsPriority needs dateaccessioned limits.
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 12632
Blocks:
  Show dependency treegraph
 
Reported: 2015-03-27 19:58 UTC by Christopher Brannon
Modified: 2016-06-15 17:09 UTC (History)
4 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 Christopher Brannon 2015-03-27 19:58:39 UTC
LocalHoldsPriority needs to have another parameter to limit by number of days since dateaccessioned date.

We have several libraries that need the LocalHoldsPriority on, but in doing so, have found that very popular items, such as video games or video streaming devices never leave our library because we always have someone from our library with a hold on them.  It would be great to have this new parameter, so new items (which is what we tend to want the LocalHoldsPriority for) would be priority at their home branch, but maybe 6 weeks or 2 months later they don't have to be.

Christopher
Comment 1 Kyle M Hall 2015-07-09 18:24:51 UTC
I imagine a good solution would be to move the LocalHoldsPriority settings to the circulation rules. That way you could give new items a different itemtype than older items such that the new items honor LocalHoldsPriority and the older items do not. This would only work if bug 12632 is a dependency.