Right now, if we add an interested user to a PO Line, they receive a notification when the book is received by the library. They often then make their way to the Access Services desk almost immediately, assuming a request was placed on the book, and anticipate checking it out. However, the title is usually still in Technical Services for end processing, copy cataloging, etc.
We would like to submit an enhancement request that this feature be more customizable, allowing us to delay the notice being sent to the interested user until the book is out of processing and has a location relating to Fulfillment or the stacks.

We'd want to be able to control the anonymisation of requests, resource sharing requests and fines and fees in a similar way to loans. In particular we'd like to be able to set a parameter for days since user expiry and since the request or fine was complete.

This would allow us to create a clear policy for anonymising and purging data in Alma so that all data was treated in the same way i.e. could say that all data was anonymised or purged X number of years after user left. It would also allow us to be confident that we are only anonymising data that we no longer need.

Currently it is not possible to configure a localized version of the basic loan status codes (e. g. "recalled" or "normal") on institutional level. Instead there are static translations which are set for all Alma institutions - for example (german) "Zurückgerufen" for "recalled". That specific translation, displayed in the loan list in Primo >> My Account, creates confusion among our users since the correct term in that case should be "Vorgemerkt" ("put on hold").

We need a possibility to configure the localization of loan status codes on institutional level - no matter if in Alma or in the Primo code tables.

It would be helpful to have a waitlist functionality for short-term loans (i.e. for reserve items). This would allow patrons to put their name on a list to be next in line once a short-term loan item has been returned. Alma would send an email/text to the patron when the item is returned telling the patron they have a specific window of time (e.g. 5 minutes, configurable by the institution) to check out the item. During that window of time no other patrons can check it out. After the window of time has expired the next person on the waitlist receives an email/text from Alma saying they can now check out the item.

For the circulation desk operator it would be helpful to have a waitlist page in Alma that displays which items are currently on the waitlist, how much time is left in each one before the window of time expires. This will help operators to know at a glance where all the waitlisted items are in the waitlist process. This waitlist system is different from a booking request because the waitlist does not require a patron to select the date and time of when they want an item. Instead, it is simply a list of names of patrons who want to be next in line when an item arrives. The waitlist functionality would only be available when an item is checked out; a patron can't put their name on the waitlist if the item is on the shelf.

Ideally the waitlist function could be done by both staff and patrons, but this should be up to the Alma institution. The institution can decide whether to turn waitlist function on at all. If they turn it on, it will at a minimum be administered by staff. Additionally, they can decide to turn on a patron-facing side that allows patrons to add their names to the waitlist. Ex Libris has also developed an embargo period on loans, which means items can't be checked out to the same patron within a specified window of time. This is very helpful, but it is not the same thing as a waitlist functionality. We need a system that will let patrons get in line for a loan.

I have noticed there are several ideas suggested in the ideas exchange regarding linking a patron's name and/or ID to their record in Alma.
These include:
- 'Link patron loan to patron record' (posted 25/05/2016)
- 'Hyperlinking from request queue/holdshelf to patron record' (posted 21/09/2017)
- Ability to view patron data via patron ID link in resource sharing' (posted 11/01/2018)

I have one more to add to the list - linking within 'Manage item returns'.
When an item is returned, the patron returning the item is displayed in the 'Patron' column, with a hyperlink to their record, and the option of pop-up information. In the attached example, our next step is to post the item to the next patron, displayed in the 'Next step' column. Unfortunately this column does not have a hyperlink to the patron record, or the option of pop-up information. As it does not link through to the record or display address information, we then have to exit out of 'Manage item returns' and do a separate search for the patron in either Admin > Manage users, or Fulfillment > Manage patron services.

Linking from the patron name to the patron record would assist workflow significantly in many areas of Alma. It seems to be an ongoing theme in the ideas exchange and I hope ExLibris will consider this enhancement in the near future.

At minimum, add the ability to search Fulfillment Network (FN) patrons in the Requester field of a Physical Item Request, like we can in Manage Patron Services, Return Items, and Scan in Items.

Use case: one of our patrons requests an item from Interlibrary Loan (or from our shelves, but we discover the item is missing), and we want to convert that to a Fulfillment Network request. Currently, we have to contact the patron and direct them to Primo, where they must find the item at a FN library and place the request themselves. To make things more seamless for the patron, we would like to be able to contact a FN library and have them initiate a Physical Item Request for our patron. In order for that to happen, the Requester field must be able to find patrons at another institution.

Ideally, we would like the ability to complete the request in Alma ourselves by looking up the FN item and placing the request. This would be similar to the "Initiate consortium fulfillment requests for items in another institution from Alma" idea (https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/17887696-initiate-consortium-fulfillment-requests-for-items), but for Fulfillment Networks as well as consortia. This would first require the ability for FN libraries to search each other's items in Alma, as consortia can.

Currently the only way to use records from NZ in an IZ is to search them in the NZ and perform an action like "order" or "link" on every single record one by one. There are, however, situations where an IZ wants to use a bulk of records. For this purpose we need a possibility to link records in bulk and create inventory for the linked records.

We imagine a linking job that takes as an input a logical or itemized set of records saved from a search in the NZ. The linking job can create physical and electronic (and digital) inventory, similar to current import profiles. The inventory operations for electronic inventory should include an option to specify the desired action if the record and a portfolio exist already in the IZ, out of the following choices:

- Add new portfolio.
- Update portfolio information (the URL).
- Don't do anything.

Use case:
The NZ loads monthly updates from e-book vendors where the IZs have purchased different packages. The workflows for group inventory aren't applicable here because the NZ doesn't possess the necessary information for determining who has rights to which portfolio. OAI is no option because this currently creates duplicate portfolios each time a record gets updated in the NZ. The workarounds currently in place involve sending files back and forth which is error prone and not very efficient.

Currently, the display of holdings in Primo for multi-volume monographs is random.
Alma only allows to configure the order of locations by "their proximity to the patron, according to the library IP address”. However, holdings with the same location but different call numbers are not sorted in any meaningful way.

When we catalogue a multi-volume monograph we create a different holding record for each volume, so we cannot use the “item sort routines” to adjust the display in Primo, because they only apply to items within the same holding.

Currently, our patrons see things like this:
http://primo.sns.it/primo_library/libweb/action/display.do?tabs=requestTab&ct=display&fn=search&doc=39pis_alma2150514590002521

We’d like to be able to sort the holdings primarily by location and secondarily by call number, so that the holdings pertaining to different volumes of the same publication would be displayed in the proper order.

There are two other ideas about the sorting of holdings in the GetIt Tab, but I think
they don’t overlap
“Sort of holdings by location (A-Z) in Primo GetIt” is about sorting locations alphabetically by name
“Configure the order of the holdings records in the GetIt tab” is about sorting locations by loan period