[Koha-bugs] [Bug 2396] New: Add a syspref to block the ability to place next available hold in OPAC on titles that only have lost items.

[bugzilla-daemon at pippin.metavore.com]

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=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
           Version: rel_3_0
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P3
         Component: OPAC
        AssignedTo: jmf at liblime.com
        ReportedBy: debra.denault at liblime.com
         QAContact: koha-bugs at lists.koha.org
                CC: rch at liblime.com, galen.charlton at liblime.com


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.




------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.