As a librarian processing RS requests, it is useful to be able to see the patron's Primary Identifier when I am editing a request. I can copy this to quickly check a patron's account in Fulfillment.

This information used to be available and is visible in the patron pop-up in the Requests list.

Enhance the Holdings Records Mapping feature (new as of March 2018) to include adding 007 fields and other control fields during the import process. Per SalesForce case #00525849, this new feature currently only works with data fields (non-control fields).

Now "save and edit" is only an option for the borrowing req. made manually, would be helpful option for all req.

We would like the ability to bulk reassign requests in Alma RS, in terms of assigning a group of requests to one staff member to process rather than having to reassign individually.

As a result of lending requests sometimes being attached to an incorrect MMSID, with no clear indication as to why or how, we would like to see an enhancement to the lending request history tab to include information when this happens. This is to better analyze future cases where this error occurs.

It should be possible to add a Note at the same time as Uploading a File to a patron. Currently, we have to send a separate Patron Query Template after the link has been sent.

Resource sharing borrowing requests which have been exported to third party broker systems should be able to be reactivated, in the same way as completed requests sent to P2P partners.

This is needed because we make mistakes! Sometimes a request is sent to a broker by accident.

We also need to be able to handle workflows which combine brokers and P2P partners. We want to be able to send a request to a broker system, and then if the request cannot be filled via that broker, to be able to return to the Alma request and assign alternative P2P partners.

When a user enters a DOI into the Alma Resource Sharing form we would like to see the form use the DOI to auto-populate the rest of the metadata for the user.
This is a functionality we have had our users requesting.

When Uploading a File, it should be possible to preview the file before clicking on send, to prevent the wrong file from being uploaded.

When you convert a hold request into a resource sharing request, Alma does not check the resource sharing library's borrowing resource sharing fulfillment unit rules to make sure the user is allowed to submit resource sharing requests. This makes it possible to create resource sharing requests for users who do not have resource sharing privileges. When converting a hold request into a resource sharing request, Alma should check the check the borrowing resource sharing fulfillment unit rules. If the user is not allowed to submit resource sharing requests, a warning message should appear.

For Lending Digital requests, could the "Complete the request" be automatically selected when we ship an item (or maybe the recent choice remembered) – so we don't have to select it each time we supply an item?

There is an Active Resource Sharing Request limit, which you set in the Fulfillment rules for your resource sharing libraries.
However there doesn't appear to be an ability to allow staff to override this limit, which from time to time they need to do.
I propose that there is a parameter that allows staff with a particular role the ability to override this limit.
Either something that was set as the default for the Fulfillment Services Manager role, or a block preference that you can override.

Currently if a DOI is added to a request it isn't included in the email request sent to an email resource sharing partner. The DOI could help identify the correct article more quickly - seems strange that this is not included already

Too much clutter in active screen. Would be great if this screen only showed new /pending created requests. The facets to the left would then be more meaningful and useful as filters to find specific requests - those sent to partner, those that overdue etc instead of requests with these statuses being presented within the active request mix

When creating a borrowing request in Alma, Alma transforms the info in a brief bibliographic record. This is great for everything that has to do with Resource Sharing.

BUT: Librarians who are cataloging find this bib record, don't think twice and just add a holding and an item. So the RS bib record has become a real bibliographic record, but without any one completing the info.

We would like the resource sharing bib records to be marked somehow so that cataloguers can identify them easily and either complete them or import them from another source.

We would like to circulate items to fulfillment network member patrons based on their user type in their home institution.

This means that the linked account rules need to be based on Source Institution + Source Institution User Group.

This could be made an optional feature so that Fulfillment networks that did not want to share that level of detail didn't have to.

We have multiple libraries set up as Resource Sharing Libraries. However as we can only have one preferred email address the Borrowing Resource Sharing Requests are coming from the default email address for the library (usually the information email address), and not the dedicated email address for resource sharing at that library.
It would be really useful to have an email address type in a library record that is used to send Resource Sharing requests.

Resource Sharing requests appear in "Patron Services" with one Request Type: "Patron physical item request". However, in "Resource Sharing Borrowing Requests" there are two types of Requested Format: Physical or Digital. Both types should appear correctly under Patron Services, and not only Physical.

We would like Digital Lending Requests to be automatically updated to Being Processed once the slip has been printed - in the same that way Physical Lending Requests are updated to Being Processed once a hold has been placed via Manage Fulfillment Options. At the moment they have status Created Lending Request - which means we have to change the status manually.