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.
129 results found
-
Show linked purchase requests in 'Other details' beneath title record
It would be great if purchase requests that are linked to titles could be accessible via other routes rather than just the 'Manage purchase requests' section. Please could purchase requests that are attached to a title and a POL be added to the 'Other details' section beneath a title record in a repository search? This would allow us to quickly ascertain which titles have purchase requests linked to them.
1 vote -
Searching titles with "&" vs. "and" in Alma
In Primo VE, when a title in the 245 contains "&", if the title is searched with "and" in place of the ampersand the correct record will come up. This does not work the same way in Alma, however.
https://www.screencast.com/t/1mlHd3mIv
In some cases, a 246 field could be added to have "and" spelled out but that is not a universal solution. We would like to ensure that "&" and "and" could be used interchangeably in Alma title searching as it seems to work with Primo.
1 vote -
Allow multiple Z39.50 to be setup in Alma
Right we use the only Z39.50 setup for Interlibrary Loan's ILLiad. One of our librarians would like to connect a new Z30.50 to search through Endnote to run systematic reviews. We had previously wanted to use another Z39.50 setup to input a more comprehensive search in Search Resources in Alma. If we can get multiple Z30.50s setup in Alma it would help us connect various sources to Alma and make it more robust.
1 vote -
Improve search for ayn diacritic directly after hyphen
In a romanized Hebrew search when an ayn diacritic appears directly after a hyphen, there is zero results with the expected search: "gozeret ha-orot" (no spaces). This very search has the expected result in Primo but not Alma. That search also works in OCLC Connexion. I was told to use a space instead of a hyphen in Alma, which brought up the record but it is not the way one expects to search in this instance.
1 vote -
Add a tab to Manage Sets that shows Sets linked to Publishing Profiles
From Admin - Manage Sets we can see My Sets, Public Sets, and All Sets. It would be useful for there to be a way to more easily distinguish and find sets that are used in Publishing Profiles. As more and more integrations with third party services rely on Publishing (HathiTrust, Google Books, RapidILL, BrowZine, Syndetics, etc.) more and more sets need to be created and maintained and occasionally tweaked if locations or libraries are added, removed, or changed, or if new materials within the sets become unshareable for some reason.
The current workflow to find the right set is…
1 vote -
Add Call Number to all Overlap and Collection Analysis Reports that include Print
Add Call Number to all Overlap and Collection Analysis Reports that include Print
The new Title Look Up function that permits comparing a list of print to various electronic collections is excellent. However, the output reports don't include the print call numbers. That would be a significant improvement; staff could then easily use the report to go to the shelves. As it is, we have to do a separate process in Analytics just to get call numbers which seems like a waste of time.
1 vote -
automated import profiles - create log file with useful information if process fails
We are finding Alma less than helpful in cases where the automated download fails due to a parsing error. Apart from actually creating a log file as suggested here, there would be other ways to improve this experience.
This is what currently happens:
- for automated import profiles, no log file is created when the process fails, the emailed report simply states that the import failed, there is nowhere in alma where I could find any further information
- because of this, we then need to try and run the import manually, so we can see what the issue is…1 vote -
Allow Correction of MARC21 Field Data in Metadata Configuration List
In Config-->Resources-->Metadata Configuration-->MARC21 Bibliographic, Alma users can add a new MARC21 field not currently included in the suite of out-of-the-box MARC21 fields by using the "Add Extensions" command to upload a XML file that contains field definitions and prescribed indicator and subfield values. The values in that file trigger error warnings in the Metadata Editor if that field contains incorrect indicator values or unauthorized subfields in a given bibliographic record. However, it is currently NOT possible to delete a newly added MARC21 field or upload a revised XML field definition file without deleting the entire extension pack.
What we're requesting…
1 vote -
Overview of linked bibliographic records in chronological order
When cataloging, it is beneficial for catalogers to view an overview of linked bibliographic records in chronological order, rather than solely in alphabetical order. This pertains to the presentation after selecting F3 - view - bibliographic records. Currently, there seems to be no option in Alma to change this presentation. While it is possible to search from authorities outside the Metadata Editor, this process is more time-consuming.
Catalogers can work more efficiently if they can quickly determine whether an author/corporation, etc., is the correct one. Being able to promptly view the most recently published editions aids in this process.
As…
1 vote
- Don't see your idea?