Bug 16260 - Have AllowHoldsOnPatronsPossessions check for multiple holds allowed on a record
Summary: Have AllowHoldsOnPatronsPossessions check for multiple holds allowed on a record
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: master
Hardware: All All
: P5 - low major (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 9206 14695
Blocks:
  Show dependency treegraph
 
Reported: 2016-04-14 15:22 UTC by Marjorie Barry-Vila
Modified: 2020-03-01 09:43 UTC (History)
8 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Who signed the patch off:
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 Marjorie Barry-Vila 2016-04-14 15:22:57 UTC
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
Comment 1 Christopher Brannon 2018-12-01 21:21:35 UTC
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.
Comment 2 Jonathan Druart 2019-06-06 20:42:20 UTC
I'd say that code related to AllowHoldsOnPatronsPossessions (from reserve/request.pl and opac/opac-reserve.pl) must be moved to C4::Reserves::CanBookBeReserved
Comment 3 Azucena Aguayo 2020-02-26 00:09:24 UTC
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