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 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.
78 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 -
Report list of records changed after abort job
After a user was running a discovery suppression job, and aborted they assumed nothing was changed. It would be very useful if the records that were changed before the abort were reported to the user.
Here's an example showing an abort that occurred and the user running the job assumed since they aborted the job, nothing was changed:13 votes -
Adding the publisher location to the "Keywords" index in Alma
Currently, the publisher location is not indexed in the general "Keywords" index in Alma. If someone wants to search for a certain publisher location, one must use the specific index because a "Keywords" search won't bring any results.
This is particularly unpractical when searching for series or periodicals, as they often have similar names but different publishers or publisher locations, or later editions of a certain work which can be identified by the different publisher resp. publisher location.
What confuses staff users is also that if one wants to search for a book, using the title and/or the author as…128 votes -
Add an option to search the repository by "Assign to" cataloger / operator
Currently there is no way to know which records are assigned to a certain user except for the "assigned to" note indication. We need a way to retrieve the records that were assigned in order to restore them back to the users' MDE, in case they dissappeard from the opened records pane. See full usecase in SFC#00957311.
26 votes -
Ability to create sets from "Manage Deleted Repository" search
We would like the ability to create a set from a "Manage Deleted Repository" search.
Some vendors cannot use the "delete" files currently generated by Publishing Profiles. We would like to create sets (especially logical ones) from a "Manage Deleted Repository" search so that they can be attached to a Publishing Profile and help automate delete processes for these vendors rather than using an external script with the API and analytics.
This way, someone would only have to update the deleted date range of the set periodically, or even better, more search options and filters could be created for "Manage…
14 votes -
Reading lists - notification on Alma if an attempt is made to delete an item on a Leganto reading list
We would like there to be a notification on Alma if any attempt is made to delete an item that is on a Leganto reading list, whether it is deleted individually or as part of a batch-job. The deletion could be because the physical item is in poor condition or has been lost by a user, in which case we would need to know to purchase another copy. Alternatively, we may be deleting because we have purchased a newer edition, and would need to make sure that our reading lists are updated. This would apply to both physical and e-resources.…
16 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.
68 votes -
Create a Set of Inventory from a Title Set
It would be very useful to be able to take a set of titles, and convert it into a set of inventory attached to those titles. Specifically, I would like to create a Portfolio set from a set of Electronic Titles. I have regular need to move groups of portfolios from one local e-collection to another. I have only a list of ISBNs to start with, which I use to create an itemized Electronic Titles set. However, moving portfolios requires a Portfolio set, which can only be created with Portfolio IDs. It is very cumbersome to arrive at the appropriate…
54 votes -
Authority linking issue with bibliographic field 240
We'd request that when Alma links up bib field 240 with a uniform title entered in authority record, it should take into account of bibliographic contents in field 240 PLUS field 100 ALTOGETHER, and link these combined contents with uniform titles entered in authority records.
Currently, it links up the uniform title in field 240 only with authority record. So, those generic uniform titles e.g. Works, Poetry, etc. will be ambiguous, and do not have proper linking with their authority records established with author's name.
Details, please refer to Salesforce case # 823121
32 votes -
Option to export Alma search results and sets as CSV
Right now Alma search results and sets can only be exported in XLSX-format. For performance (and other) reasons it would be good to have the option to export in CSV format.
(Publishing this as an enhancement request was suggested by Ex Libris in public Salesforce case #00825531)
27 votes -
Make approved Purchase requests searchable in Primo
By default, Purchase Requests are suppressed from search and discovery in Primo, whatever their status (In review, Approved, Rejected).
We would like the library to have the possibility to automatically unsuppress Purchase Requests and to make them searchable once they have been Approved.21 votes -
Add the NOT Boolean operator to the Advanced Search in Alma
Advanced Search in Alma contains currently only AND and OR Boolean operators - it would be very useful to have the NOT operator included, so that we can exclude particular records from Logical Sets, rather than creating 2 Logical sets and then combining them with NOT, resulting always in an Itemized set.
27 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…
65 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.
88 votes -
Use of parentheses in advanced search
Currently advanced search does not allow the use of parentheses. We'd like to suggest the capability of using parentheses in doing some complicated search logic. This can shorten the search query a lot. Currently, we have to repeat the search queries, and apply a combination of AND/OR search logic. The attachment explains the situation with a screen shot of current search logic.
24 votes -
Show orders and requests in repository search regardless of role
Every staff member should be able to see if there are orders or requests for a title regardless of their roles.
It's important e.g. for staff at info/circulations desks to see why a title without items is found - as well as for receiving operators to see if there are any patron physical item requests...Still, of course, one should only be able to edit orders or requests with the respective privilege.
17 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
62 votes -
Add a lock feature to prevent selected items from being withdrawn when running a job
I envisage this as a simple checkbox within an item's record which prevents that item from being accidentally withdrawn. (A parallel exists in many photo editing software packages.)
I also envisage this as being a property which could be engaged or disengaged on a set of items via a job.
When running a withdrawal job, any such "locked" items which were not withdrawn should be listed individually in the job report so that the user can determine whether this was correct (in case an item has been accidentally locked by a user, for example).
A use case is as follows:
…
24 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
- Don't see your idea?