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
-
Ability to search for duplicate varying text in two different Marc fields
It looks to be possible to find duplicate fixed text values within subfields of the same MARC field (and possibly between two MARC fields), but there doesn't seem to be a way to build a rule that would identify two matching fields for varying text by record, for example, finding a record that had the OCLC number duplicated in another field (but which the number would obviously vary title by title). The asterisk only seems to work if you have some kind of fixed piece shared among records and not if the whole field varies.
5 votes -
Please allow Enum C and Enum D selection in Physical Items Enrichment of Publishing Profile
As we construct a crucial Publishing Profile, we need to fetch our Enum C and Enum D. However, in the Physical Items Enrichment option of the publishing profile, these fields are not available. Our go-live is scheduled later this year and lack of Enum C and Enum D causes a great deal of concern.
5 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 -
Subject Index search: the comparison is not to contain a certain string but the entire field
PrimoVE enriches the search with terms from the 150 or 450 fields of the authority record when searching by subject index. Still, we would need the match not to contain a certain character string but to match the entire 150 or 450 fields with the subjct being searched for with an exact search in PrimoVE.
This would prevent subjects sharing part of the string (but not all) from appearing in an exact subject search in PrimoVE.For example, if we search for records on "Right to life" in Subjects index, Primo VE also retrieves records on "Right to private life"…
4 votes -
Follow NACO rules when linking bib headings (reduce number of "ambiguous" headings in ACTL reports)
When linking bib headings, Alma does not follow NACO comparison rules when checking for ambiguous headings. This results in numerous headings not linking at all, and being reported as ambiguous. This reduces the utility of Alma's authority control process, because there are too many headings to link manually.
Examples of headings that Alma won't link because they are "ambiguous"
- Peabody Essex Museum
Peabody & Essex Museum
Ciné+ (France)
Cine France
Mohammad, Ali
Mohammad Ali (a cross-reference in the authority record for Ali, Mohammad)
McFarland & Company
McFarland Company (cross-reference in authority record for J. Horace McFarland Company)
Authority File Comparison…
4 votes -
Create a Collection for Audio Cine Films
Please create a package collection with portfolios for Audio Cine Films. Marc records are publicly available and can be found here: https://www.acf-film.com/en/infostream.php
4 votes -
Show import profile for record versions in MDE
If I could see which import profile brought in which version of a bibliographic record within the MDE, I'd find it a lot easier to spot issues with import profiles (e.g. timing, merging, normalization rules). I think the best place for this info would be after the timestamp, e.g. "Version: 2 Created By: System (13/09/2023 15:11:01 BST) IMPORT PROFILE NAME"
4 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 -
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 -
Index 532 field
MARC21 field 532 should be indexed in Alma and Primo. This is important for accessibility notes.
4 votes -
Urgently needed hotkey of remove subfield
I really need a hotkey to remove subfields. Oh, please save my backspace button.
3 votes -
Ability to search for duplicate varying text in two different Marc subfields within the same MARC field
Using the Indication rule "recordHasDuplicateSubfields", it is possible to find duplicate subfields that have the same value within the same field, but it is not possible to find duplicate subfields if the subfield content is different.
For example, we can't find a 245 field that contains two different 245 b subfields.
Having this possibility would greatly help us to identify cataloguing errors.3 votes -
246 - 2nd. indicator - Alma should include the information of the indicator.
Alma Metada editor should write the information considering the chosen second indicator before the type of title included in subfield "a"
0 - Portion of title
1 - Parallel title
2 - Distinctive title
3 - Other title
4 - Cover title
5 - Added title page title
6 - Caption title
7 - Running title
8 - Spine title3 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 -
Differentiate Success & Warning colors in MDE
It would be nice to be able to configure the colors within the Metadata Editor, specially when it comes to the success, warning and error messages. The warning messages seem to have the same color as the success messages that makes less obvious if they are very valid warning messages to look at.
2 votes -
Metadata Editor: add filter sort by type XSL
It would be helpful when searching for shared norm rules to be able to sort by type XSL. Right now when looking for a rule to copy and customize we have to pick thru a list of several hundred, because the majority are drool.
2 votes -
Enhance Validation for Fixed-Length Control Fields to Control the Field Length
Alma provides a MARC21 validation task called 'Validation Fixed Fields Positions MARC21,' but it does not include a check for the length. It would be useful to include a length check and to make it configurable whether a warning/error is generated (thus also adding a new exception to the validation exception profile). This should be available for all kinds of records that have fixed-length control fields and should take into account that e.g. in 008, the correct length differs for different types of material.
2 votes -
Searchbox jankiness
The searchbox in Alma is...odd.
When you click into it with one click, it highlights everything (instead of inserting the cursor where you clicked). Why not use the almost universal standard of 1 click = insert cursor at that point, 2 clicks = highlight that word / string, 3 clicks = highlight everything?
It's also needlessly difficult to make the dropdown disappear after having opened it when editing a record. The dropdown should disappear if you click anywhere else on the screen - as it does when not editing.
2 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 -
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
- Don't see your idea?