Bug 2711 - No Holds on Lost Items
Summary: No Holds on Lost Items
Status: CLOSED WORKSFORME
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: master
Hardware: PC All
: P3 enhancement (vote)
Assignee: Galen Charlton
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-23 02:53 UTC by Nicole C. Engard
Modified: 2020-01-06 20:14 UTC (History)
5 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Cormack 2010-05-21 00:54:59 UTC


---- Reported by nengard@gmail.com 2008-10-23 02:53:13 ----

Let me preface this by saying - I feel this is one of those things that I think is a bug that you may have a reason for.

Right now, if the only item(s) available for a biblio are marked as lost you can place them on hold - but if the items are lost, then it doesn't make sense to allow holds.

Is this a bug or something we need a system preference for like we have for other hold exceptions?



---- Additional Comments From oleonard@myacpl.org 2008-10-23 05:25:09 ----

I agree that libraries need the option to block holds on lost items. I suspect that many patrons either wouldn't notice that the item is lost, or wouldn't really know what lost meant. 

One question is how this relates to the 'hidelostitems' system pref. If hidelostitems is ON, does that take care of this issue? Even if so, are there cases where a library would want to show lost items in the OPAC but still block holds on those items?



---- Additional Comments From nengard@gmail.com 2008-10-23 16:17:01 ----

From the OPAC if hidelostitems is ON you cannot place a hold - but I guess there are libraries that are displaying their lost items.



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

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

Actual time not defined. Setting to 0.0
CC member bchurch@ptfs.com does not have an account here

Comment 1 Katrin Fischer 2013-04-13 18:55:49 UTC
I think for some situations a hold on a lost item might make sense. It would give the library a reason to purchase another item. 
So this would need to be controlled by configuration settings.
Comment 2 Marc Véron 2017-04-17 06:39:15 UTC
Still valid?
Comment 3 Hugh Rundle 2018-04-13 05:52:56 UTC
I think this is reasonably well answered here:

>From the OPAC if hidelostitems is ON you cannot place a hold - but I guess 
>there are libraries that are displaying their lost items.

Katrin's right that it should be a toggle, but effectively it already is. If you want people to see lost items then you probably want them to be able to place holds on records where all items are lost. And if you don't want them to do that, then you can just hide lost items.
Comment 4 Katrin Fischer 2019-05-04 18:34:14 UTC
(In reply to Hugh Rundle from comment #3)
> I think this is reasonably well answered here:
> 
> >From the OPAC if hidelostitems is ON you cannot place a hold - but I guess 
> >there are libraries that are displaying their lost items.
> 
> Katrin's right that it should be a toggle, but effectively it already is. If
> you want people to see lost items then you probably want them to be able to
> place holds on records where all items are lost. And if you don't want them
> to do that, then you can just hide lost items.

Closing WORKSFORME as per this comment.