Bug 7030 - Define maximum number of holds on branch level
Summary: Define maximum number of holds on branch level
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Kyle M Hall
QA Contact: Bugs List
URL:
Keywords:
Depends on: 4045
Blocks:
  Show dependency tree / graph
 
Reported: 2011-10-14 12:42 UTC by Nicole C. Engard
Modified: 2020-01-06 20:17 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:
Circulation function:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nicole C. Engard 2011-10-14 12:42:01 UTC 
We have a field for the maximum number of items that can be checked out (regardless of item type/patron category) and I think we should have the same for holds.
Comment 1 Nicole C. Engard 2011-10-14 13:18:42 UTC 

*** This bug has been marked as a duplicate of bug 4045 ***
Comment 2 Nicole C. Engard 2011-10-14 13:21:32 UTC 
While this is related to bug 4045, I'm suggesting that this preference be moved to the circ matrix so it can be done branch by branch.
Comment 3 Marc Véron 2015-12-20 17:25:29 UTC 
Still valid?
Comment 4 Owen Leonard 2015-12-21 14:55:15 UTC 
This bug is still valid, because there is no setting in circulation and fine rules for defining a maximum number of holds across all item types/patrons.
Comment 5 Marc Véron 2015-12-21 15:01:58 UTC 
What is the role of syspref 'maxreserves'? (In reply to Owen Leonard from comment #4)
> This bug is still valid, because there is no setting in circulation and fine
> rules for defining a maximum number of holds across all item types/patrons.

Is that not covered by the system preference 'maxreserves'?
Comment 6 Owen Leonard 2015-12-21 15:11:42 UTC 
(In reply to Marc Véron from comment #5)
> Is that not covered by the system preference 'maxreserves'?

The system preference 'maxreserves' is a maximum across all libraries, itemtypes, and patrons. This request is for something which is configurable per library but covers all itemtypes and patrons at that library.
Comment 7 Marc Véron 2015-12-21 15:54:56 UTC 
(In reply to Owen Leonard from comment #6)
> (In reply to Marc Véron from comment #5)
> > Is that not covered by the system preference 'maxreserves'?
> 
> The system preference 'maxreserves' is a maximum across all libraries,
> itemtypes, and patrons. This request is for something which is configurable
> per library but covers all itemtypes and patrons at that library.

Hi Owen, thanks for the clarification, I did not properly read comment #2. 
I changed the bug title a little bit.

Would that be a new column in the table branch_borrower_circ_rules?
Comment 8 Marc Véron 2015-12-21 16:01:24 UTC 
...and default_borrower_circ_rules, I suppose.
Comment 9 Katrin Fischer 2019-04-28 22:47:50 UTC 
I believe this has been fixed, we have the max number of holds in all 3 tables on circulation conditions now.