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.
124 results found
-
Add option to batch edit 852 $k and $m in Holdings through the Change Holdings Information Job
Would love to see the option in the Change Holdings Information Job to be able to apply/remove/change a shared call number prefix or suffix on a set of records. This would greatly improve the efficiency of metadata management for collections of physical items.
9 votes -
End date confusion
Inconsistent formatting of dates in different places in Alma leads to confusion. Dates in coverage statements are fomatted mm/dd/yyyy but dates in other places, such as 'Creation date' or 'Modification date' are sometimes formatted dd/mm/yyyy. Ex Libris should start using a standard and consistent date format, namely, the ISO 8601 Date and time format, YYYY-MM-DD, see https://www.iso.org/iso-8601-date-and-time-format.html
5 votes -
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 votesHello everyone,
I’d like to share our plans to introduce support for XSL (Extensible Stylesheet Language) normalization rules. This new feature is designed to handle complex normalization tasks and offers the flexibility of a full programming language, enabling advanced data manipulation. It will complement our existing normalization rules based on DROOLS, preserving all of its current capabilities.
Would the addition of this new type of normalization rule address the requirement outlined in this idea?
-
Add the option to the item call number in the Table customization list
Adding "Item Call Number" to the "Table customization" would be very helpful for us. Bib has holding call number, item call number. Item call number is also important to us, by the way, sort by item call number would make our job more easier. Thank you.
1 vote -
Add "search internal resources" option to MDE menu
Our Acquisition staff's workflow is to create brief records at the IZ level for donations etc., when we bring it into the MDE to search for an existing full-level record we are only given the option to "search external resources". We'd like to be able to search internal resources (NZ records) within the MDE (find matches is limited and does not work in most cases--we often discover after we've brought in a record that it did indeed exist in the NZ).
2 votes -
Index 532 field
MARC21 field 532 should be indexed in Alma and Primo. This is important for accessibility notes.
4 votes -
Add Normalization Process to perform "Expand from Template"
The "Expand from Template" offers an option to select a template and to expand the currently opened bib record in the Metadata Editor, supporting the options to Override, Add missing and add all.
As a systems librarian, I would love to have an option to perform this action via a normalisation process.
Currently, the only way to implement an expand from template via a normalization process is to translate it into normalization rules, which is rather tedious.
If I could simply use the template in a normalization process, that would save me much time and effort.
1 vote -
MDE expand from template CZ records
Alma currently doesn't have the ability to "expand from template" for Community records. The option will enable MDE users to use a template to apply multiple local extension fields to CZ records, minimizing the unintentional error of changing the CZ records for everyone.
7 votes -
Ability to sort subfields in holding records
Currently, there is an option to sort subfields for BIB records, but there is no option to sort subfields for HOLDING records.
As an administrator for Alma, it would be helpful to have the ability to sort subfields in holdings records. For example, I was adding a subfield 3 to 583 holding records via normalization rules and the subfield was added at the end of the holdings tag. I desired the subfield 3 to be listed first in the 583, but it was not possible to do.20 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 votes -
Suppress from Public Displayed on Export
A field for indicating if records are currently suppressed from discovery should be standard on all exports directly coming out of Alma. Having this information directly available would greatly help in tracking data pulled from Alma without having to go into individual records first, or pulling a list from Analytics first to cross-reference.
It seems to be a major component missing, especially from the Export (All Fields) list.4 votes -
Improvements for the MDEs left pane
The left pane in the MDE is a very helpful tool for navigation in daily business. With the following improvements it could be even more helpful:
- Customization of the display of the different databases in all the tabs (records/templates/rules): it would be very helpful if one could select only the databases that are necessary for the daily work for display (example: I have in the record tab 14 different databases of which I only need 4, and one that I need is only accessible through the drop down menu); if a selection is not possible it would be helpful…42 votes -
Make "search" and "sort by" functionality from Browse Bibliographic Headings accessible when binocular icon is clicked.
The Browse Bibliographic Headings feature allows a user to search in the results list and to sort the list by date, title, creator, etc. When you click the binocular icon for a subject in Alma, it looks like it brings up the Browse Bibliographic Headings feature, but the search and sort features are missing. We'd like them to be added to the results screen when you click the binocular icon.
8 votes -
Improve accessibility of some pop-ups in MDE
Some pop-ups in Alma cannot be handled with the keyboard (e.g. with the tab and enter keys) but need mouse clicks.
This makes end-to-end work processes based on keyboard actions and shortcuts impossible.
For employees with repetitive strain injury (RSI) who should minimize repetitive mouse actions for medical reasons, this is a disadvantage.
It would be very useful to be able to handle the following pop-ups with the keyboard:“Expand from template”, the template cannot be selected and confirmed via keyboard (tab, arrow keys, enter).
(In the similar case of the “Enhance the record” dialogue, key actions are possible.)“Confirmation…
4 votes -
The addition of the ability to facet on item format and language in the MDE external resources search.
It would be really useful to be able to search external resources via the MDE specifically by format and language, or filter the results accordingly. For example, if a cataloguer wants to search principally for records in English and for print format items only.
2 votes -
Indications rules for holding records
We are looking to filter sets with an indication rule to look in holding records to see if a 9XX field exists.
1 vote -
Selecting multiple sets of bibliographic records to export just in one go
At the moment the process to export multiple bib record sets is quite time-consuming since sets can only be selected one at a time. That means that if there are ten sets of bib records to export, the same procedure must be repeated ten times.
I wanted to suggest that from the Run a job screen it is possible just to select/tick in one go all the sets that need to be exported. It would be an enormous time-saver. I attach a screenshot for reference. Thanks7 votes -
Delete Bibliographic Records Job should be able to be restricted to the different Related Record Types
The "Delete Bibliographic Records" job can be executed with "Do not delete if related to other records", but the parameter takes into account any Related Record Type to other bib records. We think it would be a great improvement if "Do not delete if related to other records" could be used to optionally select the exact Related Record Types that should be used for running the job. This selection would be very similar to the functionality for consortia "Restrict Deletion of Network Zone Bibliographic Records with Related Records " with Configuration > Resources > Collection Retention > Bibliographic Record Deletion…
14 votes -
Implement OAI-PMH attribute completeListSize to element resumptionToken
As a data recipient of the Alma-OAI-PMH interface, I would like to see the extent of the response for a ListRecords query (also for ListIdentifiers), i.e. how many records are to be expected.
This information can be provided in accordance with the OAI-PMH standard (https://www.openarchives.org/OAI/openarchivesprotocol.html) in the completeListSize attribute of the resumptionToken element.3 votes -
Create a set from records held in the Metadata Editor
It would be useful to be able to save all of the records that you are working on in the metadata editor as a set to come back to later.
For example, this would be helpful when working on a bound with where you need to work on several records at the same time and need to add links across the records. At the moment, if this work is not completed and we need to return to it later, we would then need to create an itemised set by searching for and adding each record individually. Instead, it would be…
34 votes
- Don't see your idea?