Bug 10591 - Why do we allow holds on restricted items (952$5=Use restrictions)? Place a hold for reference?
Summary: Why do we allow holds on restricted items (952$5=Use restrictions)? Place a h...
Status: In Discussion
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: master
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-15 11:31 UTC by Marcel de Rooy
Modified: 2021-12-20 15:32 UTC (History)
6 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 Marcel de Rooy 2013-07-15 11:31:27 UTC
Currently, it is possible to place a hold on an item marked as Restricted with 952 $5. And you can also confirm the hold, setting it to Waiting status.
The code in Circulation.pm (CanBookBeIssued) checks before issuing if an item is restricted and will not permit checkout.
So actually, the book is not for loan. It may be available for reference in the library?

This may be just unintentional. But if we would have the intention to provide a mechanism to place holds for reference in the library, we probably should deal with the remaining workflow too. How do we registrate that the user received the book for reference, and when do we remove the waiting hold? Do we count these kind of references? 

Note also that we could have a library building workflow on this possibility, and another developer that some day makes it impossible to reserve restricted items not knowing that.

What do you think?
Setting this report to In Discussion, hoping for some more feedback.
Comment 1 Martin Renvoize 2014-12-17 08:06:18 UTC
Did this ever get asked on the list... is it still the case... how can we progress this?
Comment 2 Katrin Fischer 2015-01-13 09:11:36 UTC
I am currently investigating how we could possibly use the restricted field in Koha for a new library.

This is what I found out:
- the circulation will only be blocked, if restricted = 1
http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=C4/Circulation.pm;hb=483ad2aee510cb23f2bae61883d6b90de262d13d#l903

There seems no other functionality linked to it.

So currently, if you added another authorised value != 1, you can check out the item just fine.

I'd like to see us decide how this is intended to be used to avoid future problems.

We already have the 'not for loan' status blocking circ and holds - maybe it makes sense to have another status that allows holds, but for example only allows for on-site checkouts? 

But I'd hesitate to change the current behaviour without a good plan and an email to the list, as libraries might have been using this field in different ways. Maybe even needs to be a parameter for a while.
Comment 3 Lisette Scheer 2016-09-10 20:51:16 UTC
I tested how it works today a little bit.
With a -1 value:
You can put an item on hold for a staff patron and check it out to staff patrons with no problems. 
You can't put it on hold for a non-staff patron. 
You can check it out to a non-staff patron, with a prompt that they shouldn't be able to, would you like to override Y or N. 

We are looking at using this functionality for our professional development collection.
Comment 4 Katrin Fischer 2016-10-16 13:55:34 UTC
Hi Lisette, thx for adding your comment!
Comment 5 Florian 2021-12-20 15:32:53 UTC
Any news on this? We're trying to fix the weird traps behaviors (952$0, $1, $4 and $5) and the fact that there's nothing to prevent a hold on a restricted item seems weird to me. Not even a syspref.