Bug 5590 - error message on holds not consistent
Summary: error message on holds not consistent
Status: CLOSED WORKSFORME
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: Main
Hardware: All All
: P5 - low major (vote)
Assignee: Kyle M Hall
QA Contact: Bugs List
URL: /cgi-bin/koha/opac-reserve.pl?biblion...
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-07 13:59 UTC by Nicole C. Engard
Modified: 2020-01-06 20:15 UTC (History)
4 users (show)

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


Attachments
batch holds (76.17 KB, image/png)
2011-01-07 13:59 UTC, Nicole C. Engard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nicole C. Engard 2011-01-07 13:59:29 UTC
Created attachment 2964 [details]
batch holds

I'm trying to place a batch of holds and the error message at the top says I can't place holds on any of the items, but there is one item that has the option to place a hold (visually) - that one item however is checked out to the patron already, so it shouldn't be allowed to be placed on hold (I don't think). So basically the error message is right, but one of the items that can't be put on hold is still allowing holds. See attached.

I need someone to test this further to confirm that it's an error and what's causing it.

Also CCing Owen because the errors highlighted in yellow should probably go all the way to the end of the box - they look a bit short/funny now.
Comment 1 Owen Leonard 2014-07-15 16:48:29 UTC
Please check whether this bug is still valid. I think that I'm unable to reproduce the problem, but I'm not exactly sure if I'm trying to duplicate it correctly.

> that one item however is checked out to
> the patron already, so it shouldn't be allowed to be placed on hold (I don't
> think).

I don't think one should expect a hold to be blocked when the title is checked out to that patron.
Comment 2 Katrin Fischer 2014-07-20 21:35:17 UTC
There is a system preference for this: AllowHoldsOnPatronsPossessions

I think the problem is, that if the record is one with different volumes or serial issues, placing a hold on something the patron has already checked out should be possible.
Comment 3 Marc Véron 2016-01-05 11:51:31 UTC
Is this bug still valid?