The new Automatic Claim feature does not differentiate between Format Types when adding "Time to Claim (days)" in the Partner record. For example, it should be possible to write 2 days for Digital requests and 5 days for Physical requests.

We would like to print Book Straps (like in OCLC) to attach to books as quite often our patrons return books with out the Slips.

It should be possible to change the status of a Borrowing Request to Digitally Received by Library from Physically Received by Library or vice-versa, if the wrong Format was received. Currently, it is impossible to create a barcode if the item was Digitally Received.

If we add any notes it would be helpful to see that there is a note in the request on the first creation screen so that other people can see it straight away without having to look at each one individually

Unfortunately, ILLiad's email import feature does not always import emails generated by Alma properly. This happens mainly when there is a copyright symbol in the requested item's publication date. Giving us the ability to remove the publication date field from the email generated by Alma would help us manage this issue until OCLC and Atlas Systems can find a proper fix.

It would be helpful if the resource sharing request would display in the brief format the name of the staff that the request is currently assigned to. Currently, you have to go into the "History" tab of the request to find this information.

In a different area, "Reading lists", this information is readily available, and it would facilitate the workflow in resource sharing handling, too.

1. It should be possible to configure the automatic Claims job to send additional Claims every X number of days, until the status of the request is updated to Received.




2. In the meantime, it should be possible to send additional Claim letters manually (and not as a General Message).

We would like to see on the audit of a borrowing request which actions were done.
For example, if we change or add something to a title, we could not see that anywhere.
We would like also to know if the publication date was changed, ...
We are a team of 5 librarians and with 10'000 requests from our users per year it's not possible to remember what everyone makes for each request.

In attachment, the audit now and an example of our ancient audit (historique) on the ancient software.

We sometimes need to change the Request Type from Physical to Digital and vice versa, after we have placed the request via Management Fulfillment Options. As there is no edit option, we have to place a new request and then delete the redundant option.

Following the implementation of the ability to check for duplicates when creating borrowing requests, we see that this only applies to active requests. We would find it helpful to have duplicate completed and cancelled requests flagged up in Alma (without the request being automatically rejected)

In the December 2017 enhancement, the fields Chapter Author, Chapter Title, and Editor were added to the Alma Resource Sharing screen and Chapter was renamed Chapter Number.
However, these fields were not added to the Primo Resource Sharing form, which means all the details must be entered in one field such as. Chapter details: title, author, number.
As most Resource Sharing requests arrive via the Primo form, it would be helpful if EXL fixed this too.

After Renewing a Lending request the status automatically updates to "Received by Partner" - it would be more helpful if the status updated to 'Renewal Accepted".

Ability to dismiss notes/General message in rejected lending/borrowing request.

When we recieve notes/general messages on rejected lending or borrowing request the only option is to delete the note/ general messages. If we want to keep the requests history, deleting messages/notes is not good.

Some LADD notes and actions don't map to visible fields in Alma, therefore we don't receive them.
For example, if a LADD user sends a damaged note this does not come through into Alma via ISO. Is there a way that non-mapped elements can be mapped to the general messages area in Alma, so that they can at least be viewed/received.

We would like to combine data from Funds with data from Borrowing, Fulfillment and Fine & Fees in Analytics

Enable the option to send notifications to users who place resource sharing requests for each stage of the process. This will give users a better sense of where their requests are, instead of just sending them into a black hole with no idea when they might arrive. This is similar to the way that online shopping provides notifications for each stage of a purchase, and is something users are coming to expect.