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.
132 results found
-
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…
82 votes -
Add warning for active title-level-requests when relinking or deleting holding records or items
When relinking holdings and items to new bib records or deleting holdings or items, requests can get lost. This is the case if they are on the titel level instead of on the item level.
(Cf. https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/Physical_Resource_Management/015_Managing_Physical_Resources#Relinking_Items_to_Another_Bibliographic_Record)Staff with the role Cataloger Extended or similar roles which allow for relinking and deleting of records, holdings, and items, would benefit from a warning that an active request is present on the title level (e.g. a pop-up) before a holding record or item is relinked or deleted.
80 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.
73 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.
68 votes -
Analyse and normalise special characters and diacritics in Alma records
In order to enable correct and consistent automatic linking between Bib. headings and authority records, Alma's treatment of diacritics needs to be normalised, and made configurable according to the Authority file being used. In addition there are special characters in use (such as quotation marks), that have more than a single graphic representation that should be normalised in order to prevent discrepancies in Almas' match and link mechanisms.
SFC#00533813, SFC#00375370 relate to the issue.66 votesDear all, we would like to update that in addition to what was done in the May 2020 Release, we are looking at ways to allow libraries to select if diacritics should be taken into account in the linking process. We are exploring adding diacritics matching as a condition in the authority control rules to support flexibility, setting this for specific authority vocabularies only.
-
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…
65 votes -
Please add the ability to use the facets for Archival Materials according to LDR pos. 8 = a
Hello,
Most archival materials are cataloged as follows:
LDR pos. 6 = p
LDR pos. 8 = a
Currently, the facet in Alma show these kind of materials as "Undefined".
Adding a facet of "Achieve Material" according to LDR pos.8 = a, would be very useful.Thanks.
63 votesHi. 1. Are you stating that you want a new “Resource Type”?
2. The definitions of the resource types are explained in the table titled “Rules Used to Create the Resource Type Field – MARC 21/KORMARC and UNIMARC” at https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/010Getting_Started/050Alma_User_Interface_%E2%80%93_General_Information/Searching_in_Alma#The_Resource_Type_Field
3. Do you want a new row in this table which would be as follows?
Archival materials. LDR pos. 8 = a
4. The table is read top to bottom and as soon as match is found it stops. Where in the table would you like this new row to appear?
5. How come the title of this suggestion states “LDR pos. 8 = a” but the comment from Feb. 2 also has “LDR pos. 6 = p”? We do not think “LDR pos. 6 = p” is a good idea. That is used for “mixed materials”. On the other hand “LDR pos. 8… -
Allow to define several local search indexes, including standard MARC fields
Following the partial implementation of idea "Ability to search via free text MARC tag and subfields" (https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/17197337-ability-to-search-via-free-text-marc-tag-and-subfi) under NERS 2020 #6795, here is perhaps a more modest suggestion, that hopefully can be more technically feasible and still provide a large chunk of the missing functionality.
Similar to the analytics "Local Param" concept, it would be very helpful if institutions were able to define 5-10 "Local Search Indexes", based on each institution's needs. These indexes should be able to include any MARC field or subfield, whether local or standard (and preferably also field combinations).
Use case: In our institution,…
60 votes -
Normalization rules - adding dates
It would be great if the normalization rules could be enhanced to use variables such as date, or add datestamps.
We would like the ability to insert dates into MARC notes fields via normalization rules.
Ideally inserting variables something like %DAY%/%MONTH%/%YEAR% in a rule would add today's date in the format DD/MM/YYYY once a rule is run.
60 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.
60 votes -
Make it possible to add single titles from other sources than the IZ to Collection Discovery
At the moment you may only add titles from your IZ to a collection in collection discovery. It would be nice to have a method also to add titles from the NZ, the CDI and external resources.
59 votes -
New UI-Call Number as an option in the search customization
In the old UI when conducting a search the call number would display in the search results. In the new UI each individual title now has to have the physical title clicked on to see the call number. It would be helpful to have a call number option under the customization options so that it would eliminate all of the unnecessary clicking when trying to view call numbers during a search.
59 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.
58 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…
58 votes -
Need ability to search 79X fields
We plan to implement use of the 790 field for local tracings (such as former owners) to be used for special collections materials, and have set up a separate search field in Primo. Now we see that we can't search that field at all in Alma, only Primo. Since Alma does index 59X fields as "local notes" and 69X fields as "local subjects" we propose that the 79X be indexed as well.
58 votes -
Change color of NZ icon to distinguish from the CZ icon
The new Alma UI has made the NZ icon and CZ icon the same color and very difficult to distinguish from each other. The previous interface had different colors for these icons, which made it very easy to distinguish them. Please change the color of the NZ icon so that at a glance we can easily distinguish it from CZ records.
57 votes -
Improve editing of large fields in the Metadata Editor
When creating and/or editing a MARC field with a large volume of text, such as the 505 or 520 field, occasionally the cursor will appear to be in a different position than it is, so that the user may accidentally delete the wrong characters, or insert them in the wrong place. This appears to happen at random, and saving the record, restarting Alma, and even clearing the browser cache does not consistently fix the problem, even in the short term.
57 votes -
bulk remove titles from collections (not the electronic type)
Add the ability to remove titles in a set from a collection (not the electronic type) in bulk, as well as add titles in bulk from a set.
56 votes -
Add all Enumeration and Chronology fields to the Inventory Information tab of an Import Profile
Currently, only Enumeration A - C and Chronology I - K are listed in the Inventory Information tab of our Import Profiles. Our consortia uses Enumeration A-D; Enumeration D specifically is used for free-text phrases that do not conveniently fit into the category of volume, number or issue; so "index", "part", "box", etc. are all written in EnumD. This is why it is frustrating that this enumeration field cannot be imported via an import profile.
It would be immensely helpful for us if all enumeration fields were listed in the import profile. There is no point in having so many…
55 votes -
Make Suppressing a location function the same as suppressing a holding in all publishing jobs
Currently, the general publishing job exports inventory in locations which are ticked "Suppress from Discovery" in Physical Locations config, when "Excluded Suppressed Locations: is ticked in the Publishing Profile.
Alma should handle this flag as it does for Publishing to Primo and Publishing to Libraries Australia and ignore suppressed locations, otherwise what's the point of setting this at the location level and then providing an option to Exclude suppressed records. It is extra work to set this value for each individual bib/holdings record.
55 votes
- Don't see your idea?