Alma
Your feedback matters to us. Help us improve Alma by telling us what you’d like to see using the message areas below. You can also can support something already posted.
We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.
For more information please review our FAQ and guidelines. Thank you.
- or
No existing idea results
- ~ No ideas found ~
1733 results found
-
Add GND to the Linked Open Data (LOD) editor, Alma Lookup Service
For now, the service only includes a few sources. We would like to add the GND vocabulary. This vocabulary is very important because a large number of libraries use it.
1 vote -
Flexible and normalized comparison of portfolio coverage dates in Overlap & Collection Analysis
Currently, Overlap & Collection Analysis compares portfolio coverage dates exactly as they appear in the portfolio coverage fields. As a result, equivalent coverage ranges are not always recognized as matches when the dates are recorded at different levels of detail or when some components are missing.
For example, coverage such as:
• 2.1.2016, Volume 1 Issue 1
and
• 2016, Volume 1 Issue 1
may represent the same start point, but the system treats them as different because one includes a full date while the other includes only a year.
In many knowledge bases and vendor data, coverage dates are inconsistently populated — sometimes year only, sometimes year and month, and sometimes full dates. This leads to inaccurate or misleading overlap results.
Proposed enhancement:
Enable configurable comparison granularity, allowing institutions to choose the precision used for matching, for example:
• Year only
• Year + month
• Full date (year + month + day)
This would allow comparisons to succeed even when some date components are not populated, and would let each library select the level of precision that best fits its collection analysis needs.
Expected benefit:
This will:
• Improve matching accuracy in overlap analysis
• Reduce false mismatches caused by different levels of date detail or missing components
• Provide more reliable overlap calculations across vendors and knowledge bases
• Support better collection management decisions (e.g., which collections to activate or deactivate)
• Minimize manual normalization and data cleanupCurrently, Overlap & Collection Analysis compares portfolio coverage dates exactly as they appear in the portfolio coverage fields. As a result, equivalent coverage ranges are not always recognized as matches when the dates are recorded at different levels of detail or when some components are missing.
For example, coverage such as:
• 2.1.2016, Volume 1 Issue 1
and
• 2016, Volume 1 Issue 1
may represent the same start point, but the system treats them as different because one includes a full date while the other includes only a year.
In many knowledge bases and vendor data, coverage dates are…105 votes -
Contribute URL Type (Override) to community-managed collections when contributing portfolio changes
I locally changed the Free E- journals link for bioRxiv (PID: 53441287610000041) to a dynamic URL:
IF(rft.doi)
https://doi.org/openurl?url_ver=Z39.88-2004&rft_id=info:doi/{rft.doi}
IF()
https://www.biorxiv.org/This allows the links on all the bioRxiv CDI records to go directly to the article. However, I can't contribute this change to the community because the "URL type (override)" won't go with it. So, my idea is to include that setting with any portfolio changes contributed via community-managed collections. This will allow the community to write more dynamic URLs and perhaps get those Free E- Journals links to link directly to articles, rather than to the journal's homepage.
3 votes -
Allow configuration of the default destination location for item move requests
Currently, when creating an item move request (temporary or permanent) in Alma, the Destination Location field is pre-populated with a default location. This default value cannot be changed or cleared by configuration.
We request an enhancement that would allow institutions to control this behavior - specifically, the option to leave the Destination Location field blank by default. This would require staff to actively select the appropriate destination location from the dropdown list, reducing the risk of accidental or incorrect moves.
This behavior would align item move requests more closely with patron physical requests, where required fields are not pre-filled and must be intentionally selected by staff.
Currently, when creating an item move request (temporary or permanent) in Alma, the Destination Location field is pre-populated with a default location. This default value cannot be changed or cleared by configuration.
We request an enhancement that would allow institutions to control this behavior - specifically, the option to leave the Destination Location field blank by default. This would require staff to actively select the appropriate destination location from the dropdown list, reducing the risk of accidental or incorrect moves.
This behavior would align item move requests more closely with patron physical requests, where required fields are not pre-filled and…
3 votes -
Add “Report to Ex Libris” Option to Failed Scheduled Alma Jobs
Scheduled Alma jobs that end with errors do not currently provide a built-in “Report to Ex Libris” option. Reporting such issues requires opening a support case manually and copying information from the job report.
Idea: Extend the existing “Report to Ex Libris” functionality (available at the portfolio level) to scheduled Alma job reports.
For scheduled jobs that end with Error or Failed status, allow users to open a reporting screen, pre-filled with the relevant job details (Job ID, process ID, error message).
Benefit: Provides a consistent reporting experience for recurring system jobs and improves accuracy of job-related support cases.139 votes -
Access host bibliographic record for "bound-with" relationships via API
Currently if you have two or more bibliographic records in a "bound-with" relationship via the 774 MARC field, the MARC data on the host bibliographic record contains the MMS ID of the child records, but there is no information on the child record to show the relationship. The Alma staff interface and the Primo interface clearly know that the relationship is there, because the holdings of the host bibliographic record are displayed in both interfaces. The information is clearly indexed, therefore, but is currently inaccessible to API users, limiting the ability to write scripts and interfaces that handle this concept.
The API should be improved to provide access to the linkage in both directions.
Currently if you have two or more bibliographic records in a "bound-with" relationship via the 774 MARC field, the MARC data on the host bibliographic record contains the MMS ID of the child records, but there is no information on the child record to show the relationship. The Alma staff interface and the Primo interface clearly know that the relationship is there, because the holdings of the host bibliographic record are displayed in both interfaces. The information is clearly indexed, therefore, but is currently inaccessible to API users, limiting the ability to write scripts and interfaces that handle this concept.
…
1 vote -
Allow relinking of items to other holdings records via API
The Alma user interface allows cataloguers to relink an item onto a different holdings record, either on the same bibliographic record or a different one. It is not possible to relink an item via the API.
If a library wishes to do a major restructure of holdings records via API (e.g. post migration from another system), it is currently impossible. For example, during migration of our early printed books from our old LMS, Ex Libris craeted one holdings record per location, despite there being multiple distinct items with different shelfmarks and provenance history, which should have separate holdings records. We have the skills to write a script to split these items across new separate holdings records, but the API does not exist to do this. Instead our script will have to delete and recreate items, which would lose the record history.
The Alma user interface allows cataloguers to relink an item onto a different holdings record, either on the same bibliographic record or a different one. It is not possible to relink an item via the API.
If a library wishes to do a major restructure of holdings records via API (e.g. post migration from another system), it is currently impossible. For example, during migration of our early printed books from our old LMS, Ex Libris craeted one holdings record per location, despite there being multiple distinct items with different shelfmarks and provenance history, which should have separate holdings records. We…
5 votes -
Add No Charge parameter to Update PO Lines Information job
Please add the No Charge field to the Update PO Lines Information job to allow a library to set the No Charge value on PO Lines in bulk. Currently, neither this job nor the Update PO Lines Information - Advanced job allow this value to be modified, though a user may modify the POL manually.
This is valuable to acquisitions staff that are cleaning up POLs for titles ordered in a subscription package, whether the POLs were migrated from a previous system or they were added to Alma incorrectly. Another POL will be used to encumber and invoice the subscription. However, since Alma does not allow a $0.00 price on a POL, these POLs tend to carry inappropriate $1.00 encumbrances which affect fund reporting. However, modifying the No Charge value hides the pricing and funding section of the POL and removes encumbrances.
In addition to adding this parameter to the Update PO Lines Information job, we request that it should also be valid to modify this value via the Acquisitions API without creating an error.
Please add the No Charge field to the Update PO Lines Information job to allow a library to set the No Charge value on PO Lines in bulk. Currently, neither this job nor the Update PO Lines Information - Advanced job allow this value to be modified, though a user may modify the POL manually.
This is valuable to acquisitions staff that are cleaning up POLs for titles ordered in a subscription package, whether the POLs were migrated from a previous system or they were added to Alma incorrectly. Another POL will be used to encumber and invoice the subscription.…
1 vote -
Supply more accurate cancellation reason when Requests – Handle Expiration Step automatically cancels booking requests
If a booking request releases its release time before staff have had a chance to pull the item, I believe Alma's default behavior is for the Requests – Handle Expiration job to assign Missing status and to send a FulCancelRequestLetter stating that the "Requested material could not be located". This causes patrons, who sometimes pick same day booking release dates, to think we've lost their requested items. A better cancellation reason would be BookingReleaseTimePassed/Booking request passed its release time.
3 votes -
Community Zone collection for University of Florida Press journals
Requesting a Community Zone collection for the journals published by University of Florida Press (UF Press) / University Press of Florida (UPF), as listed at https://floridapress.org/journals-home/.
1 vote -
Retain recall overdue fines even if the request is cancelled
When a request is cancelled, we would like the fine incurred for an overdue recall to remain in place (for the days up until the recall is cancelled) to deter customers from keeping a title that may be required by others. Currently, overdue fines disappear from manage patron services when a request and the recall is cancelled.
6 votes -
Hide Note field in Assign To dialog unless Send as Email checked
When the "Send as Email" checkbox is not checked, the assignee will never see the Note. The only place the Note is recorded is the General Assign To Letter. If the "Send as Email" checkbox is unchecked, no letter is generated.
1 vote -
Add Resource Sharing Partner Setting for ILLiad Cleared Status
When a library creates a resource sharing partner for ILLiad and checks the Create User in ILLiad box, Alma does not pass a Cleared value in the CreateUser ILLiad API call. This means all ILLiad user records created by Alma need to be manually cleared. Please add a new setting to the ILLiad resource sharing partner type that allows libraries to select a Cleared value of either "No" or "New".
31 votes -
Add ability to clear/delete Birth Date data via the Update/Notify Users job.
A library may choose to store a user’s birth date data in their user records, but may decide later to stop storing it. In addition, in an AFN environment, one member library may choose to store this data locally and then share it with AFN partners through their Linked Account Shared Fields settings. If this setting is later changed to exclude this data from future Network user records, it has no impact on pre-existing Network user records in an AFN partner’s IZ, who continue to retain the date until said Network user records are refreshed.
Impact of Problem – Currently, there is no mechanism in Alma to run a batch job for clearing/deleting the birth date field data from user records, requiring instead a manual, one by one update process. Being able to use the Update/Notify job to complete this task is simply much more efficient.
A library may choose to store a user’s birth date data in their user records, but may decide later to stop storing it. In addition, in an AFN environment, one member library may choose to store this data locally and then share it with AFN partners through their Linked Account Shared Fields settings. If this setting is later changed to exclude this data from future Network user records, it has no impact on pre-existing Network user records in an AFN partner’s IZ, who continue to retain the date until said Network user records are refreshed.
Impact of Problem – Currently,…
1 vote -
Pop-up window with information about blocks and reader's fees when create a request
It would be helpful if, when filling out the user request form in Alma, a pop-up window with information about the users's blocks and financial obligations appeared when their card number was entered.
A pop-up window exactly like the one that opens when you open a patron's account using the “Manage Patron Services” option.This solution would allow the users to be immediately informed of their obligations and avoid being sent from one station to another.
For example: In our library, fines can only be paid at the station on the ground floor. If the employee at that desk orders items for the patron to be picked up on the third floor and does not notice that the reader has a fine, the reader will go to the third floor. There, the loan will be blocked and they will have to return to the ground floor and then back to the third floor to pick up the items they ordered.
It would be helpful if, when filling out the user request form in Alma, a pop-up window with information about the users's blocks and financial obligations appeared when their card number was entered.
A pop-up window exactly like the one that opens when you open a patron's account using the “Manage Patron Services” option.This solution would allow the users to be immediately informed of their obligations and avoid being sent from one station to another.
For example: In our library, fines can only be paid at the station on the ground floor. If the employee at that desk orders…
20 votes -
Funds and Ledgers: Encumbered balance: Linked orders: limiting to POL with outstanding charges
In the “Funds and Ledgers” section, the overview for each allocated fund shows, among other things, the amount of the expendede and the amount of the encumbered balance
If you follow the link “expended balance,” the orders with currently paid invoices are then listed. Very good.If you follow the link “encumbered balance,” all orders are then listed—including those with invoices already paid in the respective year.
This is apparently the behavior desired by ExLibris:
https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/080Analytics/Alma_Analytics_Subject_Areas/Funds_Expenditure
However, this is very confusing for us, because when working quickly, we compile the list as an Excel file and may not notice that all orders are included here. It would make more sense for us to only find the outstanding order charges for the respective year here.In the “Funds and Ledgers” section, the overview for each allocated fund shows, among other things, the amount of the expendede and the amount of the encumbered balance
If you follow the link “expended balance,” the orders with currently paid invoices are then listed. Very good.If you follow the link “encumbered balance,” all orders are then listed—including those with invoices already paid in the respective year.
This is apparently the behavior desired by ExLibris:
https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/080Analytics/Alma_Analytics_Subject_Areas/Funds_Expenditure
However, this is very confusing for us, because when working quickly, we compile the list as an Excel file and may not notice that…1 vote -
maria.nordgren@umu.se
Allow 2 e-mail addresses to be in use for patrons who needs this. We have patrons that goes from being employee to private individual. Their e-mail as an employee stops working and they reciev no information about loans and so on. This would help a lot
3 votes -
Improve cookies on Alma and other Clarivate sites
Alma-specific:
* Re-configure the OneTrust settings so that performance cookies default to off
* Targeting cookies should not be present at all (my Alma usage is useless to advertisers and if it's not then that's really concerning!) but if you must have them then these should also default to off.
* Leganto and other systems that are configured in Alma should respect any opt-out settings the user has already specified on the Alma site (and vice versa)Clarivate-wide:
* Someone should have a thorough review of OneTrust configurations across the whole conglomerate to make all optional cookies default to off, remove unnecessary cookies (ie social media cookies and especially targeting cookies), and make more Clarivate sites respect user preferences as expressed on other Clarivate sites.Background - current situation:
Clarivate has a vast range of library/research related websites. They all use OneTrust to manage cookies, but are almost all configured separately (so even after you've set your preferences on one site, other sites don't apply the same preferences) and differently (so some sites default to optional cookies off while others default to on).The best site is ProQuest Support. This has a lot of cookies (Functional, Targeting, Social Media, and Performance) but they all default to off, so you can open it up and quickly confirm that. Moreover if you then go to ProQuest Central, it appears to remember and respect those same preferences.
Primo (both VE and NDE) doesn't have a cookie banner at all. I hope this means that it doesn't use cookies? (Though if Primo can manage without cookies I wonder why the other sites can't.)
Other sites default to having cookies on: IdeaExchange only has Performance cookies, while Knowledge Centre, Developer Network, Alma, Leganto, and Web of Science all have both Performance Cookies and Targeting Cookies.
This means that if, for example, you've cleared your browser cache for some reason, then when you open Alma, Leganto, Knowledge Centre, Developer Network, ProQuest Support, and IdeaExchange, every single one of these sites separately wants you to manage your cookies. Also if you start on ProQuest Support where cookies default to 'off' you may assume the same is true on the other sites, and try to save time by clicking 'confirm my choices' without clicking every individual tab first, not realising that this is actually setting them to 'on'.
Alma-specific:
* Re-configure the OneTrust settings so that performance cookies default to off
* Targeting cookies should not be present at all (my Alma usage is useless to advertisers and if it's not then that's really concerning!) but if you must have them then these should also default to off.
* Leganto and other systems that are configured in Alma should respect any opt-out settings the user has already specified on the Alma site (and vice versa)Clarivate-wide:
* Someone should have a thorough review of OneTrust configurations across the whole conglomerate to make all optional cookies default to off,…23 votes -
General Electronic Service Batch Import and Export Option
Background:
The General Electronic Services (GES) provides essential options to customize the view and features for patrons. Currently, the GES only allows service availability rules to be added one at a time. However, libraries often need to manage extensive and complex availability rules, sometimes with very little notice.Request:
Add the ability to add, update, or remove service availability rules in bulk using an Excel or CSV file. In addition, provide the ability to export service availability rules in a format compatible for future uploading.Why:
* In cases where we're providing alternate access to a resource, we may need to add a hundred or more individual ISSNs. This is extremely time consuming.It would allow easier testing of complicated rules. Unsuccessful tweaks to the rules could be overwritten via a prior saved file without having to remember and back out the specific changes or creating numerous test GES.
For consortia, the current distribution setup requires us to distribute all the General Electronic Services to every member institution or none. This setup only works for consortia that are highly harmonized. In concert with the Consortia Dashboard, adding a batch import option would allow us to streamline customized management of our member institutions without requiring a rewrite of the current distribution mechanism.
It expands Alma's capabilities to prepare us for use cases we haven't even thought of yet but may need to implement quickly.
Note: Sharing General Electronic Services in the Community Zone could help with consortium sharing in some cases but may include more information than we would want to display to people outside our system, particularly when in the middle of negotiating with other vendors. Regardless, it does not help with the initial work of needing to add service availability rules one at a time.
Background:
The General Electronic Services (GES) provides essential options to customize the view and features for patrons. Currently, the GES only allows service availability rules to be added one at a time. However, libraries often need to manage extensive and complex availability rules, sometimes with very little notice.Request:
Add the ability to add, update, or remove service availability rules in bulk using an Excel or CSV file. In addition, provide the ability to export service availability rules in a format compatible for future uploading.Why:
* In cases where we're providing alternate access to a resource, we may need…14 votes -
Metadata update for the “Kohlhammer eLibrary Gesamt” collection.
The metadata for this Kohlhammer collection is very poor for publications from 2025 onwards:
Collection ID: 614920000000005630
MMS ID: 9929441643200041Please ask Kohlhammer to update the metadata.
Thank you in advance.1 vote
- Don't see your idea?