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.
53 results found
-
Update metadata for Inlibra collections
The metadata for Inlibra in the CZ is extremely poor. Please contact Inlibra to update their metadata.
1 vote -
Add Bloomsbury Law 2026 Collections to Alma CZ
Can you please add all the Bloomsbury Law 2026 Collections to Alma CZ? (Including- ‘Bloomsbury Collections Hart Publishing 2026’) Thank you!
1 vote -
AI Metadata Assistant
The AI Metadata Assistant is limited to processing four pages or four files per upload. Enabling batch uploading would better support larger metadata workflows.
1 vote -
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 -
List of possible CZ electronic collection types are inadequate
According to Alma documentation and the answer from ticket 08300011 CZ electronic collection types can be characterised as:
Abstract & Index
Book
Journal
Mixed
OPAC
Web ServiceOur library has linked to CZ collections which only have streaming video, or streaming audio portolios. We think it would be better if there were more content types available to CZ collections to better reflect their contents
2 votes -
Create an All Open Access CZ Collection for Elsevier ScienceDirect Journals
Could a CZ collection be created for Elsevier ScienceDirect journals that are completely open access leaving out hybrid journals (or what Elsevier terms as "contains open access" or "subscribed & complimentary"). That information can be found on their web site: https://www-sciencedirect-com.proxy.binghamton.edu/browse/journals-and-books?contentType=JL&accessType=openAccess
If a title becomes open access after a specific date, that information can be found on the journals "All issues" page (see attached showing that Advances in Nutrition became OA "31st December 2022").
2 votes -
Add an API endpoint to rerun an import profile job that failed
We are monthly running an automated import profile to import electronic resources. Almost every time the import profile job finishes with status Completed with Errors and needs to be manually "rerun". This is a documented behavior: https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/060Record_Import/080Monitor_and_View_Import_Jobs#Rerun.
We would like to have an API endpoint through which we can simply rerun the import profile job that have failed due to the error "Failed in Commit after calling NZ" in some of it's files. This would allow to have the whole import process truly automated and without the need to manually intervene every time it runs.
2 votes -
Linked Data Enrichment Moves $e Relator Subfields to Incorrect Positions When Saving Authorities with F3
When saving a name authority record in Alma using the F3 function, the Linked Data Enrichment process is causing the $e relator subfield to move to an incorrect position within the field. Instead of maintaining the expected order (e.g., $a, $e, $1), the $e subfield is often placed at the end or in another unexpected location after $0/$1 subfields are added. This disrupts the intended structure of the authority field and creates extra manual work for cataloguers.
Attempts to correct the placement by copying and pasting the $e subfield do not work as expected—Alma consistently pastes it at the end…
48 votes -
ensure that when 'po_line_description_update_upon_bib_change' enabled, subfield A does not get overwritten by subfield L in 022
Sharing description from our Cataloger, CH:
We believe the following describes a defect.
Support indicates it is an enhancement request and suggests we propose on Idea Exchange.
Background:
1) We turned on the ‘polinedescriptionupdateuponbibchange’ enhancement in the sandbox.
2) The enhancement overwrote the $$l instead of pulling in the $$a from 022 – this behavior describes a defect
None of the following 3 options allow us to properly use the ‘polinedescriptionupdateuponbibchange’ enhancement:
1. Ideally, we want to enable the ‘polinedescriptionupdateuponbibchange’ function to…10 votes -
Enable conversion of English vocabulary in NOTE field to 336/337/338 fields for records with 040 $$b eng
Currently, the system supports conversion of Japanese vocabulary in the NOTE field (e.g., "Content Type: text (ncrcontent)") into structured 336/337/338 fields for records with 040 $$b jpn,. However, a similar conversion is not applied to records with 040 $$b eng, even when the NOTE field contains English vocabulary in the same format.
We request that the same conversion logic be extended to records with 040 $$b eng, so that:
Example:
NOTE: Content Type: text (ncrcontent), Media Type: unmediated (ncrmedia), Carrier Type: volume (ncrcarrier)
-->
336 $$a text $$2 ncrcontent
337 $$a unmediated $$2 ncrmedia
338 $$a volume $$2 ncrcarrierThis…
4 votes -
NACSIS-CAT Could App: Enable English output in NOTE field when converting 336/337/338 fields for records with 040 $$b eng
Currently, when converting 336/337/338 fields to a NOTE field in Alma --> NACSIS-CAT mappings, the output uses Japanese vocabulary regardless of the cataloging language. For records with 040 $$b eng, we request that the NOTE field be generated using English vocabulary to match the cataloging language.
Example:
Expected output for 040 $$b eng:
336 $$a text $$2 ncrcontent
337 $$a unmediated $$2 ncrmedia
338 $$a volume $$2 ncrcarrier
→ NOTE: Content Type: text (ncrcontent), Media Type: unmediated (ncrmedia), Carrier Type: volume (ncrcarrier)Current output:
→ NOTE: 表現種別: text (ncrcontent), 機器種別: unmediated (ncrmedia), キャリア種別: volume (ncrcarrier)This enhancement would ensure consistency…
3 votes -
To be able to remove the LOCAL marking of marc fields
Now, if a field in a record is to be 'un-local', you must delete the field and recreate the field without the local indication. An option to de-localize from the menu in MDE would make a better workflow.
1 vote -
Display personal metadata editor history of opened/edited records
Currently in Alma's All Titles search you can see a list of records you have previous looked at, but it would be helpful in the metadata editor if you had a list of records that you have opened recently. Even a list of 5-10 would helpful.
7 votes -
Información del campo-Editor de metadatos
En los diferentes campos de un registro en el editor de metadatos la información del campo podría estar en castellano.
1 vote -
With the implementation of AI Metadata Assistant, a streamlined process for exporting records created in Alma to OCLC would be nice.
...and if it could automatically set holdings and loop back to Alma and insert an 035 with the newly assigned OCLC# that would be even nicer.
1 vote -
Request for a List of Selectable Special Characters in the MDE Virtual Keyboard
Request regarding the MDE virtual keyboard for inserting special characters, which became available with the August 2025 release.
I would like to be able to view all available characters at once, or to change the order of the character code blocks in the drop-down menu.
It would be especially helpful if the characters could be displayed in Unicode order.
Currently, characters are grouped and selectable via a drop-down menu, but this structure requires users to know which set contains the character they want to input.
This makes the process inconvenient, especially when searching for less common characters.126 votes -
Expanding Unicode Tool range in Metadata Editor
The new Insert Unicode Characters tool in the Metadata Editor should be expanded to include the 0300-036F range of characters. This range includes several diacritics that are commonly used by catalogers, including the ligature (0361), candrabindu (0310), and combining diaeresis below (0324).
21 votes -
MDE Virtual Keyboard – Add Welsh as a separate language option.
The new Virtual Keyboard for Inserting Special Characters and Diacritics in the Metadata Editor has many different language options. However Welsh is not amongst them.
Can Welsh be added as a separate language.
21 votes -
Reloading several records from the union catalog at once
I would like to update several records from the union catalog at once, for example all the records within an itemized set. So far, this is only possible for individual records in the MDE ("Reload record from central catalog"), which is rather exhausting. It would be much easier if there was a button saying "reload records" by which you can push all checked items to the MDE and simultaneously reload the records from central catalog.
In this way, we could easily and quickly update bibliographic records from the "Failed to update delete" event in Analytics. Another use case would be…
15 votes -
Allow a NR to run with the PTC job
TL;DR:
We would like to have the ability to run a normalization rule whenever the PTC modifies a record.Background:
In November 2024 Ex-Libris added a new functionality to the PTC job:
MARC 21 Preferred Term Correction Can Flip Headings with Cross-Reference in Different Field
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2024/Alma_2024_Release_Notes?mon=202411Problem:
The PTC job only changes the first indicator correctly when the PTC job changes a field into 630.
in all other cases, the existing indicators remain.
We opened a case and spoke directly with Ex-Libris, but were told that the PTC job runs as intended, and that not handling the indicators is not…46 votes
- Don't see your idea?