Summary: | Allow holds on multiple items of selected titles | ||
---|---|---|---|
Product: | Koha | Reporter: | Jane Wagner <jwagner> |
Component: | Hold requests | Assignee: | Jane Wagner <jwagner> |
Status: | RESOLVED DUPLICATE | QA Contact: | Bugs List <koha-bugs> |
Severity: | enhancement | ||
Priority: | PATCH-Sent (DO NOT USE) | CC: | chris, gaetan.boisson, jcamins, jwagner, koha.sekjal, lculber, nengard, paul.poulain, ruth, smoreland |
Version: | 3.4 | ||
Hardware: | PC | ||
OS: | All | ||
See Also: | http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2532 | ||
Change sponsored?: | Sponsored | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 4806 | ||
Bug Blocks: | 2532 | ||
Attachments: |
Screen shot of syspref setup
enable multiple hold working with item-level_itype=ON |
Description
Chris Cormack
2010-05-21 01:24:48 UTC
Can I ask why this is a preference? and not in the circ rules or item types admin area? It seems like a very confusing looking preference. This question comes from some talk on IRC today - if you're curious why I'm commenting now. The first thing required to get this to work is a primary key on the reserves table! Right now, borrowernumber + biblionumber are being used as the match point, which precludes multiple holds on a single title. The patch here is insufficient by itself, and references a system preference not already in Koha. Marking as obsolete. The need for some kind of restriction mechanism still exists; not all libraries will want patrons to be able to place multiple holds on a material; this could lead to gaming the system by placing holds on every available copy of a popular book, for example. I think a control mechanism that looks at the items.enumchron field for distinct values would be a way to go; this would let different vol/issue items, for example, take in multiple holds, but equivalent copies could still be restricted (unless they were explicitly given distinct enumchron values) The Harley integration project has been stalled for some time. |