Add "Request" as a block option in Block Preferences
Currently the Block Preferences have Block options to permit Blocks on Loan and Renewals, but it would be good to include Blocks on Requests on these blocks - specifically Patron Physical Item Requests, but conceivably other requests.
For example is a Patron Limit is defined on Overdues or Recalled overdues, and the limits are exceeded, the relevant Block Preferences are triggered,
i.e.
Patron overdue limits has exceeded
Patron overdue recall limit exceeded
However, the only options on what patron services blocked are Loan and Renewal.
Requests should also be added to the options so that overdues can immediately block a wider range of patron services.
Adding this option allows libraries to more adequately sanction the breaching of patron limits (without having to manually add User Defined Blocks which do allow Request blocking) and so would prevent users with overdue (requested) items from requesting additional items while they are remain overdue themselves.
-
UC - Chile commented
This idea is really necessary, has advance?
-
Ann-Louise commented
Has this improvement ever been in the NERS-voting? If not, maybe it's about time. As long as it doesn't "steal" all the complexity points. :-D
-
Simon Read commented
Thanks Moshe. We're still very keen on this enhancement being implemented so appreciate you continuing to work on it even though it's complex. We're looking forwards to its delivery.
-
The plan is to add a configurable parameter that will set the system to check the patron's permission to also borrow. If the patron cannot borrow the item, request will also not be allowed.
As simple as this may sound, the technical analysis that was already done for this development proved to be more complicated than originally estimated. We are repeatedly revisiting this issue and have not removed it from our to-do list, but unfortunately there is no near term timeline that can be shared. We will do our utmost effort to accelerate as possible.
-
Ann-Louise commented
Are there any progress on the planned solution? Any updates?
-
Monica Crump commented
Any update on this, it would be very much valued now we're all running Click and collect services. retrieving material for a user who then turns out not to be entitled to borrow the book is very frustrating and wasteful of staff time.
-
Toby Hopper commented
We'd like this functionality in the Block preferences table as described by Chris in the comments below - Any update ExLibris?
Thanks,
Toby
-
Gran commented
Dear Exlibris,
this Idea has status "Planned" since January 2018. The previous comment from October 2018 remained unanswered. Please indicate when this Idea will be implemented.
Thanks,
Meike -
Craig Rosenbeck commented
Looking forward to this update. Is there a timeline for this update?
Thanks,
Matthew -
Marco Tomassini commented
Hi all.
I totally agree with Jay's comment. We have great expectations for this improvement.marco
-
Hi,
The suggested approach is simpler both technically and in terms of the policy decision and configuring. It makes it a simple decision of 'do I want to allow requesting a resource that is (currently) not loanable', and leaves one place only to turn this policy on.
Note that this does not cover resource sharing requests, where there is no real item in the inventory that can be checked. For this reason, eligibility for resource sharing is checked via its own set of rules.
As with other request blocks, if as a result of this check the patron cannot place a request, the link will not show at all.
Moshe
-
Chelle Batchelor commented
Moshe, one thing I like about your solution is that it would include a check against patron expiration date before allowing a request. Currently our expired patrons can place requests. In the case of a Summit request, the book comes all the way from another institution to our hold shelf, and then when the patron comes to pick it up, they realize they are expired and cannot check it out. Preventing these requests would be a great efficiency.
-
DaVonne-Rochelle Armstrong commented
This enhancement would greatly help Penn's operations!
-
Marco Tomassini commented
I agree: this should be a useful and needful feature. Our library need it.
-
Chris Jones commented
Many thanks for the outline proposed solution.
We originally had in mind row 21 of Block Preference "Patron overdue limits has exceeded" where there are Loan Renew and BOTH options, (NB as also Rows 17 Patron cash limits has exceeded and 22 Patron overdue recall limit exceeded).
Is there a specific difficulty in doing an outright block preference option? as opposed to the - more subtle perhaps - configurable option of checking the requestability when it checks the loanability?
Is the additional parameter purely extending the loan block to a request consideration at the point of request service calculation - i.e. does this mean an error on trying to place a request (configurable message?) or just an absence of a request option?Elsewhere in alma the separate block types appear in User block definitions, in the "BlockedAction" levels where different blocks (including requests) can be configured (by support ). As described here:
https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/Alma_Online_Help_(English)/Fulfillment/080Configuring_Fulfillment/060Patron_Configurations?uxp=true#Adding_User_Block_DefinitionsThanks
Chris -
Anonymous commented
I agree
-
Ingebjørg commented
I agree
-
Wenche Lind commented
I agree. A huge improvement
-
Alberto Rovelli commented
I agree, we need to block patrons with Overdues from placing other requests: it would be a very important improvement for our library!
Thank you. -
Effat Zahedifar commented
I agree!