Currently the "ignorelenderduedate" setting in the Alma Customer Parameters Mapping Table is a global setting; it applies to all resource sharing partners. This is problematic for consortia who have resource sharing partners for consortia members, as well as a resource sharing partner for ILLiad.

Setting "ignorelenderduedate" to "true" works for our consortia resource sharing standard checkout, but ILLiad due dates must be entered manually.
Setting "ignorelenderduedate" to "false" works for the ILLiad lender due date, but then consortia due dates must be entered manually.
If "ignorelenderduedate" could be configured separately, for different types of resource sharing partners, this would allow a more seamless ILLiad to Alma integration.

Since some institutions have buildings with perpetual restricted access, we have some AFN fulfillment network member libraries that are willing to send their materials to another AFN member library for pick-up, but, for all functional purposes, they are closed to the public. They don't want patrons from the other AFN institutions to visit their library in person, and thus, don't want patrons from another AFN institution to select their library as a pick-up location.

This need has been heightened during the pandemic, with more institutions closed to the public.

We know that turning off all circ desk hold shelves will fully remove an institution from the list of pick-up locations visible in Primo VE; however, if an institution is allowing local requesting for their own patrons (including curbside delivery or for USPS mail delivery), then they need to have the hold shelf enabled.

We need a setting that would allow Institution A to lend/renew/borrow/request/fulfill-requests for Institution B, without allowing Institution B's users to select Institution A as a pick-up location.

Also, if Institution A will lend material to a patron from Institution B, we also need a way to prevent a patron from selecting Institution C as a pick-up location, if Institution C is not open to the public.

The functionality would need to be consistent for the patron for both local and AFN requesting, because it is difficult to teach patrons contingencies.

We are trying to configure a more automated workflow for Resource Sharing in our consortium. We recently reconfigured our Resource Sharing settings. Our Partners' Locate Profiles were all changed from not checking availability (so we had time to manually manage queues) to "Check for availability" so that items will pass instantly through the Rota if an item is not available at a partner. Then each of the Resource Sharing Libraries modified their Library Details from cancelling requests on locate failure to not cancelling requests on locate failure, which keeps the request Active after it passes through the Rota unfilled, and puts it into a status of Locate Failed. Currently, there is no job to automate the process of Recalculating the Rota Assignment for requests in any Status, let alone the Locate Failed status, so we are manually passing these requests back through the Rota by manually selecting Recalculate Rota Assignment for each one. We would like to perform this automated Recalculate Rota Assignment job daily for a set amount of time or until an entered "date not needed by" gets near (monitored manually), at which point we can help the patron acquire the item via others means at our own discretion. This setup will help our requests reach available partners more quickly and allow an automated way of re-checking Partners for requested items that become available again.

A borrowing article request is stopped for local ownership when the library has an electronic database that may have coverage for the journal.

Currently, the borrowing locate local ownership check does not check the year, volume, or issue in the article request to determine if the library has access to this specific year in the database. The borrowing locate does not check for embargo status.

Because the citation year is not checked for local ownership, requests are stopped from being automatically sent to lending libraries that have the article. Library staff must spend time checking if their library has access to the specific year in their electronic databases.

In Alma Configuration> Fulfillment> General>Other Settings the rsuresolverlocate can be used to check a lending library’s electronic coverage.

An additional Customer Parameter should be added to allow a borrowing library to check their own library’s database coverage information. If a request is for an article that is not within the database coverage or is in an embargo the request should be sent to the lending library without staff mediation. Requests that are found in the library’s database should be kept in the Ready to be sent status for staff to review.

This was entered as NERS enhancement request 7052.

Thanks

In the SNLP workflow the partner changes from the own partner code to the partner who ships the request automatically. Therefore most of the requests have the correct partner when the item arrives at the library.
So most of the time there is no need to modify a partner and the staff's attention to this attribute is not as high as it is to other attributes of the request. If we observe this AFTER receiving the item, there is no possibility to do so.
Because we don't know to which partner we have to send back the item after it has been returned by the patron, we now have to missapply other fields of the request to store this information.
Perhaps not all libraries want to allow their staff to do so, so we suggest a new parameter which can be switched off, if it is not needed.

We would like the ability to view the original XML/ISO messages sent between lender and requester in our Lending requests. There is information we need that doesn’t display in requests when they come into our system.

Examples include:

*Copyright declaration: we need this for copyright compliance reporting purposes

*Maximum cost: if this doesn’t display, we have to confirm that the requesting library accepts our charges if the cost is going to be over the standard charge

*Expiry date: the request status changes to Expired if this date is passed, and the request moves on in the rota

*Need by date: the field is in the request, but the information doesn’t display. We need to be able to see this so we can notify the requesting library if we can’t supply the item in time

*Date and time that request is received: we need to know the date and time a request comes into our system so we can ensure our turnaround time meets the service level – particularly important for Express requests

Being able to view the ISO messages in requests would be invaluable.

When working on resource sharing requests lists (lending and borrowing) the first thing to do is selecting another search entry/term, mainly an aspect at the end of the list, to find a special request, because the author ist never the aspect we search for. The list in the pull down menue is hard coded and there is no option to re-order the list as we need it.
At least we like to achieve that the list starts with the last three search aspects the staff user has used. Alma has to remember them for the logged in staff user similar to the functionality developed for the NUI in connection with other topics (i.e. last location - currently at... or last searches in the persistant search box).
We need this functionality for Resource Sharing Requests as well.

When we go to the list of Lending requests or Borrowing requests (either via the Tasks menu or directly under Fulfillment),
we get requests for both our libraries/campuses. This is the case, even if we have already chosen one of the libraries as our «current location».
When we choose one particular library as the current location it would be very helpful to get a list of request only for this library.
As it is now, we need to scroll down at the bottom of the left-side menu to choose the current Owning library.
Alternatively, if the above solution is not possible, is it possible to move the menu-selection «Owning library» and «Pickup location»
to the top of the menu? We cannot configure this ourselves.