Bug 9702 - Don't allow a patron to place a hold on an item they have checked out
Summary: Don't allow a patron to place a hold on an item they have checked out
Status: RESOLVED DUPLICATE of bug 9206
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-22 22:00 UTC by Anthony Laquerre
Modified: 2013-05-11 11:41 UTC (History)
3 users (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anthony Laquerre 2013-02-22 22:00:28 UTC
Request for enhancement.

It is currently possible for a user to reserve a document that is already in his hand.

To reproduce:
1 - Pay a document to the user.
2 - Connecting to the OPAC.
3 - Find the document ready in 1.
4 - Make reservation

Ideally not allocate a reservation because it allows the user to "double" the number of renewal.

Tested today, on current master
Comment 1 Nicole C. Engard 2013-03-21 21:36:14 UTC
This is not an enhancement request - but a bug. Koha used to stop users from placing the same item on hold over and over in previous releases.

Nicole
Comment 2 Owen Leonard 2013-05-10 15:36:54 UTC
> This is not an enhancement request - but a bug. Koha used to stop users from
> placing the same item on hold over and over in previous releases.

I thought this was the case too, but I can't find a previous version that does.
Comment 3 Katrin Fischer 2013-05-11 11:41:11 UTC
I think Owen is right and it always worked that way, but there is a new system preference in 3.12:

AllowHoldsOnPatronsPossessions
Allow/Don't 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.

*** This bug has been marked as a duplicate of bug 9206 ***