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.
1809 results found
-
E-Collections: Read-only access to Alma for other institutions
We wish to provide read-only access to our Alma instance to other institutions in our consortium and vice versa so that we can compare setup more efficiently. The permissions need to be quite restrictive and prohibit access to financial, patron data, etc. but allow us to view E-Collection, Service and Portfolio level screens.
When comparing set-up of our e-collections we are spending a lot of time discussing via email and sharing screen shots, which is not as efficient as being able to go in with a view privilege and compare in real-time.
76 votes -
Ability for fulfillment staff to renew patron loans from other institutions under network activity in Alma
Our consortium would like circulation desk staff to have the ability within Alma to renew items on loan from other institutions from under a user's network activity tab (renew all and renew selected, though renew all being more helpful if both are not possible).
Currently, only the user has access to a renewal option via their Primo VE My Library Card.
76 votes -
Alma should remove any whitespace before/after identifiers, barcodes, call numbers etc.
Alma should automatically remove any leading or trailing whitespace in user identifiers, barcodes, call numbers etc. - any kind of identifiers entered manually or via copy&paste. Barcodes that are not working, users that are not matched at login are examples of real-life malfunctions that cost us time to analyze, all caused by a simple trailing blank entered in a form. It could be easily trimmed by Alma itself with neglectible implementation effort.
76 votes -
Show 'chapter/article title' and 'chapter/article author' in completed digitization requests and in Analytics
For copyright reasons, we need to track whether users have requested an article from an issue or a chapter from a book from which they have already received a scan.
Completed digitisation requests in Alma do not show the chapter/article title or chapter/article author, only the overall title requested. The data is not available in Analytics either.
This means that we are reliant on a local spreadsheet to track what users have already requested.
We would like to see the data available on the completed requests and in Analytics.
76 votes -
Create a set from records held in the Metadata Editor
It would be useful to be able to save all of the records that you are working on in the metadata editor as a set to come back to later.
For example, this would be helpful when working on a bound with where you need to work on several records at the same time and need to add links across the records. At the moment, if this work is not completed and we need to return to it later, we would then need to create an itemised set by searching for and adding each record individually. Instead, it would be…
76 votes -
Configuring External Library names for display in Primo
In Alma it is already possible to enter external location names for display in Primo. We request this option for library names, too. Currently, the configured library name is exposed to the user in the Primo Getit tab as well as to the staff in several places in the Alma user interface, f.ex. the „currently at“ pickup list and the persistent menu. We request the possibility to configure an internal name for display in Alma (for example in abreviated form) and and external name for display in the Primo Get it tab.
75 votes -
Preset item policy for subscription PO Lines
Having the ability to set an item policy for a subscription PO Line would save time and trouble. Currently, when a serials item is received (checked in), one must go into the individual item record to set the item policy. Too many clicks. Also, if someone else is checking in serials, they might forget about this additional step. If someone tries to check out an item, will the person at circulation know that it is in-library use only, 3-day use or 14-day use?
75 votes -
Add fund name to communication letter and po line claim letter
When starting a communication with a vendor the body field is pre-populated. Unfortunately, the fund name is missing. We would like to have to option to add the fund name in the communication letter (via letters configuration).
75 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
75 votes -
Field to add "Charges" in the price.
We need a field that allows us to add "Charges" in vendor record or in the POL, now these only allow discounts.
Nowadays we have to assign this charge manually in the POL's list price.
74 votes -
Send overdue notifications only on library's open days
Since we would prefer to avoid to send overdue and lost loan notifications to our patrons on Sundays and holidays, it would be great to have a further option for when to automatically run the “overdue and lost loan job”, that is, to run it only “on the library’s open days”, based on the opening hours set in the “Calendar management”.
74 votes -
Preferred term correction - correct coding when flipping LCSH to LCGFT
When a 655 field is coded for LCSH and matches a non-preferred term in LCGFT, Alma flips the heading to the preferred LCGFT term but does not update the coding (it should change the 2nd ind to 7 and add $2 lcgft).
The problem is limited to cases where:
A bib heading 655/_0 matches a non-preferred term in an LCGFT authority
What happens is:
The PTC job flips the heading to the LCGFT preferred form, but it does not change the 2nd-indicator from 0 to 7, and does not add $2lcgft
What is not a problem:
655/0 headings that…
74 votes -
Get auto-renewals dates back into Analytics
Since the recently released August version, Analytics does not longer show the auto-renewal date due to a mentioned performance improvement on the nightly job. Please consider rolling back this change as it actually makes it impossible to get how many auto-renewals were made on a certain day in the past, since the only date we currently have is the Last Renewal Date which is updated every time the job runs. We virtually lost our auto-renewals log integrity.
I know we still have this Last Renewal Date, the amount of auto-renewals and the Loan Date, and we could easily calculate the…
74 votes -
The ability to sort the "List of Items" by "Copy ID" or "Item Call Number"
Adding "Copy ID" and "Item Call Number" to the "Sort routine" in the "List of Items would be very helpful for us. We catalog various types of equipment to loan out to students. The equipment has a Permanent Call Number which designates the type of equipment and where the equipment is from using a code. Each piece of equipment belonging to that bibliographic record has an item call number so being able to sort by item call number or copy ID would make our life easier. Thank you.
74 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.
73 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.
73 votes -
Implement the Counter Registry API
Tasha from COUNTER asked (during ER&L 2024) if anyone had spoken with ExL about implementing the registry API. In the registry, there's SUSHI details, contact details, and notifications. Harvesting from COUNTER registry would reduce complications and would alert librarians to any problems.
Tamar, Tasha, Beda, and I discussed this in person at ER&L 2024. :)
73 votes -
MDE Search Resources mask should be empty
When opening the Search Resources mask in MDE, the previous search is still in the data mask. For us there is no benefit for this behavior and we would like to have an empty mask and not to clear the mask every time before starting a new search.
(If other libraries need this opportunity, we would suggest to make the default settings for this mask customizable)73 votes -
Limit number of resource sharing partners in a borrowing request's rota
We sometimes see instances where a problematic resource sharing requests are sent to dozens of partners before they're cancelled or go unfilled. It would be very helpful if we could somehow limit the number of partners that appear in a request's rota. Since we would always want to include a lender of last resort like ILLiad or WorlsShare ILL as the final partner, it would probably be best to allow us to limit the number of partners from a specific rota template that can be added to a rota.
73 votes -
Display NZ activated Portfolios even if Related Records Services are enabled in an IZ
In our consortial environement, we have activaded a number of portfolios on NZ level, which we would then expect to also be available in our IZs. Often this is not the case and instead of a specific article that is part of the portfolio, only the journal it belongs to is displayed under Services for Related Titles. As Ex Libris informed us, this is because Related Records Services are activated in our consortium, which leads the link resolver to display those related journals instead of checking if there is an NZ activated portfolio. Their solution to this would be to…
73 votes
- Don't see your idea?