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.
68 results found
-
Empty User Roles via API
We would like to be able to empty all user roles using an API call. Currently, User_Roles is the only segment that keeps untouched when the API call object does not contain any roles. This makes it necessary to keep at least one role as a parameter and it makes no sense from the API usability as it actually always returns the full user objets including empty roles arrays when we delete all roles from Alma end-point.
135 votes -
Alma to DOCLINE OAI-PMH Integration
Integration for automated harvesting of eJournal and pJournal holdings from Alma to Docline (National Library of Medicine's automated interlibrary loan (ILL) request routing and referral system).
82 votes -
Synchronizing XSL templates with external systems
When customizing XSL letter templates, it would be helpful to be able to import/export these to/from Alma. This could be done for example by webDAV. This should make it possible to use an external version control system, like git. The templates are many and complex, and version control would be useful for managing revisions. This would also enable syncing to templates between production and sandbox environments.
80 votesIn order to support this, RESTful APIs to manage the XSL templates would be added to our set of APIs for configuration related entities
-
NCIP request security
Currently a valid NCIP request from anywhere can retrieve information about a given library's patrons. In order to exploit this, the attacker would need to know server address, institution code, code of the profile for ILL, all of the correct metadata, and the correct message type/formatting. It's not trivial to gather up all that information for a given institution, but much of the information is publicly available (e.g. NCIP message formatting is a public standard), and none of it is generally treated as a secret.
Given the continuously evolving state of library systems security, it would be good to prevent…
79 votes -
Improve Shelf Report functionality and responsiveness
Alma’s “Shelf Report” tool is a cumbersome, involved “inventory” process that requires users to populate a spreadsheet with barcode values, feed it to Alma, and then track down and manually identify any items that come back as an error (without Alma providing a timely or clear explanation for where a problem item might have been found if it was detected, or not detected). We’re aware of Dean Lingley’s API for “shelf inventory” and the WRLC “AlmaInventory” tool that attempt to cover some of these gaps, but neither of these replicate the same mass-scan-immediate-feedback-fix-it-and-move-on utility (without involving spreadsheets, macros, etc.) that…
62 votes -
Allow part payments to be sent from Alma to WPM for online payments
Allow a user to choose the sum they wish to pay when making an online payment via WPM. At the moment it is only possible to pay the total fine/fees owed, no option is given to enter and pay a lesser amount.
While WPM will accept whatever amount is sent from Alma, and Alma will handle whatever payment is sent from WPM back to Alma (closing fees as possible, and partially closing fees if the paid amount does not exactly match the owed amount), Alma can only send WPM one payment element with the total amount the user owes (as…
55 votes -
Allow request-type webhooks to be triggered only under certain conditions
We would like the ability to configure request webhooks such that they are triggered only when certain conditions are met. Request webhooks for patron physical item requests include the user’s primary ID and the title they have requested. This type of circulation information should in most circumstances stay within the library and not be shared with third parties. But it may be necessary to enable a third-party integration in order to provide needed services, such as a smart locker delivery service. Currently, request-type webhooks are triggered by any request in Alma, regardless of request type or destination. We would like…
50 votes -
The "maximum renewal date" (max_renew_date) should be part of the fields that are provided by API
The max-renew_date is viewable in Primo, but if you use another Discovery it can't be displayed because it is not provided by API.
50 votes -
Exclude expired users from bursar integration job
Our bursar is not currently able to collect charges from users who are no longer at the university. So we want to be able to able to exclude these patrons from the reports that are sent to the bursar with bursar integration. The fact that this doesn’t exist now has prevented us from implementing integration.
We would like this functionality to be an additional filter in the bursar integration settings that would exclude users whose expiration date is in the past. If it could specify an actual or relative date, this would be an additional improvement.45 votes -
Warn before regenerating the SFTP Service private key
There is a «Regenerate private key» button under Alma configuration » General » S/FTP definitions.
This button is too efficient. This idea is to make the button a little less efficient, but in doing so make it safer.
Clicking the «Regenerate private key» button immediately regenerates the private key for the Ex Libris Secure FTP Service. In the process it invalidates any previously generated private key and breaks all integrations with the SFTP Service. More so, the button in Alma (Premium) Sandbox does the same as in Alma Production, including breaking all production integrations.
All it can take is one…
35 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 -
Merge Patron Accounts API
Add an API endpoint that provides a programatic interface to the merging patron accounts functionality.
34 votes -
Update Resource-sharing request through the ALMA API
Currently with the API, the only update option possible is shipping a resource sharing request. We request the option to perform other updates, e.g. change the status.
(Updating the resource sharing request through the corresponding user-request does not work.)31 votes -
API for Bibliographic record versions
Currently, only the latest version of a Bib record is available from the Bibs API. There should be some way to retrieve older versions of the record.
29 votes -
Allow institutions to export and import all configurations from Alma
Ex Libris has the new policy of forcing a refresh of the sandbox for all customers on the premium sandbox twice a year. This presents a significant challenge for institutions that use the sandbox actively, because it means that before every refresh, we have to go through the largely manual process of exporting all configurations out of the sandbox so we can keep record of them. Then if we want to recreate the old configurations, we have to do this manually.
Ex Libris offers no way to export or import these configurations in bulk. This policy change reduces the value…
29 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 –…
29 votes -
More API options for Borrowing Requests
The current API:s for Borrowing Requests are limited to get a list of request for a specific user, get a specific request of a specific user or create a new request.
To be able to integrate better with other systems, in our specific case the Swedish national ILL broker system "Libris Fjärrlån", we would need to be able to update and delete requests as well.
We would also want to retrieve lists of requests without knowing the user, for example by status, by external system or other criteria.
28 votes -
Support automatic weeding of holdings in the Swedish national catalogue
The Swedish national Ex Libris user group (ElugSWE) would like Alma to integrate with the Swedish national catalogue (Libris), so that when a bibliographic record is deleted in Alma, the corresponding holding record is deleted in Libris.
(We have discussed this idea with the local Ex Libris representative and also a customer success manager, and were recommended to submit it to Idea Exchange.)
This integration exists for multiple other library systems, and it would be really welcomed if Alma could match them on this.
The integration would need to make use of Libris API:s, documented here:
https://github.com/libris/librisxl/blob/master/rest/API.md
The sections most…
27 votes -
SIS Import/Synchronise: improve invalid character handling
When the Alma SIS Import/Synchronise job runs, if any of the files contain an invalid XML character, the entire job is aborted. The consequence of this is that user data held in Alma might be out-of-date, depending on whether it has recently changed in central systems. I assume this behaviour occurs because one of the initial steps when the import runs is to parse the input files as a whole, rather than parsing each user record individually.
This Ideas Exchange ticket requests that the SIS job is improved so that the job does not abort, but instead skips over the…
24 votes -
Field creation date by changes via API
While changing a specific field in a user records via API the "creation date" should be changed only in this field and not in any other fields – which happens now – in order to be able to recognize the newest changes in a user profile.
24 votes
- Don't see your idea?