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.
44 results found
-
Allow cross-use of MARC21 authority fields 500 and 510
Alma currently enforces strict validation rules that restrict the use of fields 500 and 510 based on the type of authorized heading (100 vs. 110), preventing cross-usage and triggering validation alerts.
However, in real cataloguing practice (including MARC21 examples and records from the National Library of Spain), it is both common and necessary to establish relationships between different types of authorities (personal ↔ corporate) using 5XX fields. For example, a 110 record may include 500 fields linking to persons, and a 100 record may include 510 fields linking to corporate bodies.
This restriction limits the accurate representation of relationships such…110 votes -
Default search option setting for external resources
MD editor > Tools > Search external resources
Search options for external resources such as title, creator, isbn, system number and year of publication are automatically filled in from a bib record. This make us to delete fields manually and spend time. It would be great to set search options at the institution level or individually.
103 votes -
Possibility to open a record in MDE with MMS ID in URL (Deep Link)
At the moment it is not possible to create a link from an external system or a document which opens the MDE for a given MMS ID.
We would like to speed up the workflows of our cataloguers by having a possibility to generate links to Alma for a list of MMS IDs.
e.g. https://{alma domain}/mde/?mms={mms id}
This could then used by external tools to generate a "show" or "edit" link for our cataloguers.
It would also be possible to generate such links in an Excel document with MMS IDs by using a formula to generate such links, which would…
92 votes -
New title search - include subfield t in Names section
we would like to see subfield t in the names section of the new titles search. This subfield shows when it is present in field 600 but not in 700. This would be very useful when searching for Author/title
75 votes -
"Display in Discovery" from any screen in Alma
Make the Display in Discovery action available in any screen/view of a record in Alma, not just in a repository search or in portfolio lists. There is often the need to see how a resource displays in Primo when working in an item, orders, and other areas of records.
73 votes -
Refine search and Search external resources function
When using the "Search external resources" function under profiles including several external catalogs, we can only use refine search link on the first tab.
It would be great if the refine search link was on all tabs rather than on the fisrt tab only.
72 votes -
Linking bib records based on 830 $x should be optional
Alma currently links bib records based on the presence of the ISSN in the 830 $x. This causes a terribly confusing display in Primo and Alma and is prone to messing up requests. This should be an optional "feature" and not automatically enabled. We do have the option to turn off all related records, but if we use that, we lose all our boundwith relations.
We should not have to delete a valid MARC subfield (830 $x) in order to prevent related holdings record displaying in Alma and Primo.
72 votes -
Ampersand symbol (&) in Repository search
It's found that the repository searches using the ampersand (&) symbol and the word 'and' produce different results. Our request is to make the ampersand symbol and the word ‘and’ interchangeable when Alma does repository searches.
SF case # 00646924
66 votes -
Alma User Role for Editing/Deleting only Quick-Cataloged Records
Scenario:
Library staff frequently need to create records for resources using the Quick Cataloging feature. Often, those records need to be edited after creation, due to mismatching resource types, updated information, operator input errors, etc. Most of the staff using the Quick Cataloging feature are not trained as catalogers, and do not have cataloging roles in Alma.Problem:
Quick-Cataloged records are not editable by staff without cataloging roles in Alma - who are frequently the creators/managers of these records. This has led to several different workarounds at various institutions:Some institutions have given their non-cataloging staff full cataloging permissions to…
66 votes -
Ability to use import profiles on OCLC Connexion exported records
Currently import profiles can applied to Marc files that are uploaded into Alma. One can use the import profile to specify match methods, tell Alma how to deal with matches of existing and incoming records (overlay, merge, or use NZ record), and also specify inventory info to map the Marc 949 field to holdings and item records. Although the OCLC Connexion integration profile deals with importing records it lacks the features described in the previous sentence. Please see screenshot of settings in Oclc integration profile versus in an import profile.
Basically we would like the ability to specify an import…
64 votes -
Update All Relevant Indicators When Correcting Preferred Terms Linked via Cross-References
The recent enhancement to Preferred Term Correction correctly updates bibliographic headings when the preferred and non-preferred terms are in different authority fields (for example, 410 → 130), and changes the bibliographic field tag accordingly (e.g., 610 → 630).
However, the current implementation does not fully synchronize MARC indicators between authority and bibliographic records.The enhancement documentation states:
"When a bibliographic field is updated to an X30 field, the non-filing indicators in the bibliographic record will be adjusted based on the linked authority record. According to MARC21 standards, the 1st indicator of authority field 130 (Nonfiling characters) will be copied to…63 votes -
MDE: same behaviour for all languages/scripts which are written from "Right-to-Left"
Hi,
There are several scripts that are written from "Right-to-Left":
Arabic, Aramaic, Azeri, Divehi, Fula, Hebrew, Kurdish, N'ko, Persian, Rohingya, Syriac, Urdu.When typing a Hebrew letter in the Alma MDE the direction switches automatically from "Left-to-Right" to "Right-to-Left". Same for Arabic, Azeri, Modern Aramaic, Kurdish, Persian, Urdu (see attached file: Alma-MDE-Scripts-written-from-right-to-left.pdf).
Please provide us the same behaviour for all the languages/scripts concerned.
In our library, we are especially interested that when typing a Syrian letter the direction also switches to "Right-to-Left" automatically.
Thank you in advance!
63 votes -
Manage Deleted Repository--ability to select and restore a group of records
Manage Deleted Repository is a helpful feature helps us restore records that were mistakenly deleted. However, it only allows us to restore records one at a time by clicking a "Restore" button next to each record. This is not workable when a large number of records need to be restored. We need functionality that will allow us to select and restore groups of records.
The Restoring Records Removed or Changed by Jobs functionality (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/050Administration/070Managing_Jobs/020Manual_Jobs_on_Defined_Sets#Restoring_Records_Removed_or_Changed_by_Jobs) does not sufficiently address this need, as it can only restore repository content deleted by a job, not records deleted manually. Also, even in…
62 votes -
Additional "Suppress from FRBR/dedup" option and display
When viewing a bib record, the pop-out information to the side of the screen lists whether or not the bib is suppressed from discovery and suppressed from search. It would be helpful if this info also contained whether the bib was suppressed from FRBR/dedup.
Additionally, when you edit a bib record, you can select "Suppress from Discovery" and "Suppress from External Search" under the Record Actions dropdown menu. It would be helpful if there was also a "Suppress from FRBR/dedup" here.
60 votes -
Add Melingo to ALMA
Hello,
The assimilation of Melingo in Primo for the customers in Israel proved to be a useful solution.
It would be nice if it can also be implemented in ALMA.
If Melingo will indeed be in ALMA, the catalogers will no longer need to add Ktiv Maleh or Ktiv Haser in Hebrew in variant titles.Thanks.
59 votes -
Create new reports for Authority management
National libraries and institutions managing controlled vocabularies require robust tools to ensure the integrity of their authority files. Current Alma functionality (Authority Control Task List) focuses primarily on the link between bibliographic and authority records. We propose a new set of dedicated Authority Management Reports to identify internal inconsistencies, errors, and redundancies within the authority files themselves.
Proposed Reports & Functionality
· Orphan Authority Records: Identifies authority records without any associated bibliographic records. Crucial for cleaning up legacy data or unused headings.
· MARC Encoding Errors: Detects structural errors within authority records (e.g., missing mandatory fields like 008, invalid indicators,…
53 votes -
Make Push Selected to MDE button available for Itemized Sets
'Push Selected to MDE' (pushing records in bulk to Metadata Editor) is not available for Itemized sets, but it is available for Logical sets in the current Alma implementation. While the option to Push Selected to MDE is plainly visible in the Logical Set Results view (please see the attached screenshots), it is replaced by the 'Remove Selected' button in the Itemized Sets Members’ view. We would be very interested in having the Push Selected to MDE available for both Logical and Itemized sets. Is it possible to add the 'Push Selected to MDE' to he Itemized view and keep…
49 votes -
Authority control for name-title access points: link bibliographic 1XX+240 to authority 1XX $t
In Alma, bibliographic records containing 1XX + 240 do not establish an effective authority link with the corresponding name-title authority record (1XX $t).
As a result, when the authorized access point for a name-title authority is updated (for example, a change in the title portion in 1XX $t), the update is not propagated to the linked bibliographic records. The 240 fields in affected bibliographic records remain unchanged and must be identified and edited manually.
This behavior results in:
· High manual maintenance effort
· Increased risk of inconsistencies between authority and bibliographic data
· Reduced effectiveness of authority control in…
48 votes -
Community Zone Authorities vs Network Zone Authorities
When authority records are managed from a Network Zone (NZ) in a cooperative way—that is, when several institutions create and maintain authority records of different types (names, subjects, etc.)—it is confusing for catalogers when authorities from the Community Zone appear.
For this reason, we would like the possibility to choose from which zone we view authority records, mainly in these two screens:
• In Browse Authority Headings in the NZ, we would like to have different tabs to choose which zone we want to consult, the NZ or the CZ
• In Browse Authority Headings in any IZ of the…31 votes -
Please allow customer-specific definition of local subfields regarding sorting and non-repeatability
The configuration of resources in Alma offers the option to define local subfields as "non-repeatable". However, this has no effect. No error message appears when saving if a local subfield is accidentally populated multiple times.
The normalization process "Marc21 Bib normalize on save" offers the option to sort subfields (tab "Task Parameters"). However, this has no effect on manually edited and saved data in MDE. Sorting can be triggered by the process from time to time for a dataset, but it does not run continuously. We had hoped to achieve sorting directly in MDE, which would allow operators to better…
30 votes
- Don't see your idea?