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.
128 results found
-
Add a job for adding Repository search labels
please create a job to add Repository search labels for titles and holdings based on a set. This would be a convenient solution for managing large numbers of records in the new UI and the addition to bulk labeling.
1 vote -
Collection - report who added title and when
When adding titles to Collections (Resources\Manage Collections) it would be helpful if it reported who and when a title was added to the collection. Report of this via Analytics would be preferable but displaying in Alma would be a start.
3 votes -
convert bib. records to sub collections in bulk
We discovered in Alma the possibility of creating collections of archival materials, which gives us the opportunity to create a hierarchy of collections and subcollections. Visually it also looks good. We do not yet have DIGITAL ALMA, we cannot load materials themselves, but a reader receives comprehensive and detailed information about library collections.
At the same time, we encountered a problem: we have collections with dozens of subcollections, and each subcollection needs to be edited separately. It takes precious time and a feeling of wasting energy on creating records of subcollections, when we have their bibliographic records ready with all…1 vote -
Add ability to abort jobs when they are for information only, such as when exporting data or running overlap analysis
Currently it is more common than not for jobs in Alma to be missing an option to Abort them under Monitor Jobs > Running.
This is a highly frustrating situation where the only option is to open a Support case to request for the job to be aborted, and wait days for response.
In the meantime, staff work is completely halted for this while we wait for Support.It is understandable that the Abort option is not present in cases where there could be negative impact on records, such as initiating an job update to change the records.
But it…1 vote -
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
72 votes -
Support Processing System Control Number (035) Updates in Imported Authority Record Updates
Currently, Alma's authority-control jobs do not process updates to MARC21 authority tag 035 (System Control Number) when the update occurs via an authority import profile as the update of an existing record, i.e. there is a match between the existing authority record in Alma and the incoming authority record via the authority import profile. In contrast, the update is processed when there is no match with an existing record, i.e. the record is new to Alma, or, when the authority record has been updated manually via the MDE.
This was clarified by Ex Libris in a support ticket (case 07255325).…
11 votes -
Searchability for MARC 361
We would like to be able to search MARC-361 in Alma, if possible also specifically in subfields of the 361.
https://www.loc.gov/marc/bibliographic/bd361.html
https://www.loc.gov/marc/holdings/hd361.html104 votes -
Add filters and columns to import profiles screens for zone, protocol, scheduling, status
The Import Profiles screen has few options for narrowing the list of profiles if one isn't certain of the profile name, or if descriptions are too similar. Please add filters and columns to the display screen--preferably sortable columns--for fields that distinguish the zone, scheduling, and status for import profiles.
Priority 1, Zone: Users should be able to clearly see whether an import profile is using the network zone or the institution zone for an import profile, as this affects the workflow and processing of records being imported.
Priority 2, Status: While the Active/Inactive status of a profile may be useful…
4 votes -
Add MMS to title list search options in Collection Resource Editor
When searching the list of titles assigned to a collection, users can only search by title or publisher. It would be helpful if there was also the option to search by MMS ID since this allows for more precise retrieval. See screenshot: https://app.screencast.com/sCZbTHJ39CcHE
3 votes -
Sorting results of non-English external searches performed through SRU.
When performing external searches via SRU in languages other than English, the results are first sorted in English before being sorted in the respective language. We request that the results be sorted in the search language first.
1 vote -
Add a new vocabulary in the CZ
We have in NZ of CCUC (Catalan Union Catalog) a vocabulary in Catalan that is a controlled language used for indexing the genre or form and it can be used in bibliographic records together with any other subject heading system. Its use is of interest to any library that uses Catalan as the language of the catalog (for example, libraries in Andorra, the Valencian Community, the Balearic Islands, etc.). Some of these libraries use ALMA and have requested that this vocabulary be accessible in the CZ in order to use it.
Therefore, we request the indexing of the TGFC vocabulary…48 votes -
Adding Facets to Alma's internal All Titles, Physical Titles, and Physical Items searches
Currently, a search within Alma allows for a limited number of facets to filter a user's search when searching "All Titles", "Physical Titles", and "Physical Items". These only include the following facets: "Material Type", "Resource Type", "Language", and "Publication Year."
In contrast, Primo VE's public search has many more configurable options that include "Location", "Creation Date", "Collection", "Availability/Peer Review", etc. It seems odd that Alma would be unable to also use some of these options since they're configured within Alma. At the very least, having "Location" added as a facet would be helpful for seeing where items are in a…
22 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.
46 votes -
Display Number of Records in Set Information Section
It would be extremely beneficial to have the ability to view the number of records in a set directly within the Set Information Section, without the need to click through to the content.
Specifically, adding a line such as “Number of Records: ####” in the Set Information Section would streamline the process of sorting through sets. For example, when managing multiple sets of items for withdrawal, it would allow me (or my students) to quickly ascertain the number of remaining items without the need to navigate into each set, view the content, and then return to the previous screen.
This…
12 votes -
Improve the efficiency and accuracy of Check call no.
In the Aleph environment, when a cataloger presses F3 in the MARC tag of call number (050), they can see "all" similar call numbers. This helps them to decide the call number for the record they are working on. The system does not differentiate whether these are physical or electronic resources, or whether they have holdings. However, in the Alma environment, when in the same call number (050) MARC tag, it is not possible to see "all" call numbers of records in the system, especially not for electronic resources. This significantly increases the difficulty for catalogers in deciding the call…
4 votes -
Improve "Select all" search results selection
When running a search within Alma, we have the option to "Select All", at which point we can accomplish various tasks like "Push selected to MDE" (for a Physical Titles search), "Add to Itemized Set" and "Create Itemized Set" (for a Physical Items search), etc.
However, when clicking "Select All", this only selects the results on that page of results, which is capped at 50. If you create a search with many pages of results, you would have to take action on each page individually. Clicking "Select All" should actually select all results, not just the results on that page--or…
40 votes -
Add permission to remove items from sets to more Alma roles
Several of our cataloging workflows are based on multiple catalogers working off of a public Alma set of items to be cataloged. After they catalog an item, they remove it from the set. The ability to remove records from sets created by others requires the Repository Manager role. Currently we have to add the Repository Manager role to catalogers to get the "remove from others' sets" functionality, and we don't want to grant the other advanced permissions along with that role.
Please add the ability to remove items from sets created by others to additional Alma roles that are lower…3 votes -
Display of the 1,000 most recent linked data records in Alma and Primo
It is not possible to display all linked data records since the number is limited to 1’000. For better user convenience, at least the 1’000 most recent records should be displayed and not the 1’000 oldest or randomly selected records.
Especially in the case of journals and monographic series that have been published for a long time, 1,000 linked records are not uncommon and the most recent ones are usually of interest.12 votes -
No relation "Replaces/Replaced by" between records due to entry of invalid ISBN (020 $z)
If there are two records in Alma, one that has 020 $a u and another that has 020 $a v and 020 $z u, the both records will be related by the system with the relation: Replaces/Replaced by. The 020 $z is understood as a "cancelled" ISBN and therefore included in the job that calculates the relations.
In the vast majority of cases we know 020 $z is a false/invalid ISBN: a publisher mistakenly(!) uses the same ISBN in two different resources that have nothing to do with each other. However, according to the international rules for describing resources, the…
7 votes -
OAI publishing profile
At the moment Alma can have only one OAI publishing profile. However this doesn't always meet customers needs.
We already have one OAI profile which we use with RapidILL to control books and is restricted to our main library via the set rules. However we have now been asked to set up another OAI profile to link to a service which would use books in two of our other libraries. At the moment this is impossible.
Could this functionality be added? I imagine it would be of benefit to other Alma users.0 votes
- Don't see your idea?