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.
67 results found
-
Gulshan Dynasty, located in Sector 144, Noida
Gulshan Dynasty, located in Sector 144, Noida, offers a luxurious lifestyle blending modern amenities with timeless elegance. The prime location ensures easy access to essentials like schools, hospitals, shopping malls, and corporate hubs. The property features state-of-the-art amenities like a luxurious clubhouse, lush green spaces, sports facilities, 24/7 security, and sustainable living. Each apartment is designed with elegance in every corner, offering a serene yet connected living experience . Contact us at 7983028075 or 9711298311 to book a site visit or get more information about this exclusive property.
1 vote -
Expand API access to all record fields across all record types
Libraries frequently use API access to Alma records to complete a variety of tasks, provide services, and support special projects. Currently, the types of records and fields that are accessible via APIs are limited. For example, in bibliographic records, the 024 (UPC) field data is inaccessible via the API. Please Expand API access to all record fields across all record types.
3 votes -
Add API support for read/update/add/delete contact e-mails in Organization units: library, Institution Zone
Use case: Library / IZ contact e-mails are used in many workflows as the e-mail sender for letters generated in Alma. In our network (31 IZs), we are running a consortia mail server. As part of the configuration, we moved the library and IZ contact e-mails to our consortia domain. For example, library@abc.ch is now library-abc@swisscovery.net. This means changing the configuration of each library contact e-mail in the IZ to a different e-mail address and adding a description.
Initially, we made these changes manually. However, as e-mails can change, we have to maintain these changes. In addition, these e-mails…2 votes -
Enhancing Alma with ERP System Integration for Streamlined Operations
Alma is a robust library management system, but its potential could be further maximized by integrating ERP (Enterprise Resource Planning) system functionalities. By incorporating ERP features, Alma could streamline financial management, procurement, and resource allocation across library operations. This integration would not only improve efficiency but also provide a unified platform for managing budgets, tracking expenditures, and optimizing resource allocation. Additionally, an ERP system could enhance reporting capabilities, offering deeper insights into library data that could inform strategic decision-making. This approach would position Alma as a more comprehensive tool, catering to the evolving needs of modern libraries.
ERP recommendation: https://www.impactfirst.co/id/erp/software-erp
1 vote -
Mail Handling via Graph API by Microsoft
I am writing to highlight the technical advantages of using Microsoft Graph API over SMTP for our email services:
Unified Endpoint:
Graph API provides a single endpoint for accessing a wide range of Microsoft 365 services, streamlining integration and reducing complexity.Enhanced Security:
Utilizes OAuth 2.0 for authentication, offering stronger security measures compared to SMTP's basic authentication.Rich Data Access:
Access to not just emails, but also metadata, user profiles, and more, enabling comprehensive application development.Real-time Capabilities:
Supports webhooks and delta queries for real-time data updates, ensuring immediate synchronization.Simplified Development:
Consistent API with extensive documentation and SDKs, reducing…
1 vote -
Add a configuration option to make Alma send e-mails in plain text only
It should be well known among responsibly acting software vendors that HTML e-mails pose a serious risk for IT security. Anyone who sends HTML e-mails (even such containing a plain text layer) tempts recipients unaware of this risk to do take potentially risky actions in their e-mail client. We as a library should be able to opt-out from tempting our users to do potentially risky things so please add a configuration option to make Alma send plain text only messages.
18 votes -
Optimizing Library Operations Through Alma API Integration
Hello everyone,
I am seeking expert guidance on effectively harnessing Alma’s API capabilities to elevate our library’s operational efficiency. As we strive to streamline processes and strengthen system integration, including mulesoft API integration. I am eager to learn from the collective wisdom of this community.
I am particularly interested in insights on:
Best Practices: Proven methods for seamlessly integrating Alma APIs with external systems to ensure optimal data flow and mitigate potential challenges.
Overcoming Obstacles: Common hurdles encountered during Alma API integration and successful strategies for resolution.
Performance Enhancement: Techniques and tools for optimizing Alma API performance, especially when…3 votes -
Improve access to Developer Network by consortial staff
Currently the Developer Network requires unique email addresses for accounts, even across different institutions. This prevents our central office staff from having one developer network account, with their real email address, to use across our consortium.
Instead, they're forced to create multiple accounts, with bogus email addresses or no email addresses at all, in order to have access to multiple institutions Developer Network accounts. And, as we understand it, bogus or missing email addresses mean that the Multi Factor Authentication can not be used.
We believe a single account for an individual, tied to a single real email address, should…
4 votes -
Mail Handling Integration - In September 2025 Microsoft Exchange Online to retire Basic auth for Client Submission (SMTP AUTH)
Are there plans for supporting more modern authentication methods (e.g., oauth2)?
I imagine that there are quite a few customers that use Microsoft Exchange (office365) as a relay and will be affected by the retirement of basic auth for Client submission. What, if any, are your plans for handling this?
Thank you
Related article:
4 votes -
Retrieve associated collections by MMS ID
In the Alma API there should be an end point to input an mms id number and return all collection ids associated with that ID number.
This functionality already exists for e-collections (GET /almaws/v1/bibs/{mms_id}/e-collections) but no such functionality exists for regular collections.
1 vote -
schedule job api support "Reload & Delete"
Currently there are api interface to trigger running of schedule job. However there are situation where OAI repositories does not support tracking deleted items, therefore, the current solution is to update import profile harvest start date and run "Delete & Reload" manually from time to time. We would like to suggest to include support to update import profile parameter and running of "Delete & Reload" job.
0 votes -
Add API support for licenses with type Negotiation
We are trying to update the license terms on our licenses in the Network Zone. However, when trying to update a license with type Negotiation, the API returns an error:
"errorCode": "69002",
"errorMessage": "Updating negotiations by API is currently not supported",
"trackingId": "E01-0703094132-MPLRX-AWAE786493119"Please add support for updating Negotiation licenses through the API.
34 votes -
Reverse Bursar Export and Restore State of Items and Fines/Fees
Have the ability to immediately reverse a Bursar Export and restore the state of items and fines/fees. This would be a good quick thing to have in case you have made an error.
3 votes -
Add ability to customize the data exported by Bursar integration profile using System = Other
When creating an integration profile of type Bursar which uses a ‘System’ setting of ‘Other’ there should be more granular control over what data is included in the export.
If a ‘System’ setting of ‘Other’ is selected, then a 'Data' tab should be made available which will allow you to select via checkbox what fines/fees and user data is included in the exported file. The data available should at minimum include, but not necessarily be limited to, what is accessible via API.
15 votes -
Add export start/effective date to Bursar integration profile configuration settings
When creating a new Bursar integration profile, we want to be able to limit the transactions being exported to only those generated after a specific date. This is in addition to ‘Time before export (days)’ setting. We've never used an integration profile to export fines/fees to be transferred to our bursar office and have instead used the API. We're now stuck in a situation where we can't switch to using an integration profile because without a start/effective date there's no way to prevent the exported files from creating double billing of transactions that have already been transferred to our bursar…
15 votes -
Address issue with incorrect fiscal period in Update PO Line API when accrual mode configured
When activating ledgers for the current and upcoming fiscal years in Alma during API creation, there is an issue where the selected ledger (FY cycle) consistently defaults to the future financial year instead of the current one. As a consequence, the team is compelled to manually adjust the funds to ensure accurate registration against the correct fiscal year. This manual intervention hinders the full automation of the API for DDA activation, and continuous orders renewals via API, thus requiring reliance on manual checks and interventions.
We experience this with Rialto/Alma API integration and EBSCOnet/Alma API integration.For Rialto we utilize…
3 votes -
Add the ability for users to view current AFN checkout information via the My Account feature on self-check machines.
Currently, when a user accesses My Account via a self-check machine, they are unable to view any information pertaining to their active AFN checkouts. We opened a support case with Ex Libris, reporting these findings and providing details provided by our self-check vendor (mkSolutions), and their final decision was that this functionality is not currently supported, requiring an enhancement request.
Enhancement Request: Add the ability for users to view current AFN checkout information via the My Account feature on self-check machines.
3 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 –…
24 votes -
provide means to access our Alma and Primo data via our own analytics tools
we need to analyse and combine our data with data from other systems that are in use at the university. extracting data from Alma in a meaningful way is way too cumbersome to be useful. all methods that I am aware of are based on an Analytics report, and have restrictions on numbers of rows that can be exported at one time. E.g. we would need to compare data from our reading list system (which we can access using an ODBC connector despite the system being SaaS) with print and electronic holdings in Alma and their usage. I do not…
3 votes -
API allow quantity for pricing in POL creation
We use the adquisitions API to duplicate POLs. When we are creating a new POLs based on a existing ones.
We get the original POLs json and we make some changes on it to send it again in order to create a new one.
If the POL has more than one items to be ordered (quanity for pricing field), the api ignore it and put always a 1.
The problem is that the Alma make some calculations with the amount field and the fun percentage changes, so the POL amount increases and is not the correct amount.In order to…
3 votes
- Don't see your idea?