Bug 3551

Summary: patron able to place hold on book he already has
Product: Koha Reporter: Chris Cormack <chris>
Component: Hold requestsAssignee: Henri-Damien LAURENT <henridamien>
Status: RESOLVED DUPLICATE QA Contact: Bugs List <koha-bugs>
Severity: enhancement    
Priority: P5 - low CC: katrin.fischer
Version: Main   
Hardware: All   
OS: All   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:

Description Chris Cormack 2010-05-21 01:12:02 UTC


---- Reported by nicolas.morin@biblibre.com 2009-08-25 16:01:09 ----

I have an item on loan, I go to the opac and search the book. Then place a hold: Koha doesn't tell me I already have that book on loan, it accepts the hold request. 
There should be a message like: "you already have this document on loan", and the hold rejected.



---- Additional Comments From katrin.fischer@bsz-bw.de 2009-09-01 14:20:06 ----

I talked to Chris Cormack on IRC about this behaviour of Koha. We came to the conclusion its more a feature than a bug. But I would really like an option to prevent holds on items the user has already checked out.



--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 01:12 UTC  ---

This bug was previously known as _bug_ 3551 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=3551

Actual time not defined. Setting to 0.0
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here: chris@bigballofwax.co.nz.
   Previous reporter was nicolas.morin@biblibre.com.

Comment 1 Katrin Fischer 2011-04-18 13:59:07 UTC
Readding mailing list as qa contact.
Comment 2 Chris Cormack 2013-01-13 18:06:33 UTC
Is this still needed?
Comment 3 Katrin Fischer 2013-01-13 19:46:16 UTC
I had a library complaining about this last week...so I think it's still relevant. But I think there is another bug dealing with that problem somewhere, I will try to find it.
Comment 4 Katrin Fischer 2013-01-13 21:07:24 UTC

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