[Koha-bugs] [Bug 15534] Add the ability to prevent a patron from placing a hold on a record with available items

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15534

Owen Leonard <oleonard at myacpl.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Needs Signoff               |In Discussion
            Version|unspecified                 |master

--- Comment #2 from Owen Leonard <oleonard at myacpl.org> ---
I don't think this is the right solution for what is currently a messy problem. 

As I understand it, the current "allow on shelf holds" feature will let you
place a hold if *any* of multiple items is unavailable. I understand that this
is The Way It Has Been, but the description of the option in and the
documentation do NOT make it explicit that this is the behavior.

My initial reaction to this patch is that it's trying to make "allow on shelf
holds" work the way it is actually described rather than how it really works.
Do libraries who use the "allow on shelf holds" feature *want* it to work that
way, or do they use it because it's better than nothing?

I think having two settings, "allow on shelf holds" and "allow hold if others
available" is needlessly confusing. On the face of it they both look like they
do exactly the same thing, and I have no idea how they're supposed to work in
conjunction with each other.

In my test of this patch I set a global all item types/all patron categories
rule with both "allow on shelf holds" and "allow hold if others available" set
to "no." However, I was able to place a hold on a title which has one
checked-out item and three available. I don't think that's right.

There have been other discussions of this issue too which should be taken into
account: Bug 6837 and Bug 9190. If we bring it all together is there a single
solution which can accommodate everyone's needs?

-- 
You are receiving this mail because:
You are watching all bug changes.