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.
1812 results found
-
Ability to change the default for reading room to NOT FINAL - Second Attempt
In August 2018 Release we got a solution for the original idea, which made things worse for us. Previously the default for the reading room was set to "Final" check in. The original idea suggested to change this to "Not Final" to help avoid a scenario where for example resource sharing items are returned accidenty to their home campus when users are not finished with them.
As of August 2018 Alma remembers the last selected choice and keeps it for the next action ("sticky approach"). Since eventually every book loaned in the reading room has to be returned "final", now…47 votes -
Improve po_line_remove_interested_users_job
The polineremoveinterestedusers job allows institutions to delete Interested Users from PO lines that have closed. However, there are many times when a PO line is closed before the item has left the department; consequently, running the polineremoveinterestedusers job means that interested users may be deleted before the item becomes available. Additionally, while the job removes the Interested Users from Alma, it does not remove the information from Analytics.
We request that:
A. Institutions have the ability to set a delay on the job based on the date the PO line was closed.…47 votes -
Retain Course Reserves info in Alma Analytics
It would be helpful if the system would retain information about course reserves in Analytics, even after things are deleted in Alma. It would be useful to be able to look back over various terms and see what courses were run and when.
47 votes -
Option to define another set of records to be included in the Database search
The database search in Primo includes only electronic collections with collection type “database” or electronic collections with a collection level URL and an unsuppressed bibliographic record.
Even though you can change the electronic material type of a portfolio to “database” these titles can’t be searched through the database search. This means we have to add local database collections even though the title can be activated through the community zone.
An example is the electronic collection “De Gruyter Databases”. I should like to be able to include these in the database search.47 votes -
linked-data-powered sets and collections
TL;DR: populate existing ALMA sets / collections infrastructure using retrieval of a list of LCCNs from an external URL to allow linked-data-powered sets and collections.
Problem
We've all seen the book displays that most physical libraries have in their high-traffic areas. These might be works by the in-house press, topical events, anniversaries of author's birth, etc, etc.
In the digital space, there are shallow-functionality RSS feeds and then a yawning gap out to things that are typically called 'digital exhibitions' which are resource-intensive glossy displays.
ALMA Collections can be used for digital exhibitions, but populating them is labour-intensive and slow.
…
47 votes -
Allow a NR to run with the PTC job
TL;DR:
We would like to have the ability to run a normalization rule whenever the PTC modifies a record.Background:
In November 2024 Ex-Libris added a new functionality to the PTC job:
MARC 21 Preferred Term Correction Can Flip Headings with Cross-Reference in Different Field
https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2024/Alma_2024_Release_Notes?mon=202411Problem:
The PTC job only changes the first indicator correctly when the PTC job changes a field into 630.
in all other cases, the existing indicators remain.
We opened a case and spoke directly with Ex-Libris, but were told that the PTC job runs as intended, and that not handling the indicators is not…47 votes -
Increase the number of available facets for all POL searching
All aspects of the POL should be available as facets, assuming they appear sufficiently frequently in a set of results. Most notably, all 5 reporting code fields should be available as facets.
Additionally, other sources of POL lists, such as the Alma Vendor Record should offer all of the same faceting functionality, including the ability to customize which facets are visible.47 votes -
Enhance Physical Locations List export for "Suppress from Discovery" and other tags
At the moment there is no easy way to create a list of all physical locations set to "Suppress from Discovery".
It's not in the export, it's not in Analytics and it's not in the data you can get via API.
I would expect this information to be included in the export you can download in Alma. Same thing goes for "Accession Placement", "Call Number Type" and all other fields that are available in "Edit Physical Location".
At the moment the export is rather short as it contains only Code, Name, Location Type and Fulfillment Unit.
46 votes -
Ability to create additional note fields in the physical item editor
At the physical item Editor, we currently have access to one public note, one Fulfillment note, 3 internal notes and 3 statistics notes. We would need 3 additional public note fields visible to the user in Primo and 3 additional internal note fields.
46 votes -
Folders in "Manage sets"
We would like the option to make folders in "manage sets". This would make it easier for different depatmants to navigate through the public sets of the institution.
46 votes -
Display all assigned PO lines in task list
With the introduction of the new PO line layout, it became possible to manually assign PO lines, regardless of their status. However, the Alma task list (tasks requiring your attention) still only displays assigned PO lines, when they are in review. Assigned PO lines with different statuses tend to be overlooked.
It would be very useful for ACQ staff to be able to see all PO lines assigned to them in the task list. This could also encourage more use of the "Assign To" function.
46 votes -
Fulfilment find patron
Fulfilment - enter patron name & select from list - should not have to additionally click 'Go'/enter to display record
45 votes -
Exclude expired users from bursar integration job
Our bursar is not currently able to collect charges from users who are no longer at the university. So we want to be able to able to exclude these patrons from the reports that are sent to the bursar with bursar integration. The fact that this doesn’t exist now has prevented us from implementing integration.
We would like this functionality to be an additional filter in the bursar integration settings that would exclude users whose expiration date is in the past. If it could specify an actual or relative date, this would be an additional improvement.45 votes -
Making Copy to Community / Network / Institution configurable
When searching for authoritiy records, there are options to copy an authority to Network or to Community or even to the Institution zone.
We understand there may be institutions and consortia administrating different kind of vocabularies at different levels, but this is not the case for all. We see in our consortium too many mistakes due to catalogers selecting the wrong button when importing a record. We therefore strongly suggest making all these options configurable, so that it will be possible to hide the buttons.
45 votesHello,
I would like to share our current approach and confirm that it aligns with your expectations for this idea.
In the new UX, these actions will be available as row level actions and will be configurable. Users will be able to hide them if they prefer not to see them, and administrators will be able to define them as hidden by default so that only users who choose to enable them will see them.
Does this approach address your request? Please let us know if this meets your needs. If confirmed, this capability will be included as part of the new Search UX.
-
Allow more than 50 POLs on a PO via manual packaging
Right now, in the Purchase Order - Package screen, you can only package 50 POLs onto one PO. The "PO lines to package" screen will only display 50 POLs max, and if you select all, then go to the next screen, it removes everything from the first screen that you selected. This means only 50 POLs max can be put on a PO. This is frustrating when we put in an order for more than 50 items and have to create multiple POs for a single order. I think the easy fix would be to have those POLs remain checked…
45 votes -
Add Associated PO Line field to New Order Import Profile & Update PO Lines job
Alma lacks the functionality for batch adding an Additional PO Line to a group of PO Lines. Because Alma lacks this functionality, a great deal of manual work is required.
Here is the use case: we made a large prepayment (the parent POL), and now we are creating technical orders (the child POLs) for all the items we chose to purchase with that pre-payment. We need each of the child POLs to have the parent POL as its Associated PO Line. We can create the child POLs in a batch using a New Order Import Profile. However, we have no…
45 votes -
Post download links for digtization requests to user's Primo account
Currently, Alma will post a download link to the user's Primo account when a resource sharing request is filled digitally. Alma does not post a download link to Primo when a digitization request is filled. This difference can be confusing for users, so it would be very helpful if download links for both resource sharing and digitization requests were posted to the user's Primo account.
45 votes -
Add Item‑Level Usage Option to Deselection & Retention Project Scopes
When determining eligibility for Deselection/Retention Projects, Alma is currently only evaluating title‑level usage rather than item‑level. This means that loans of Lost or Withdrawn items are being considered and the project is actively excluding items that have not circulated for years (because a now lost/withdrawn copy circulated more recently). Further to this, this information is not readily available without going into Alma Analytics.
Proposal: add an option within the Scope configuration that allows institutions to choose whether usage should be evaluated at:
Title Level (current behaviour)
OR
Item Level (requested enhancement)This enhancement would:
- Improve accuracy of deselection lists
- Prevent…
45 votes -
Link to next higher level when Alma can't match to article or chapter
When Alma cannot successfully link to an article because of no exact match is found, it would be helpful for Alma to use alternative metadata, such as the page number, to target. It would also be useful to users to be taken to the next higher level of the publication, e.g., the journal issue page. If there is uncertainty about the issue, then users should be taken to the journal page.
This problem frequently arises for short pieces and book reviews. For example, some journals publish book reviews in a section entitled, "Book Reviews", rather than as separate articles. In…44 votes -
Ignore call number prefix ($$k) in BROWSE SHELFLIST in Alma
Alma's Browse Shelflist function includes the call number prefix (holdings record field 852 $$k) when generating the browse list. At the University at Buffalo, we use that prefix for oversize volumes, and for a variety of other sub-locations, designations and shelving areas.
As a result, any holdings with a prefix ($$k) does not show up alongside holdings in the same call number range, essentially hiding many titles from staff who seek to browse the shelf list.
An advanced search for specific library holdings, permanent call number type, and permanent call number does not remedy this issue, as it does not…
44 votes
- Don't see your idea?