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.
40 results found
-
Add extra filter operators to date fields in title search
Add the following filter operators to all titles search:
-Is within last (days)
-Is older than (days)
-Is within next (days)to filters in all titles search such as MMS creation date (title) and modification date (title).
These filters are already available in user search.
3 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 -
Display all 035$a values for the Record Number column in Table view of Titles UI
In the new titles search UI, the Record Number field lists only the first listed 035$a value of the record, followed by "and others." This is true for both the record view, where keeping data compact makes sense, and on the table view where one might expect to see more values for repeating data fields.
If the table view showed all of the 035$a values in the record number column, this would increase the utility of this view, as it would allow staff to recognize OCLC and other system numbers among the list without requiring a click and scroll through…
12 votes -
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 -
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
76 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 -
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 -
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 -
Option to change default management tag publishing for bibs
When creating or importing new bib records from an external source (especially OCLC), the bib's default management tag in the MDE is set to "Publish Bib" for publishing under "Export to WorldCat". However, "Publishing Holdings Only" is useful for the purposes of publishing our library's Local Holdings Records (LHRs), and other libraries may not want to publish bibs or holdings by default at all. The option to choose between one of these three publishing defaults would benefit libraries who would otherwise need to either regularly update batches of records or manually edit each one as they're created.
129 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…
89 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…
51 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.
74 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 -
Display the date a work order is created
When a work order is created to put an item in process internally ("Technical Services (CAMS)" or "Show to supervisor" or "Preservation") it would be helpful to have Alma display the date this status change happened.
It could be in the "item history", and/or the "In process" display, and /or in the "list of items." Currently, the receipt date is the last date displayed in these locations, which does not help with locating an in-process item.
92 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 -
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 -
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 -
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 -
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.
70 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
- Don't see your idea?