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.
1784 results found
-
Request for Enhancement: ALMA Records Customization Functionality
Currently, the Records Customization feature in Alma only allows for configuring the visibility and order of fields, but does not support modifying the structure or composition of individual fields.
We would like to request an enhancement that enables institutions to customize the structure of each field according to their needs.
For example, the Creator and Imprint information are currently displayed as a single combined field. We would like these to be separated so that institutions can independently select and display only the elements they require.
3 votes -
maria.nordgren@umu.se
When adding a portfolio from CZ from a collection that is not in your IZ. The whole collection is imported to IZ. We use this for moving a portfolio from one collection to another. Example one portfolio is missing in ClinicalKey Dentistry, but is found in ClinicalKey Books, I can activate the portfolio, but then the ClinicalKey books collection is transfered to IZ. We would like to be able to activate a single porfolio without that the collection is imported
6 votes -
Rename Fulfilment Request status "READY" to either "PENDING" or "INQUEUE"
Currently Fulfilment request status READY - is misleading given its definition is
"The request is still in the queue, not activated yet. Currently, there is no available item to fulfill the request."It does not even mean "ready to be requested" given the request has been made already.
Note also "READY" is displayed in the User Request area in Alma, and this can be confusing to the client facing staff. They have to understand and be able to explain to clients that their requests are NOT READY yet despite the Alma labels says READY.
See Case#10569064
1 vote -
Enable adding labels in bulk to title-level records for large sets
During large-scale projects such as: weeding/deletion, we need to mark many records with a label indicating their status.
Current Limitation:
Labels cannot be applied efficiently to large numbers of records; it is limited to 50 at a time.Requested Enhancement:
Provide a bulk mechanism to add labels to title level records beyond current limits.Benefit:
Improves efficiency, reduces manual work, and supports large collection management workflows.2 votes -
RS Pick Slip configuration
Currently the FUL Incoming Slip Letter can only be configured to display the Library of Congress classification, and not the Item Permanent Call Number. This means the pick slip generated in the Resource Sharing lending workflow shows an incorrect call number.
Please make the Item Permanent Call Number available as a configurable field in the FUL Incoming Letter, so that pick slips display the correct shelf location.
1 vote -
ellipses in specific contexts(三点リーダー“…”)
In Japan, we use ellipses in specific contexts.
Please adjust both Cloud App and Alma so that typing three middle dots and converting them results in an ellipsis (“…”) with three dots centered.
*Note: This is not three periods (“...”).I believe this issue is likely caused by the font type, language settings, or similar factors.
Thank you for your cooperation.3 votes -
madelene.turnbull@otago.ac.nz
Add ability to include or exclude specific location codes in the Retention / Deselection workflows
Currently the retention and deselection workflows only allow selection for inclusion at the library level. It would be helpful to be able to include or exclude specific location codes within a library's collections, for example it would be helpful to be able to exclude from deselection recommendations all titles in our Special Collections location codes. Currently the only way to do this is to run the search, export results to excel then filter by collection code.
3 votes -
We would like to request an enhancement to Alma.
When a user reports that a borrowed item has been lost, and the item is not returned within a certain period, we would like to have a function that allows the circulation staff to change the item’s status from "Lost" back to "Loaned."
6 votes -
DARA recommendations for autoholdings should ignore open access collections
DARA recommends using autoholdings. However, it does so even when it really shouldn't recommend it. Situation: an institution has activated an open access collection, and doesn't subscribe to anything from that vendor, but DARA recommends using that vendor's autoholdings, which confuses librarians. The correct operation of the DARA recommendations would be to ignore open access collections.
3 votes -
Enhance Analytics Support for Authority Records (Additional MARC Fields)
We would like to propose an enhancement to Alma Analytics for authority records.
Currently, Alma Analytics provides limited support for authority fields, such as 1XX and 373. However, many other important MARC authority fields are not available for reporting and analysis.
We recommend adding more authority fields to Analytics, including but not limited to:
046 – Special coded dates (commonly used for birth and death dates of authors)
372 – Field of activity
374 – Occupation
375 – GenderThese fields are widely used in authority records and are highly valuable for data analysis, authority control, and research purposes.
Providing…
1 vote -
Add full MARC records to CZ for Mohr Siebeck
This collection of Mohr Siebeck eBooks contains many titles with metadata that are too poor and need to be enriched. Could you please follow up with Mohr Siebeck?
MMS-ID: 9919375751300041
Thank you for your intervention!
Kind regards,1 vote -
Counting Searches in Alma Persistent Search Box
We know that the usage actions in Primo VE can be retrieved in Analytics to measure patrons’ various search actions. This helps library identify the strengths and limitations of current Primo VE user interface, and review it to better meet patrons’ needs.
However, there is currently NO way to retrieve search counts from Alma’s search persistent box in Analytics.
Counting Searches in Alma Persistent Search Box
Library staff often use the Alma persistent search box to search for records for various library operations—for example, locating a bibliographic record to create a PO line—across the institution and community zones (and the…
2 votes -
Output MARCXML file (over 8GB size) from Publication Profile compress into .tar.bz2
By default, the publication profile for an XML file is compressed into a .tar.gz file. We host the exported file on our FTP server so that it can be downloaded from the BNE website. If the file exceeds 8 GB, it is not compressed. Our IT staff have informed us that compression to .tar.bz2 makes the file even smaller. We propose that, in addition to .tar.gz, it should also be possible to compress MARCXML files using the .tar.bz2 extension.
7 votes -
Encumbered Balance Amounts only link to unpaid purchase order lines
In the Summary Details of an allocated fund code, there are hyperlinked amounts listed next to Expended Balance and Encumbered Balance. We want the Encumbered Balance amount to link through to only purchase order lines that make up the total balance amount listed in the hyperlink.
Currently it links through to any purchase order line that had an encumbrance placed on it with this allocated fund code. Regardless of whether the purchase order line has already been expended and disencumbered or still has an outstanding encumbrance waiting to expend on it.
This would be helpful as it would give us…
4 votes -
Expose Shared License, Distribution, and Negotiation Details in the license REST API
The Alma license REST API (POST/PUT/GET /almaws/v1/acq/licenses) does not expose several pieces of license configuration that are available in the Alma UI. This prevents end-to-end license provisioning via API and forces manual UI work after every API call.
Fields currently absent from the API:
At the top of the License Details form — the "Shared License" on/off setting, and the "Distribution" multi-select controlling which sections are shared with member institutions (Summary, License Terms, Notes, Attachments).
In the Negotiation Details tab that appears for shared licenses — per-member rows containing Member Name, Price per year, Price increase (percentage), Currency, Start date,…
11 votes -
Enable Full MARC 21 Format for Holdings Data (MFHD) Editing in the Metadata Editor
We request that the Alma Metadata Editor (MDE) be updated to allow direct MARC-level editing for all fields in a Holdings Record as defined by the MARC 21 Format for Holdings Data (MFHD).
In the library industry, a "Holdings Record" is a unified data carrier. It includes the shelving location (852), but also other copy-specific fields such as donor (541), the provenance (561), and the individual item details (876-878). In the MARC standard, the "Holdings" and the "Item" are part of the same metadata record.
While we recognize that Alma’s underlying architecture treats “Items” as child entities of “Holdings”, the…
3 votes -
Temporary Location Status
Alma temporary location due dates are informational only; adding configurable alerts or automated actions when those dates expire would reduce manual monitoring and improve location accuracy.
1 vote -
Have libraries' open hours as configured in Alma display in Primo or embeddable in library home pages.
We would like to display the open hours, closed exceptions, etc. that are already configured in Alma in the Primo landing page and have them able to be embedded on a library web page. That way if hours change for holidays, seasons, etc. they will be correctly shown in all locations without having to change posted hours in multiple places.
3 votes -
Add an "OA articles only" option to coverage tab in electronic portfolios.
Several autoholdings collections for journals include titles with OA content even if there is no active subscription, meaning that our only access to the journal is for the OA content. This makes it hard to provide accurate coverage information to our patrons. While we can add a public note as a workaround, it would be nice if there was an "OA only" option (maybe a checkbox) on the Coverage tab for electronic portfolios.
13 votes -
Be able to see the full email message when using Send email to partner or Send query to patron
Currently we cannot see the full context of these email messages, we only see the “body” of the email, but that does not include any pre-set text or the greeting and signature.
Staff are left guessing what information is included in the full message, and the sent messages often look poorly composed and unprofessional. It is inconvenient and time consuming to find the templates to check the complete message before sending. Knowing what the full message looks like at the moment of writing, would help staff decide exactly what to write in the email
Message.5 votes
- Don't see your idea?