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.
1693 results found
-
Save certain subfields from being overwritten via F3 and PTC
When linking names, subjects etc. from authority files in various BIB fields, some cataloguing conventions require giving additional information in certain cases.
One example for such a requirement, stemming from the German speaking countries, is to add the time and place of an auction when linking to the genre/form term “auction catalogs” in BIB field 655 (see attached screenshot). This additional information is, of course, specific for each BIB record and must not be overwritten or deleted, if at a later point in time either PTC processes said BIB record or a colleague invokes the F3 functionality.
Since different subfields…
258 votesHello everyone, for those who raised comments about the correction of 830 $v, could you please provide a detailed, step-by-step explanation of the scenario in which this subfield gets overwritten?
-
Manage Purchase Requests - facet by 'Assigned to:' and display Library notes
Add to the facets the option to filter by 'Assigned to:'
Also the option to see the notes tab details when viewing all Manage Purchase Requests 'in review' .
We can see the requestor note but not any Library notes from the Manage Purchase Requests screen to make this information easier to review.3 votes -
Allow EOD to generate multiple items (multi-volume sets) via Import Profiles
Currently, importing Embedded Order Data to generate POLs with a New Order Import Profile creates a single item per quantity ordered in the POL. Similarly, Update Inventory imports can't update more than one item. Unfortunately, when ordering multi-volume sets, this means volumes 2-n are left off the POL and must be added manually. This creates significant manual work for acquisitions teams, for both approval plans and firm orders. Being able to specify Quantity ordered AND Number of Items (per set) would disambiguate how many volumes we expect to receive, and allow for code that could specify barcode/enumeration on each of…
14 votes -
Add the ability to apply multiple rolling embargoes to a single electronic portfolio
If a portfolio has access to two sets of rolling publication dates, it would be helpful to have the option to apply multiple rolling embargoes. For example, an institution might access to the last 10-20 years of publication as well as the last 3 years of the publication, both on a rolling basis.
1 vote -
Add a parameter to manage suppression of unheld purchase requests
Currently, when a bib record is created for purchase request for a title not held by the library, it is automatically suppressed by default. We would like the option to make these records visible to users so they can place holds and track availability. Please introduce a configurable parameter that allows us to control whether such requests are suppressed or displayed.
2 votes -
Fullfillment / Manage Patron Services - Action Claim returned - Freeze loan suspensions
When claiming an item as returned, the loan’s status is changed to Claim Returned. The item’s Process Type value is Claimed Returned, and the item remains requestable and is considered to still be on loan. Due dates cannot be changed on loans in "Claimed Return" status. By default, overdue fines accumulated prior to the item being claimed as returned are applied to the patron's active balance, but no new overdue fines accrue from that point onward.
We would like the “Claim returned” action in Alma to freeze loan suspensions. No loan suspensions will be put in place once the item…17 votes -
Job “Withdraw Physical items” and holding of related records
With the “Withdraw Physical items” job, Alma does not provide the option of preventing the deletion of holding and bibliographic records when there are Holding of related record. We would like an additional option “Delete holdings; delete bibliographic records that have no other holdings and that have no Holding of related records”.
39 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.
40 votes -
enhance current authorities reports
Hi, Sir,
The current authority reports can list local authority headings that are or are not linked to bibliographic records. Please enhance the authority statistical report function by adding:The ability to generate statistics on CZ authority records, including local/CZ authority records for author and subject headings.
A statistical summary and detailed list of bibliographic records linked to local/CZ authority records for author and subject headings.
A statistical summary and detailed list of local bibliographic records with author and subject headings that are not linked to local/CZ authority records.
This will allow librarians to systematically review and update records, ensuring…3 votes -
Implement Checks on the Authority Heading Type for Institutions Using ID-based Authority Control
Currently, when authority linking in Alma is based on ID rather than text, Alma does not check whether the authority heading type in the bibliographic record matches the heading type in the authority record. For example, Alma will link a 600 tag in the bib record for personal names with an authority record whose heading is in tag 110 for corporate names if their ID matches, even though Alma would not offer that option if F3 were pressed.
We would like Alma to (1) avoid linking in such cases and (2) flag these instances in the authority control task list.
…
2 votes -
Improve Request Limit configuration to match Loan Limit configuration
Request limit configuration is currently extremely limited:
- It applies across the whole instutition
- It is a single limit which can't be distinguished for different material types, items or kinds of requests
- It is linked only the user group of the patron.
We propose that request limit config should match loan limit config and allow for other variables:
- Application to a specific library
- Limit by item policy, location, material type, user group, statistical category and job category.
An additional improvement would be to allow some link up between request limits and loan limits. They are particularly problematic for remote storage integrations…
7 votes -
Collection - report who added title and when
When adding titles to Collections (Resources\Manage Collections) it would be helpful if it reported who and when a title was added to the collection. Report of this via Analytics would be preferable but displaying in Alma would be a start.
3 votes -
Automatically suppress bib records generated from the Order It! Amazon plug in.
Allow the option to automatically suppress bib records created from the Order It! Amazon plugin. Additionally, allow the option to have the titles of the generated brief bibs typed in all capital letters as per standard practice for acquisitions brief bibs. Brief bibs typed in all caps help visually distinguish them from full bibliographic records.
1 vote -
Top Level Collection Analytics
Please add top Top Level Collection information to Analytics. Specifically, we are looking for data on changes to the collection such as items added, who added them, when they were added, and any changes to the collection or sub-collections and who made the changes.
12 votes -
Allow us to create duplicate borrowing requests via the Users API
The SUNY system has created an ILLiad addon that automatically converts ILLiad borrowing requests into either Alma borrowing requests or Alma hold requests (depending on whether the requested item is locally available). We're using the Users API to create these requests in Alma. We've figured out how to override the Alma function that blocks the creation of duplicate hold requests when necessary, but we there's no way for us to override the function that blocks the creation of duplicate borrowing requests. Please add this feature to the Users API.
4 votes -
Overlap and Collection Analysis reports enhancement
As a collection development librarian, I propose allowing the selection of multiple collections we want to compare. Repeating the same process for different collections is time-consuming. For example, we have 8 active IEEE collections, and I have to match them one by one with other collections.
Also, is it possible to re-run the Overlap analysis report if I forget to include some collections, instead of creating a new analysis each time?25 votes -
Add Fulfillment Note to the New 2025 Manage Patron Services Table Customization
We use the Fulfillment Note field to track Lost Items by recording the patron ID, replacement cost, and billing date to our Finance department, allowing us to efficiently identify returned lost items. Additionally, we check out lost items to a dedicated patron record to facilitate tracking, reordering, or withdrawal over time. Adding this feature to the Manage Patron Services Customization Table would help ensure these notes are consistently recorded.
17 votes -
resource sharing lending participating items, exclude by provenance
Would it be possible to add a new filter to the Resource Sharing Lending Policies Participating Items? At present it is only possible to exclude by material type, item policy and location. We would like a new filter for item provenance please.
6 votes -
Enhancing Security in Alma: Restricting Return without scanning the item, Claim Return, Found Functions to High-Level Roles
The new Alma Manage Patron Services, implemented in February 2025, allows any role to "Return" an item without scanning it. This function should be restricted to high-level roles only. Similarly, the "Found" and "Claimed Return" functions should also be limited to high-level roles.
Currently, WS students can access these functions with the Circulation Operator – Limited role. While we are in the process of removing the Actions Customizations from the Settings wheel, our preferred solution is to restrict access to these functions to higher-level roles.
7 votes -
Problems receiving documents from POL (Purchase order Line)
Since the change to Alma's new visualization, when receiving the document from the order (POL) there are two behaviors that, in our opinion, are regressions:
- When we mark the check for “Keep in department” Cataloging copy, this check is not marked for future reception. We request that this check be kept marked by default.
- When the reception date has to be entered, marking a date before the current date on the calendar is not allowed.What we are asking for is that, since this improvement that has been presented (display of all data integrated in the POL), when…
12 votes
- Don't see your idea?