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.
1773 results found
-
Narrow Withdraw Items job functionality to Physical Items sets
Restrict the Withdraw Items to functioning with Physical Items (barcode) sets. (Currently it will run with sets of Physical Titles and effectively perform as if the job DELETE BIBLIOGRAPHIC RECORDS were run with the “Delete all associated inventory resources” parameter selected.)
Include OCLC number in the Excel Export for Physical Items (currently only Physical Titles sets export with the OCLC number, but those sets function erroneously in the Withdraw Items job)
35 votes -
Receiving note for electronic resources
It would be fantastic if a receiving note option was included for electronic resources as it is for print resources (a field which can be extracted for analytics). The current notes field can not be accessed via analytics and it is therefore difficult to track trends in usage, information about cohorts using different resources, reasons for purchasing, etc.
35 votes -
Allow Alma to export preferred names to ILLiad when automatically creating ILLiad user records
When Alma automatically created an ILLiad user record for someone who has submitted a resource sharing request that must be exported to ILLiad, it always passes the First Name and Last Name fields to ILLiad even if the user's records contains a Preferred First Name and/or Preferred Last Name. It would be incredibly helpful if Alma could pass preferred names to ILLiad if the user's record contains any preferred names.
35 votes -
Use preferred email from Partner record for shipping digital Lending Requests
Often the Requester Email in a Lending Request is not the email that we can ship a digital item to (or sometimes the Requester Email is empty). Instead, the email address we use is from the preferred email address in the Partner record. We would like configuration to be made available so institutions could choose to use the preferred email address from the Partner record in Alma when shipping digitally instead of the Requester Email address that comes with the Lending Request.
35 votes -
Have searchable Notes fields in vendor records
It would be great if the data in the Notes tab of vendors records could be searchable - possibly as an Advanced Vendor search, or as part of a keyword search, or even within Analytics. Some data from Voyager's 'alternative vendor name' field has been migrated into the notes and it would be useful to be able to search on this.
35 votes -
Creation of Lending requests by DOI or PMID
It should be possible for ILL librarians to create Lending requests received by email from non-Alma Partners by entering a DOI or PMID using Alma Resolver Augmentation.
This would save the time involved of entering each field manually by copying and pasting.
The feature already exists in Borrowing but was not developed for Lending.35 votes -
Improve reorder functionality in Fulfillment Unit Rules
Right now, if you add a new fulfillment unit rule, it goes to the bottom of the list. If it needs to be elsewhere, you have to use the reorder arrows to quite tediously move the rule up and down (click ... reload page ... scroll to find where rule is ... click ... reload page ... ad nauseum.)
It would be SO much better if we could either
1) Drag and drop the rules (and then require clicking a save button to save the new order, and/or
2) Reorder using the row number by exporting to an external spreadsheet,…35 votes -
Alma Analytics> Fulfillment> notification sent indicators
In the Alma Analytics Fulfillment subject area, there is a "Courtesy Notification Sent" indicator field.
I would appreciate similar indicator fields for the other types of notifications sent to the user for the transaction, such as the "Ful Overdue and Lost Loan Letter", the "Ful Overdue Lost Loan Notification Letter," and the "Return Receipt" letter.
It would be helpful to confirm that Alma generated each letter for the user, for the transaction.
Since we have a retention period set on how long each letter copy will stay on the patron's attachments tab, it is possible that the patron may still…
35 votes -
Enable creation of individual patron blocks for loans of specific material types
If an institution needs to prohibit an individual user from borrowing a particular type of resource temporarily, e.g. placing a temporary ban on laptop loans for that person, then there is no way to block them from borrowing items of that specific material type without preventing them from borrowing everything else as well. As a result, we are unable to apply blocks in exceptional circumstances, such as with our laptop loans service, because the block would be disproportionate and prevent the user borrowing any physical items at all. The only workaround would be to have a ‘Blocked’ user group configured…
35 votes -
Add block information box on patron’s account landing page
Currently, when accessing a patron’s account through the “Manage Patron Services” tab, the patron’s account landing page does not show the block information (a pop-up does show up but with incomplete information, as recorded in a SF case). In order to access block information, one has to click on the patron’s name, and then navigate to the block tab.
The suggested idea would be that a box containing block information be added in the left-hand column of the patron’s account information, under the box containing loans, returns, requests and fines and fees information. Block types could be described with the…35 votes -
The default receiving status in manage items of receiving workbench is all and it should be not received or should be configurable
As part of the new prediction pattern development it is possible in the receiving workbench to receive new items and filter the 'manage items' section by "all" "received" or "not received".
Currently it defaults to "all" which is not what would be desired because
A. it would show too much
B. they would need to manually search for what they want to receive.It should default to "not received" because then they can choose the issue they have in hand and receive it. Another option would be to have it always remember the previous filter of the user and use…
34 votes
Anonymous
responded
Submitted by Ex Libris PM on behalf of our customers
-
Enable embedding fund balance graphs and data on Alma Home Screen
Fund balance data from Analytics is inaccurate as data is piped in to Analytics on a daily basis, making fund balance widgets created in Analytics less useful for checking available balances. We would like to request the ability to quickly access up-to-the moment fund and available balances available under each fund under Acquisitions > Funds and Ledgers > Fund > Reports in home page widgets. This would enable staff placing order to check live fund balances easily on a regular basis.
34 votes -
Add suppress functionality to context menu in list of holdings
When a staff member is looking at a list of holdings for a physical title, the right-click context menu / actions (ellipsis) menu should include a function to suppress holding.
It's inefficient to have to enter the MDE to complete this action. It's inefficient to have to run a job for just a few holdings at a time.
34 votes -
Automated order claiming
We need a solution for order claiming that works automatically for this for groups
- one time orders
- subscription orders
- standing orders
- online resource orders.Workflow:
a) The expected receipt date/expected activation date in the order/item/portfolio is reached.
b) Alma must send an claim to the vendor.
c) Alma changes the expected delivery date/expected activation date automatically by taking the information from the vendor-account (date of day plus expected receipt after ordering (days)/date of day+expected activation after ordering (days)).
d) A reminder in the task list is not necessary.Details for the four groups see attachment please.
34 votes -
Add roles to “Use Electronic Inventory Features” in DARA
Currently, the “Use Electronic Inventory Features” in DARA is available only to users with the “General System Administrator” role.
We propose making the “Use Electronic Inventory Features” available to users with the “Inventory Operator” role for viewing purposes only, without the ability to configure or run jobs.
This will allow more users to view important content news, and better understand and manage electronic resources.34 votes -
Add the option to custom harvest the entire institution's SUSHI accounts
We usually analyse the usage data of the whole previous year. In our "Monthly usage data" overview many reports failed. We have 100+ vendors with SUSHI accounts.
To manually go to each vendor and custom harvest the year's usage data takes a long time.
Please include the option to run a job that harvests ALL SUSHI data as a custom harvest.
34 votes -
Acquisitions API - Interested in user – add other identifiers in addition to Primary ID
Currently Alma allows multiple identifiers to identify ALMA Users, however the Acquisitions API (Interested In users) mapping only allows “primary_ID”.
We’d like any other identifiers used in Alma also be allowed in the mapping (e.g. Email Type). If this is added on the API parameter, staff can use the less sensitive info instead on vendor site.
Noting that adding other identifiers in the Interested_User api parameters - is only doing what EOD acquisition workflow/mapping can already do.
It is cumbersome for staff having need to search the requester’s primary id to be able to use this feature.
Ref #06652820 –…
34 votes -
Community-Managed electronic collections: Add several portfolios to one title
In Community-Managed electronic collections, it is not possible to contribute a second portfolio to the same title that is pointing to a different URL. Use case: Both URLs are valid, both contain copies (in part) of the journal. It would be nice, if the contribution only gets blocked, if the URL of the newly contributed portfolio is identical to the existing one.
34 votes -
Add free/not free information about collections
Currently through Analytics it's not possible to create a report on collections with the information: "Is free?" and "Is Free? (override)".
It is just possible to find "Service is free" and "Service is free (override)" fields, that exclude all collections that don't have any services, such as databases.
We propose to add fields "Is free?" and "Is Free? (override)".34 votes -
Please add 3xx field support in Bibliographic Details dimension of Alma Analytics
Currently there are many fields in the 3xx range which are not supported OTB in the Bibliographic Details dimension of Alma Analytics.
We have mapped 300 to a Local Param several years ago, but we are stymied in our work updating to RDA consistently as the desired foundation for then considering LOD work in BIBFRAME, given this is a key area with many 3xx fields utilised such as 334, 335, 336, 337, 338, 340, 344, 345, 346, 347, 380 and 382.
Although the number of Local Params increased in 2024 finally from 10 to 30 we use many of these…34 votes
- Don't see your idea?