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.
49 results found
-
Add RVMFAST authorities to CZ
Please consider adding RVMFAST to the list of controlled vocabularies mainted in the CZ by Ex Libris.
For French and bilingual institutions in Canada, RVM is an essential tool. While the main RVM authorities are available only to subscribers, RVMFAST is a freely available French translation of the FAST vocabulary. The authorities and updates are available for download from RVM's website (https://rvmweb.bibl.ulaval.ca/rvmweb/rvmfast/supplements_rvmfast.do?locale=en). Adding RVMFAST to the list of controlled vocabularies managed in the CZ would save institutions the work of maintaining local authority files and enable easier adoption.
3 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…
47 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…
3 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.110 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 -
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 -
Intelex Past Masters collection needs better metadata
The Intelex Past Masters
In Alma in the electronic collections I can find the metadata have a structure that follows the structure of the database and not a normal catalogue standard.
A title looks like this: 'Collected works of Ludwig Wittgenstein. On certainty' and there are very few other information, eg. the field for ISBN and the writer has not been filled out.
When I search in Primo, I have to do a very specific search to find the title, since the title is not simply 'On certainty' and Wittgenstein in the writers field. Therefore the ranking gives a very…
4 votes -
Support Storage Location ID in SRU and Barcode API Queries
Hi,
Currently, Alma's BIB SRU interface does not support querying by Storage Location ID. This limits our ability to perform targeted searches for items based on their physical storage location, which is a critical need for institutions managing remote or offsite collections.
We propose the following enhancements to improve Alma's interoperability and search capabilities:
Extend the BIB SRU “q” parameter to support querying by Storage Location ID.
Introduce an ITEM-level SRU endpoint, similar to the existing BIB SRU, that would support more granular item-level searches including by Storage Location ID.
Alternatively or additionally, add Storage Location ID as a searchable…
1 vote -
Allow for an authority file to be addressed by different codes in $2 of various BIB fields
In Alma the authority file, a subject or term stems from, is defined by the content of $2 in various 6XX fields. This code controls the F3 functionality, as well as the linking process and the various jobs like PTC. Each and every authority file is addressed by one specific code.
In the German speaking countries we use an integrated authority file (GND), which amongst names and subjects, also includes genre/form terms. For historical reasons the genre/form terms in BIB field 655 are marked with the official LoC /MARC Genre/Form Code and Term Source Codes “gnd-content” and “gnd-carrier” in $2,…
145 votes -
Save certain subfields from being overwritten via F3 and PTC
When linking names, subjects etc. from authority files in various BIB fields, some cataloguing conventions require giving additional information in certain cases.
One example for such a requirement, stemming from the German speaking countries, is to add the time and place of an auction when linking to the genre/form term “auction catalogs” in BIB field 655 (see attached screenshot). This additional information is, of course, specific for each BIB record and must not be overwritten or deleted, if at a later point in time either PTC processes said BIB record or a colleague invokes the F3 functionality.
Since different subfields…
258 votesHello everyone, for those who raised comments about the correction of 830 $v, could you please provide a detailed, step-by-step explanation of the scenario in which this subfield gets overwritten?
-
Implement Checks on the Authority Heading Type for Institutions Using ID-based Authority Control
Currently, when authority linking in Alma is based on ID rather than text, Alma does not check whether the authority heading type in the bibliographic record matches the heading type in the authority record. For example, Alma will link a 600 tag in the bib record for personal names with an authority record whose heading is in tag 110 for corporate names if their ID matches, even though Alma would not offer that option if F3 were pressed.
We would like Alma to (1) avoid linking in such cases and (2) flag these instances in the authority control task list.
…
2 votes -
Arrow keys now 'stick' in fields in MDE
When navigating through records in MDE, if you've previously typed anything in a field, you now cannot move out of that field using the arrow keys. It's not entirely consistent and sometimes does let you move out the field, while other times it 'sticks' randomly in fields you haven't edited at all, but in general it is extraordinarily inconvenient.
I see using the arrow keys to move within a field was previously suggested as a feature, but even within that suggestion, the idea included the stipulation that if the cursor was already at the start/end of a line hitting up/down…
2 votes
- Don't see your idea?