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.
651 results found
-
Release notes should be posted
Currently when LibOW is updated to a new version, no notice is given, and no list of new features / enhancements is provided. The changes are sometimes significant. For instance, recently a set of new webhook triggers was added. Release notes should be posted somewhere for LibOW users to review.
12 votes -
Holdings Display
Please revert the display back to what it was before August 2025 updates for viewing holdings for a title. Go back to a full screen (not a sliding window). Show POL in holdings again. This helps serials work when needing to move items to a suppressed record to be able to see the POL and the receiving dates displaying easily.
1 voteStarting from November release it is possible to expand the sliding pannel into a full page as well as resize it using the drag&drop option.
Best,
-
Browse Shelf Listing for call numbers: Improve search for letters with umlauts
Sorting of the whole call number index is generally correct - scrolling through the list, page after page, we see that the call numbers are sorted correctly. But if we search for a special call number (search field "signature"), we do not always get the right entry when it comes to umlauts.
The umlauts should sort like that:
ä = ae
ö = oe
ü = ueWhen searching, it looks like this is the sorting:
ä = a
ö = o
ü = uExample: The results from Bo to Brym in the order when scrolling through the pages:…
417 votesThanks everyone who supported this idea and helped analyzing the request.
Institutions whose Solr search language is set to German will now have German sorting of umlauts in the Browse Shelf Listing search.
As this requires full indexing for call number, the effect of this enhancement will be seen after the November semi-annual indexing is completed.
Best, Alma Product.
-
Revert the changes made to Job: Update PO Lines Information Advanced
This really pertains to Admin >> Run a Job, but please revert the change you made to the Job: Update PO Lines Information Advanced. Currently, the job will NOT run if there are invoices on the PO. Before this change was made it did not matter.
It does not matter to the library because the terms of a continuous order can and do change (it was a subscription, now it is offered as a continuation order), how a library chooses to catalog an item can and does change (a title was a serial, then it became a monographic series) So…1 voteHi all,
The Update PO Lines Information Advanced job has been enhanced following the community's feedback.
For additional information, please refer to the Release Notes
Best,
Liza and the Product Team
-
Portfolio loader and Multiple MMS
When we load portfolios through the Portfolio Loader, Alma attempts to find a match based on the identifier in the Community Zone, in order to get the bibliographic records for the portfolios.
When there are multiple MMS records in the CZ that match the searched identifiers, you get an error and no portfolio is loaded. Currently, there is no internal logic for the portfolio loader to choose between these records, even if some have no inventory at all.
it would be useful to implement a logic that allow to choose between records, at least in the case that some have…104 votesHi all,
I'm happy to update that this idea has been implemented as part of the November 2025 release.
The portfolio loader now supports auto-selecting the preferred MMS (based on inventory and rank) in case of multiple matching records.
read more about this option in the November 2025 release notes: https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2025/Alma_2025_Release_Notes?mon=All#:~:text=Handle%20Multiple%20Matching%20BIB%20Records%20in%20Portfolio%20Loader
Best, Alma Product
-
NR - Normalization rules editor -- fix display to ltr + use monospaced font
1.
Currently there's a problem with the NR editor when there are too many rtl characters (Hebrew, Arabic, etc.) in the NR, the whole display changes to rtl. This renders the NR unintelligible and makes editing it in Alma impossible -- you have to edit it outside AlmaWe would like the direction of the NR editor to be fixed to ltr regardless of the composition of the characters used
2.
We would like to have the NR editor use a monospaced font. This would make the code neater and easier to read24 votesAlma now supports XSL normalization rules, expanding its capabilities beyond the existing DROOLS support. This addition enables more advanced and intricate data normalization. The request of this idea can be addressed using the new XSL normalization rules. For detailed information on using XSL normalization rules, please refer to the May 2025 release notes available at: https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2025/Alma_2025_Release_Notes
-
Purchase requests on network records
When a purchase request is made in Primo VE from a record that belongs to the network, the purchase request shows error when clicking on Approve and order: Failed to create order.
It should be possible to create purchase requests on records belonging to the network. The purchase request should be created in the IZ level and be managed there. The corresponding order, if the request is approved - should also be managed in the IZ level.
5 votesDear All,
This is to inform you that this idea was implemented in Alma May 2025 Release:
When ordering in Primo from the Network Zone (NZ), the purchase requests created in the Institution Zone (IZ) are now linked to the bibliographic record in the Network. Alma first checks for a local MMS ID linked to the bibliographic record in the Network. If such a record exists, Alma uses it for the purchase request. If it doesn't exist, Alma creates one and uses it.
Thanks,
Zohar Shemesh
Alma Product Team
-
General electronic service in Get It should built with information from the main bib and not from related record
General electronic services are built using data from the context object.
When there are related bibliographic records, the context object is sometimes created with the related record's information.
As a result, the general electronic service has the related records information - e.g. ISBN.
Desired outcome
General electronic services in getit should use the main record's data and not related record's data.
5 votes -
Add Alma support for microlanguages and language codes recognised by Library of Congress, including Austlang
Alma’s support for Language for search indexing, facet, and display is hardcoded for 041 to the 3 digit MARC Code List for Languages.
This excludes languages recognised by Library of Congress, such as Austlang languages which were recognised more than 6 years ago in 2018.
This issue has been addressed in Primo in 2021 and 2022 with customer advocacy efforts, but remains a glaring omission within Alma.
See details: https://igelu.org/primo-support-for-austlang-and-iso-639-3/The only option currently within Alma for searching this data is to use the keyword field to search by information such as C15, and then use the Language filter to…
83 votesHello all,
I want to clarify the decision made regarding this request, as it should help make things clearer.
First, we added the option to upload Controlled Vocabularies using a CSV or Excel file, making the process much easier than before.
In addition, we enhanced the 041 $a OTB Controlled Vocabulary list to include ISO 639-3 languages, in addition to the existing MARC21 standard list. This extended list supports search, facets, and other functionality — offering more capabilities than most other lists in Alma. Any additional language codes (e.g., Austlang) can be added to this list by each institution according to its specific needs.
Please note that due to a performance issue, the full functionality will be available in the February 2026 release. For more information on how to use it, please refer to the release notes and online help.
Erez
-
Separate new and deleted portfolios behaviors of "Activate new portfolios associated with service automatically"
"Activate new portfolios associated with service automatically?" has just 2 options (Yes and No), and it doesn't just control what happens when new portfolios are added to the collection; it also controls what happens when portfolios are deleted from the collection. I think there are probably additional use cases besides these as well.
If "Activate new portfolios associated with service automatically?" is set to "Yes":
New portfolios added to CZ collection are automatically activated in IZ
Portfolios deleted from CZ collection are totally deleted from IZIf "Activate new portfolios associated with service automatically?" is set to "No":
New portfolios…191 votesHi all, Happy to share that starting from the May 2025 release it will be possible to define auto-activation and auto-deletion behaviors separately on services activated from the Community Zone. As before, all updates will be reflected in the CZUTL.
-
Create Alma search queries and sets with relative dates
Give customers the ability to query Alma using relative dates. This functionality is currently only available in Alma Analytics, but we would like it to also be available for repository search.
This functionality would be especially useful for creating sets, particularly logical sets that can be used to populate logical collections. One of the most common uses for collections is to showcase new materials (e.g., books, journals, databases, etc. acquired in the last 90 days). However, there is currently no way to build a logical set like this. The best one can do is to select the current year and…
175 votesHey all,
Thank you for submitting and supporting this idea!
Starting from the May 2025 release, Date-related search indexes in the Users advanced search now include new options to search within a moving range of days. This enhancement allows you to create dynamic "moving-window" sets (for example, a logical set of users who expired in the last 30 days).
We're planning to expand this functionality to additional search indexes in upcoming releases.
If there are specific search indexes where you'd like to see this feature implemented, please weigh in on this related idea: Search possibilities as "Received X weeks ago" or "Available X weeks ago".
-
Add "equal" option to the title search "Authority id" index
When searching for titles by authority ID, currently the search supports searching with: Contains keywords, contains phrase, is empty, not contains keywords, not contains phrase, is not empty.
Add the option to also search by "equals".3 votesThis request has already been fulfilled; the equals operator is implemented and available in the Authority ID index.
-
Add "General Notes" at the collection, service, and portfolio levels to Analytics
Please add the following note fields to Analytics:
Electronic Collection:
- General notes (multiple entries)
Electronic Service:
- General notes (multiple entries)
Electronic Portfolio:
- General notes (multiple entries)Why is this necessary?
You can search for many fields in Alma itself, but not all of note fields can be exported from Alma. But this is particularly important for note fields!Thank you very much in advance!
Note: this is a follow-up idea to:
Add "General Notes" at the collection, service, and portfolio levels as indexable/searchable fields
https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/46387843-add-general-notes-at-the-collection-service-an125 votesHello,
We are happy to inform the community that the E-Inventory subject area now includes the "General Notes" for electronic collections, services and portfolios.
Regards,
Hadas
-
Search possibilities as "Received X weeks ago" or "Available X weeks ago"
Libraries sometimes wish to build logical sets from constantly changing data. For example, a logical set of items received in the last 30 days or a logical set of ebook portfolios activated in the last 15 days. The "Receiving date" (Physical items) and "Activation Date" (Electronic portfolios) search indexes only accept a specific date (selectable from a calendar) and only allow the operators "Equals", "Not Equals", "Before", "After", "Is Empty", and "Is Not Empty". It is therefore not possible to build 100% logical sets based on items received in the last 3 weeks and associate them with a collection for…
155 votesHi all,
thank you for supporting this idea!
happy to inform that as of November 2025 release, It is possible to search for titles and inventory using a relative date range, such as titles created in the last month.
read more in the Alma release notes: https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2025/Alma_2025_Release_Notes?mon=All#:~:text=Relative%20Date%20Searches%20Support%20in%20Repository%20Search
Best, Alma Product.
-
Add "Delete or replace URL's SUFFIX" to Job "Change Electronic portfolio information"
Sometimes it is necassary to change or delete the URL in portfolio information for a set of portfolios. It is possible to delete or replace URL's prefix in Electronic Portfolio information, but it is not yet possible to delete or repclace url's suffix .
For us it would be very useful to have both opportunities.100 votesNow in Alma a new option is available to edit static URL suffix in bulk, using the "Change Electronic Portfolio Information" and "Change Electronic Collection Information" jobs.
For more information, see Manual Jobs.
-
Filter OUT cancelled PO Lines
Provide a facet to filter OUT cancelled PO Lines in the PO Line view. We have a lot of cancelled PO Lines with the same title as existing PO Lines, and it is confusing and time consuming to find the 'active' PO Lines. It would help us tremendously if we could filter OUT cancelled PO Lines, perhaps even by default.
13 votesHi all,
Thank you for supporting this idea.
Starting from the Alma August 2025 Release, Users can exclude facets in the PO lines list. For additional information, refer to the Alma Release Notes
Best,
Liza and the Product Team
-
Finished claiming job does not give the library the option to check which vendors received a claim letter
When a claiming job is finished running in Alma you can view “events” from the finished job. This gives a line for each claim processed in the job, and lists three different identifiers: JOBID, POLINEID and VENDORID. None of these identifiers are searchable for the library, and the library then have no option to control what letters were sent in that specific job. If the identifiers listed in the job events were changed to the PO line reference and the vendor code the library would have the option to find the relevant POL and vendor and…
31 votesDear community,
starting from February 2025 release, The "PO Line - Claiming" job report will include PO lines list of claim letters that were successfully sent, and also for send failures.
For more information, see Alma Release Notes
-
“Run a job” and “Create itemized set” should be available from the list of Purchase order lines
When you are in a list of items on a bibliographic post in Alma you have the option to checkmark several items and choose “Manage selected” – “Run a job” or “Add to itemized set”/”Create itemized set”. Now that we have the list “All PO Lines” and can checkmark POLs in the list, it would be practical for these options to also be available for PO lines. Currently you only have the option of creating a logical set (if you add filters to the list) from the list “All PO Lines”. This would make it easier and quicker to run…
8 votesHi all,
I'm happy to inform you that the Alma August 2025 Release introduced new bulk actions related to PO lines search list, including 'run a job' and 'create itemized set'.For additional information, refer to the Release Notes
Best,
Liza and the Product Team
-
Order of action buttons in the POL
In the new PO line interface, the action buttons available when creating a POL is not in a practical order, which causes a lot of our staff to press “save” instead of “save and continue”. This causes the POL to remain in status “in review”. The user also must use more energy to locate the correct action button. We have two different suggestions for solving this:
Move the actions “Save and continue” and “order now” to the right part of the menu line and have this be marked in a stronger color than the other buttons. In the current design…
19 votes -
Metadata editor: LDR form opens automatically
With the November 2023 release, we noticed a change in the metadata editor.
With the configuration "forced form editing" activated, whenever a record is pushed to the metadata editor, the LDR form is opened automatically and this is irritating, since cataloguers do not necessarily want to start working on the LDR, and the display of the form takes up a lot of screen space. Moreover, the LDR form opens again when saving the record.
We would like to suggest the following adjustments:
- the LDR form is not automatically opened when entering a record
- the LDR form is not…6 votesThis was completed and available in the February 2024 release.
.JPG){kind=link}
- Don't see your idea?