Bug 2396

Summary: Add a syspref to block the ability to place next available hold in OPAC on titles that only have lost items.
Product: Koha Reporter: Chris Cormack <chris>
Component: OPACAssignee: Galen Charlton <gmcharlt>
Status: CLOSED FIXED QA Contact: Bugs List <koha-bugs>
Severity: enhancement    
Priority: P3 CC: gmcharlt, katrin.fischer
Version: rel_3_0   
Hardware: PC   
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 00:50:43 UTC


---- Reported by debra.denault@liblime.com 2008-07-24 09:49:24 ----

Currently in Koha 3.0, if a bib record has items with a lost status linked to it, when a hold is placed on that title, whether in the staff client or OPAC, item specific holds are prevented from being placed on the items with the lost status by way of not being able to click on them in the list of items. If there are other items of various statuses then the user can place a "next available" hold. The problem is when the bib only has a single or a couple of items and they all have a lost status. You are still permitted to place a "next available" hold on the title, even though all the items are lost. This makes sense from the staff perspective so that they can trap lost items at checkin if they are returned but it does not make sense to allow a patron to do this via the OPAC. It is even more confusing for them because right now the way it works, after the hold is placed and the user brought to their list of holds, the hold on the lost item title shows as "waiting to be pulled" 

It would be nice / almost essential to have a sys pref to prevent the ability to place title level holds in the OPAC on titles whose items are all lost.



--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 00:50 UTC  ---

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

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 debra.denault@liblime.com.
CC member rch@liblime.com does not have an account here

Comment 1 Katrin Fischer 2011-04-25 09:28:06 UTC
Perhaps we need an equivalent to AllowHoldsOnDamagedItems for lost items?
Comment 2 Owen Leonard 2013-01-15 20:46:13 UTC
(In reply to comment #0)
> The problem is when the bib only has a single or a
> couple of items and they all have a lost status. You are still permitted to
> place a "next available" hold on the title, even though all the items are
> lost.

This is no longer true in master.