[Bug 16260] New: Moderate the impact of AllowHoldsOnPatronsPossessions
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 Bug ID: 16260 Summary: Moderate the impact of AllowHoldsOnPatronsPossessions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs@lists.koha-community.org Reporter: marjorie.barry-vila@ccsr.qc.ca QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com Hi, System preference AllowHoldsOnPatronsPossessions is too restrictive. Test plan: -AllowHoldsOnPatronsPossessions : Don't allow -notice with 2 items (X and Y) -one of items is check-out by borrower A (item X) -other items is check-out by borrower B (item Y) If Borrower A wants to hold item Y, he can not because of the system preference. If system preference is Allow, Borrower A can hold item Y but he can hold item X too, and we don't want that he can. Is there something I do not understand in the configuration ? Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 Patrick Robitaille <patrick.robitaille@ccsr.qc.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrick.robitaille@ccsr.qc. | |ca -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 Marjorie Barry-Vila <marjorie.barry-vila@collecto.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marjorie.barry-vila@collect | |o.ca -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 Christopher Brannon <cbrannon@cdalibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|enhancement |major CC| |cbrannon@cdalibrary.org --- Comment #1 from Christopher Brannon <cbrannon@cdalibrary.org> --- I agree that this AllowHoldsOnPatronsPossessions is a problem. Currently, we have certain records that we allow mulitple holds on. The patron cannot place a hold on one of these items if they have something on that record checkout out and AllowHoldsOnPatronsPossessions is set to Don't allow. This preference needs to take into account circ rules that allow multiple holds on a record. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 Jonathan Druart <jonathan.druart@bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart@bugs.koha-c | |ommunity.org Depends on| |14695 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14695 [Bug 14695] Add ability to place multiple item holds on a given record per patron -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 --- Comment #2 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- I'd say that code related to AllowHoldsOnPatronsPossessions (from reserve/request.pl and opac/opac-reserve.pl) must be moved to C4::Reserves::CanBookBeReserved -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 Jonathan Druart <jonathan.druart@bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |9206 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9206 [Bug 9206] Only allow place holds in records that the patron don't have in his possession -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer@bsz-bw.de Summary|Moderate the impact of |Have |AllowHoldsOnPatronsPossessi |AllowHoldsOnPatronsPossessi |ons |ons check for multiple | |holds allowed on a record -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 Azucena Aguayo <azucena.aguayo@uvu.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |azucena.aguayo@uvu.edu --- Comment #3 from Azucena Aguayo <azucena.aguayo@uvu.edu> --- Our library just turned this feature ON. Most of our titles have a single copy and this feature works perfectly for that. However, when dealing with volumes the system preference falls short. Example: Title X has v1, v2, v3 Patron A checked out v1 Patron B checked out v2 Patron A wants v2 when it gets back. Patron A cannot place hold on v2. Patron A must return v1 before placing hold on v2 Not ideal for all cases, but it would help if the preference could restrict on number of items attached to a single bib. Example: Title X with 1 copy = holds not allowed on possession Title Y with 2+ copies = if all copies cko to borrower then no holds else if borrower cko title copies < max title copies then holds allowed -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 Michal Denar <black23@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |black23@gmail.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 --- Comment #4 from Christopher Brannon <cbrannon@cdalibrary.org> --- (In reply to Christopher Brannon from comment #1)
I agree that this AllowHoldsOnPatronsPossessions is a problem.
Currently, we have certain records that we allow mulitple holds on. The patron cannot place a hold on one of these items if they have something on that record checkout out and AllowHoldsOnPatronsPossessions is set to Don't allow. This preference needs to take into account circ rules that allow multiple holds on a record.
Would really like to see this oversight or conflict in logic addressed. It is an ongoing issue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 --- Comment #5 from Jonathan Druart <jonathan.druart+koha@gmail.com> --- (In reply to Jonathan Druart from comment #2)
I'd say that code related to AllowHoldsOnPatronsPossessions (from reserve/request.pl and opac/opac-reserve.pl) must be moved to C4::Reserves::CanBookBeReserved
Done on bug 22806. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 --- Comment #6 from Jonathan Druart <jonathan.druart+koha@gmail.com> --- Created attachment 156518 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=156518&action=edit Bug 16260: Remove CheckIfIssuedToPatron -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 --- Comment #7 from Jonathan Druart <jonathan.druart+koha@gmail.com> --- Created attachment 156519 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=156519&action=edit Bug 16260: Adjust logic of AllowHoldsOnPatronsPossessions -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 --- Comment #8 from Jonathan Druart <jonathan.druart+koha@gmail.com> --- I think this patch is doing what you are expecting, but I am not sure this is a change everybody will agreed on. The syspref's description is clear enough: "Allow/Do not allow a patron to place a hold on a record where the patron already has one or more items attached to that record checked out." Patch for discussion. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 Jonathan Druart <jonathan.druart+koha@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=26058 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 --- Comment #9 from Christopher Brannon <cbrannon@cdalibrary.org> --- So, my concern is, we don't want to just turn this system preference on for everything, but we have had to, because we have a mixed bag of records. Usually, a record has multiple copies of the same thing. We don't need one person monopolizing those items. However, we also have records that contain many different things. Like serials. Every copy for a title is under one bib. We do want patrons to have the liberty of placing holds on other items while they have an issue from that bib checked out. We currently have to have this preference on. The original function works as it should. We also use the Holds per record rule set to 1 for most items where we don't want people to place a second hold. But that does not account for an item that a patron has checked out. They can still place a hold. What needs to happen is that we need to define if this Holds per record rule includes current issues or not. I think that is the key element that is being overlooked here. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |enhancement --- Comment #10 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- This behaviour has remained unchanged since introduction of the feature, I think at this point any change is more an enhancement than a major bug. The feature pre-dates the ability to allow multiple holds on a record and it's worth re-thinking this situation and also the item level holds one. There are several things at play here, but it seems to me like the real question is if the items are identical or not. That's not easy to tell. One solution could be the hold level: * If item level holds are allowed, don't allow a hold on the item already checked out to me, but on others. * If no item level holds are allowed, don't allow a hold if any item is already checked out to me. We could use number of holds allowed... but it makes things a bit more complicated for what Christopher said: with a setting of 1 hold allowed, should the already checked out item count? We'd mix number of allowed holds with the checkouts. That does not feel quite right. I think the question here is not if the max allowed holds is reached, but if you have the item in question at home already or not. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 Kristi Krueger <kkrueger@cuyahogalibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkrueger@cuyahogalibrary.or | |g -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 carthur@slolibrary.org <carthur@slolibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carthur@slolibrary.org -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 Andrew Fuerste-Henry <andrew@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew@bywatersolutions.com --- Comment #11 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- We've got a general consensus here that there should be a way to have AllowHoldsOnPatronsPossessions enabled for biblios on which the items are distinct (multi-volume works) but disabled for biblios on which the items are identical (multiple copies). So then the question is how to distinguish these two types of biblios from each other. We just discussed this at a meeting of the koha-US development committee and came up with a few options, but none of them feel perfect. Itemtype: We could set this at the itemtype level. This broadly makes sense when imagining something like a PERIODICAL itemtype (enable AllowHoldsOnPatronsPossessions) and a BOOK itemtype (disable AllowHoldsOnPatronsPossessions). But a nonfiction section will often contain a mix of multi-volume titles and multi-copy records all of the same itemtype. Basing this behavior on itemtype would require libraries to create more itemtypes, which means more circulation rules and other setup. Item-level serial/volume info: We could make AllowHoldsOnPatronsPossessions look at the items.enumchron value and only allow holds where the enumchron value of the item to be held does not match the enumchron value of the item already checked out. But not every library sets enumchron values in their item records, so using this option would force a cataloging practice that might not otherwise be used. Item groups: We could make AllowHoldsOnPatronsPossessions look at item groups and only allow a hold on an item that's not in the same item group as the item already checked out. This assumes libraries would be making distinct item groups for each volume on a multi-volume bib. But this would require setting up item groups of one item each on a lot of bibs and not all libraries use item groups anyway. Some other/new value on the bib: We could make this a new value attached to each individual biblio record, stored in the biblio table. That's very flexible, but feels inefficient. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 --- Comment #12 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- The item type would probably work in our setups as we use a separate item type already to be able to enforce item-level holds where items are expexted to be "individuals" :) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 Chip Halvorsen <Chip.Halvorsen@WestlakeLibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Chip.Halvorsen@WestlakeLibr | |ary.org -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 mteal@greenvillelibrary.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mteal@greenvillelibrary.org --- Comment #13 from mteal@greenvillelibrary.org --- We use itemgroups, so using that or volumes to identify "like" items would work for us. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 --- Comment #14 from Kristi Krueger <kkrueger@cuyahogalibrary.org> --- I talked this over with Christopher Brannon, and for both of us, Andrew's proposed "Some other/new value on the bib" seems the ideal way to go (how bib records are suppressed from the OPAC is a similar example). It would mean catalogers would not need to manipulate many items. Not having to manipulate many items would be good for a Bib record with tons of items for example, People Magazine or a prolific manga or comics series. It would also keep things out of the circ rules table. The item groups option sounds like the next best option after that. Anyone else following this bug have thoughts to share? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org