Block expired patrons from placing resource sharing requests in Primo
There should be an easy way to block patrons with expired Alma accounts from placing resource sharing requests in Primo. We shouldn't have to run a script as a work-around.
Currently, there is no way to tell Alma that expired patrons cannot place resource sharing requests in Primo. Expired patrons in Alma can place resource sharing requests, even though they are unable to checkout the material. This makes for very unhappy patrons.
The February 2017 Release includes this idea. For more details please see here:
http://knowledge.exlibrisgroup.com/Alma/Release_Notes/0099_2017/110_February_2017/Alma_February_2017_Release_Notes/04Fulfillment_-_February_2017_Enhancements#Additional_Fulfillment_Enhancements
where the new check_for_expired_account, parameter is described
-
The February 2017 Release includes this idea. For more details please see here:
http://knowledge.exlibrisgroup.com/Alma/Release_Notes/0099_2017/110_February_2017/Alma_February_2017_Release_Notes/04Fulfillment_-_February_2017_Enhancements#Additional_Fulfillment_Enhancements
where the new check_for_expired_account, parameter is described. -
Paula Fitzpatrick commented
Hi, could you please clarify which requests this will apply to? As stated above, this needs to be applied to all requesting, not just resource sharing.
-
Chris Jones commented
Could we clarify which request types this is intended to apply to? Patron Physical, Resource Sharing, but digitization? patron purchase?
-
Jim Adamson commented
The control should also be effective for requests placed through the Alma resource sharing API (our institution uses a local web form which POSTs the data to this API). A suitable response code would also be helpful, so we can display a specific message to our users in these cases.
-
Thank you for this idea.
We will indeed enable the system to consider not only the role expiry date, but also the account expiry date, so that if either is expired then the users’ privileges will be considered expired.
-
Chris Jones commented
As Nicola notes, this issue exists with normal Patron physical item requests (where it is probably a bigger problem, see case 00074651). In Case 00076369 from May 2014 there was meant to be a Roadmap commitment.
"As expired users are blocked from logging in to Primo, the problem is on the Alma side. There was recently an enhancement request that staff should get a warning when trying to place a request for an expired user. The enhancement was accepted and is now on our roadmap. "
Later clarification was sought in case 00166605.
It also seems to be an issue for Patron Purchase requests where I understand (SFC 00239974) that it was designed that way.
-
Sara Decoster commented
I totally agree. It may seem strange to patrons that they can't borrow the book they requested.
-
François Renaville commented
I agree. It should not be possible for expired users/patrons or patrons with blocks to place requests. If patrons are blocked from loaning, they should also be blocked from requesting.
We're specifically interested in being able to block requests based on the following criteria: Max cash owing, Max overdue recalled items, Lost items and Expired accounts.
This new control should be effective for requests (including RS requests) placed in Alma (by the staff) and in Primo.
-
Nicola Carson commented
This problem also exists with ordinary requests as well.