Update Resource-sharing request through the ALMA API
Currently with the API, the only update option possible is shipping a resource sharing request. We request the option to perform other updates, e.g. change the status.
(Updating the resource sharing request through the corresponding user-request does not work.)
-
Allen Jones commented
This request seems to have gotten stale. This is a strongly needed API endpoint for borrowing requests to write integrations against systems from other vendors, particularly in Library Open Workflows.
Basically, we need the following:
1) be able to query requests in a particular state and for a particular partner within a specific IZ
2) be able to create/cancel/update requests (such as adding a remote record identifier to the request, add a label, or move to another status)
3) be able to 'send' the request to the partner from Alma upon save.it would be great if we might be able to send a request such as :
GET /almaws/v1/resource-sharing-requests?status=CREATED_BORROWING_REQUEST&&partner=PARTNER_CODE&limit=100
There are create and delete/cancel actions for resource-sharing requests, but not update functions (https://developers.exlibrisgroup.com/alma/apis/users/#Requests)
A script would perform remote record ID lookups automatically before sending to a specific network/partner using their local 001 identifiers to improve fill rates. Once the request was updated, a parameter in the GET request would be included to submit the request to the partner (submit_to_partner=true) and advance the request to "request sent to partner".
Ideally, we should be able to run a separate script to see if a particular RS transaction (based on the external identifier) submitted to a partner has gone 'end of rota', then update the alma resource sharing request by changing the status to "REJECTED_BY_PARTNER".
-
Matt Black
commented
Hi Knut, does your idea refer specifically to borrowing requests or does it include enhancing the lending request API (https://developers.exlibrisgroup.com/alma/apis/partners/) to support updates? Either way I second the need for this.