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.
50 results found
-
Support MARC 956 thumbnail images in Alma Staff Interface
Description:
Currently, Alma Staff Interface does not display thumbnail images originating from MARC field 956, even when these thumbnails are correctly displayed in Primo VE through thumbnail template configuration.
At the moment, Alma Staff Interface only displays cover images resolved through internal mechanisms such as:
ISBN-based cover services (MARC 020)
Digital representations
Internal cover enrichment servicesThis creates an inconsistency between Primo VE and Alma Staff Interface.
For example:
A thumbnail image linked through MARC 956 appears correctly in Primo VE.
The same record in Alma Staff Interface continues to display only the default placeholder icon.It would be very…
1 vote -
Allow All MARC21 Fields Valid for Subfield $5 to be Saved as Alma "Local Extensions"
The Problem:
Alma’s current "Local Extension" model restricts local data to a hardcoded subset of tags (09X, 59X, 69X, etc.). This forces libraries to choose between keeping standard local data in the Network Zone (where it risks being overwritten) or moving it to non-standard local tags.When standard data (like a 700 donor name or a 655 local genre heading) is forced into a 9XX or 69X field, it breaks standard Primo indexing. We lose the ability to have this critical local data indexed in standard Primo indexes.
The Solution:
Update the Alma Metadata Editor and bibliographic validation rules to…1 vote -
Modification date of records that were processed via running a job but no modifications were made, should not change.
When a record is included in a set and any job runs on that set, such as a normalization job, the modification date of the record is updated even if the record itself was not changed. This means the modification date is updated by design in Alma after processing or saving the record. Therefore, it is not currently possible in Analytics to run a report to check how many records were actually updated/modified in the job.
4 votes -
Add full MARC records to CZ for Mohr Siebeck
This collection of Mohr Siebeck eBooks contains many titles with metadata that are too poor and need to be enriched. Could you please follow up with Mohr Siebeck?
MMS-ID: 9919375751300041
Thank you for your intervention!
Kind regards,1 vote -
Enable Full MARC 21 Format for Holdings Data (MFHD) Editing in the Metadata Editor
We request that the Alma Metadata Editor (MDE) be updated to allow direct MARC-level editing for all fields in a Holdings Record as defined by the MARC 21 Format for Holdings Data (MFHD).
In the library industry, a "Holdings Record" is a unified data carrier. It includes the shelving location (852), but also other copy-specific fields such as donor (541), the provenance (561), and the individual item details (876-878). In the MARC standard, the "Holdings" and the "Item" are part of the same metadata record.
While we recognize that Alma’s underlying architecture treats “Items” as child entities of “Holdings”, the…
3 votes -
Quick Links and Keyboard Shortcuts in the Metadata Editor for Enhance the Record Normalization Processes
As a cataloger, I want to create quick links and keyboard shortcuts for normalization processes in the metadata editor, instead of selecting them via "Enhance the record", so that I can work more efficiently.
4 votes -
Allow CZ records to preserve or support local subject access for non-english indexing
We would like Alma to support a stable and sustainable solution for managing local subject access in Community Zone records.
Currently, when CZ records are updated, subject fields (65X) may be overwritten or removed. Although local fields can now be recovered in local indexes, this doesn't solve the core issue: subject access in our language is lost from the standard 65X fields, and this information becomes invisible to our consortial members.
We manage a large and continuously growing volume of electronic records, and the loss of controlled subject access has a significant impact. We have already identified more than 6.000…
107 votes -
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
4 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.
31 votes -
Please add the feature „Chat between Institution Zones“ to the Metadata Editor
Ex Libris should offer the option of creating a chat for each data record. This feature would facilitate communication between individual libraries regarding incorrect data records.
Currently, communication concerning bibliographic records are sent by email via a mailing list. For a library that has many departments with numerous employees, it is difficult to develop a workflow for jointly processing these emails. In a chat, several people within an institution can communicate with each other without having to coordinate internally beforehand.
But smaller libraries would also benefit from this chat function. When several emails are sent back and forth on a…370 votesCould you please clarify whether this request refers to communication between consortia (Network Zone) members regarding their shared data?
-
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 votesCan you please confirm whether the $e subfield is always expected to appear before $0 and $1 in your workflows? If this is consistently the case, it may be possible to address the issue using an XSL normalization rule to automatically position the $e subfield before these subfields.
-
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 -
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…
7 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.
8 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
- Don't see your idea?