Anonymize resource sharing requests when rejected by last partner in rota
A borrowing request that is rejected by partner is considered as a completed resource sharing request, and therefore is included in the anonymization job that deletes user information in a RS requests (Fulfillment job > Anonymize resource sharing requests). This causes several problems for how the BIBSYS Consortium handles resource sharing:
1) A borrowing request that is rejected by partner is not considered as complete in the way the consortium handles resource sharing. Even when the last partner in the rota rejects the request, we still want the borrowing request to be active. If no partner within the consortium can deliver the document, we may try partners outside the consortium, or even abroad. Therefore, the status Rejected by partner should not have a terminate effect. As it works now we need to duplicate the request in order to keep working on it.
2) A consequence of making a borrowing request complete when rejected by partner, is that it is included in the anonymization job. Due to strict privacy policy we can't turn off the anonymization schedule, and since we want to continue working on the rejected borrowing request we need to keep the user information.
Suggested solution:
Introduce an option to configure whether or not a request with the “rejected by partner” status should be regarded as complete.
Add “Request anonymization rules” similar to “loan anonymization rules”, allowing institutions to configure which RS requests should be subject to anonymization.
Hi,
The March 2018 release includes new options for resource sharing – you can choose whether a resource sharing request will remain in an active status even if it has been rejected by the resource sharing partner. See here for more details: https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2018/10_March_2018/Alma_March_2018_Release_Notes/05Resource_Sharing_-_March_2018_Enhancements#Workflow_Options_for_Rejected_Resource_Sharing_Requests.
-
Katherine commented
Hello,
I don't know if this will help you in the meantime, or if you've already thought of it, but:
We have manually created a 'blank' partner that we add to the bottom of the rota to prevent this from happening. Then, as part of our maintenance tasks we filter by this partner and follow up on the requests to source them elsewhere.
It's not ideal, but it does the trick given current Alma features! Hopefully this helps you?
Best,
Katherine