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.
51 results found
-
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?
-
Sorting Authority Task List
It would be highly helpful to have a sorting filter in the Authority Task List that would allow us to sort the list by Fields (e.g. 100's,600's, 700's, 830's,): Personal Names, Corporations/Conferences, Subject, Title, Uniform Titles, and Series. This way work loads can be created and assigned for these specific areas. As things are now, all items are mixed together and it takes far too much time to find/create a single list.
195 votesHello all,
We are currently reviewing it to assess its technical feasibility and implications. We’ll follow up once we have more clarity.
-
Authority data: first indicator in the bibliographic record
Now we have many mistakes in our bibliographic records in the settings of the first indicator by connecting with authority data (GND, IdRef, ..). It would be great to have an automatic process, which takes over the first indicator of the authority data to the bibliographic record when you select the authority heading.
What you have then is the following: First indicator, preferred term and authority identifier are taken over from the authority record to the bibliographic record by using “select” in the index view of the authority record.
It would be great, if this is implemented for 1XX/6XX/7XX in…148 votesI wonder if this request takes into account that certain fields in the 1XX/6XX/7XX have different first indicator definitions in the MARC21 standard for Bibliographic fields compared to their corresponding Authority fields. In such cases, copying the first indicator from the Authority to the Bibliographic heading would result in incorrect data. Is the reqeust is about Names only? Hans, I would recommend consulting with AAFG group for a detailed spec where this requested behavior is valid to which fields.
-
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,…
142 votes -
Bibliographic records editing history
Here is an enhancement request concerning bibliographic records editing history.
Currently, the "View Versions" can only tell the different version of a bib. record. However, this cannot tell logging history of updating/editing the bib. records, e.g. who add/remove a MARC fields/who suppressed/released the bib. record etc. This is no history tab to keep tracking the changes of a bib. record which is unlike other history tab functionality available in other Alma pages, e.g.
• The PO Line Summary page when editing a PO line
• The Physical Item Editor page when editing item records
• The License Terms Details page…128 votes -
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.126 votes -
Automatic dismissal of corrected authorities from the Authority Control Task List.
Automatic dismissal of corrected authorities from the Authority Control Task List.
Improve the Authority Control Task List linking functionality so that when an authority is upgraded/corrected in the metadata editor, it is automatically dismissed from the Task List. Items are added to the Task List before an institution has had a chance to upgrade the catalogue record. Many of these authorities will routinely be upgraded at the cataloguing stage. The need to then manually remove substandard authorities from the Task List which no longer exist in the bibliographic records adds a huge burden of extra work, especially for large institutions.…124 votes -
Abilty to edit the authorities from CZ
In bibliographic records and in Browse Bibliographic Records you can check the information of the linked authority - also CZ authorities. The possibility to take the authority directly in edit mode, as you have the right to edit authorities of the CZ
118 votes -
Browsing Dewey in MD Editor
We noticed that in Metadata editor the browsing in the 676 - Dewey field isn't available: we would like add the feature to scroll the lists from other records, as happens for the 6xx fields (subjects) and 7xx (authors).
114 votesHello everyone,
Regarding the request for this idea, could you please provide more details on the use case? According to the MARC21 standard, the Dewey Decimal Classification Number is located in field 082, which is why we allow browsing of data from 082 $a and $b. Additionally, we have incorporated the Locally Assigned Dewey Call Number from field 092 $a and $b into this browsing option (full details can be found on the Alma online help page).
However, fields 676 and 410 according to the MARC21 standard are not Dewey fields.
-
Prevent deletion in Community Zone based on field or value in specific field.
Blocking deletion in Community Zone based on field or value in specific field. Possibility to be definded as a parameter for each CZ vocabulary.
107 votesAs you all know, the Community Zone content is shared among all Alma customers, each with different requirements. Therefore, I’m not sure this request would be acceptable to the wider Alma community. That said, if there were a consensus on a closed list of fields that CZ bibliographic records should be restricted from deleting per MARC profile, this capability already exists and is managed by the Ex Libris Content Operations team. Unfortunately, this is not available for authorities. Do you think such a consensus could be reached?
-
search filters and better results display in the "search external resources" function
When we are searching WorldCat for a record to match a newly-ordered title, we often find duplicate records. The current search results display makes it difficult and time-consuming to choose the best record.
The external resources search would be much improved if we could limit search results by the language of cataloging (040 |b) and format. This would save us having to wade through multiple vendor records that aren't even in our local language of cataloging, and multiple records for resources in a format other than the one we are looking for.
It would save us a lot of time…
97 votes -
Adding 'own' Covers to Alma records!
Dear,
This question might be related to:
We would like to have the ability to add covers in Alma (and display those in Primo) for all kinds of records.
Br,
97 votes -
Ability to select records to release from MD editor
Cataloger can release 1 record per time or all records can be released, but it would be useful catalogers could select multiples records to release.
88 votes -
Reminders : extend the Add reminder functionality to other roles (only Cataloger now)
Reminders functionality could be more effective if extended to other roles than only cataloger role. At least Electronic and Physical inventory operators should be able to add a reminder on a Bib record in a repository search result.
The managing of reminders from Cataloging menu can be limited to catalogers.82 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…80 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…
76 votes -
Alma MDE: Filter by Marc21 field and subfield
As a cataloger I would like to have the possibility in MDE to filter the Marc21 data by field and subfield
value to have a better overview over the current part of the data which is to be checked/edited.
Further I would like to have the possibility to quick access filters which i use often.Proposal:
Add a possibility to filter by field and subfield, e.g. by having an input form for the Marc21
field (rows filtered by "Begins with {value}") and for the Marc21 subfield (rows filtered by
"Contains {value}"). The filtering should by done by "AND" condition. (See…76 votes -
Preferred term correction - correct coding when flipping LCSH to LCGFT
When a 655 field is coded for LCSH and matches a non-preferred term in LCGFT, Alma flips the heading to the preferred LCGFT term but does not update the coding (it should change the 2nd ind to 7 and add $2 lcgft).
The problem is limited to cases where:
A bib heading 655/_0 matches a non-preferred term in an LCGFT authority
What happens is:
The PTC job flips the heading to the LCGFT preferred form, but it does not change the 2nd-indicator from 0 to 7, and does not add $2lcgft
What is not a problem:
655/0 headings that…
73 votes -
MDE Search Resources mask should be empty
When opening the Search Resources mask in MDE, the previous search is still in the data mask. For us there is no benefit for this behavior and we would like to have an empty mask and not to clear the mask every time before starting a new search.
(If other libraries need this opportunity, we would suggest to make the default settings for this mask customizable)72 votes -
Metadata Editor should add the year automatically to the 866 field
Currently the Metadata editor does not add automatically the year to the 866 field. If we want the year to be in our 866 we have to add it manually. Actually this is the only way our patrons can see the year in Primo.
69 votes
- Don't see your idea?