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.
61 results found
-
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 -
Send ebook access models through the autoholdings integration profile
It would be very helpful if vendors could send ebook access models (1U, 3U, UA), and Exlibris could load them into the portfolio information, as part of the autoholdings integration profile, especially for Ebook Central. Updating this manually is difficult, especially given that ebooks are added to this collection continuously through many different feeds and not all of them have PO lines where access models can be added. We want to take full advantage of this great new feature, and it would be great if it could be automatically managed for us.
33 votes -
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…
81 votes -
Accession number available by API
Hello,
To be able to develop several external tools (relabelling, cataloging, ...) we need to access the "Accession number" table by API (read and write).
This would probably give many other clients oportunities in developing external tools for managing physical collections.
Best regards.18 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…
24 votes -
ALMA Cloud apps; can we enable this feature role-based
with lots of interest we have followed the Igelu presentations about ALMA Cloud Apps.
For now we have not enabled this feature though we would like to use it.
We do not want all our ALMA users to be able to use all these apps.
It looks as now the only choice is 'enable or disable'.Is it possible to add Alma Cloud apps role based?
For example for our users who have a General Administrator role or to the meta data experts in our library?Kind regards, Hiltje
Leiden University Library, The Netherlands48 votesDear community,
Thanks for raising this idea.
I would like to better understand the requirement:
Do you want to limit users to be able to install/use only cloud apps that they have the proper roles for operating? Meaning - users will not be able to install/use a cloud app they do not have the required roles to operate it.
or
Do you want to allow the use of cloud apps only for users that you specifically choose (by giving them a dedicated role for that)? Meaning - users will be able to install/use cloud apps only if they were given a dedicated role for that (for example, a new role "CLOUD_APP_OPERATOR")?
or
Both?
or
Other?
I would be happy to hear your thoughts and clarifications.
Thanks,
Uri Beladev
Platform Product Management team
-
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 -
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…
30 votes -
Merge Patron Accounts API
Add an API endpoint that provides a programatic interface to the merging patron accounts functionality.
34 votes -
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 -
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 -
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).
79 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 -
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 -
Alma to support Hold Information in SIP2 checkin reponse
We have a sort assistant (RFID equipment) that displays the next step/destination of an item on screen. It also generates a hold slip (with the hold patron name if there's a request for that item) or a transit slip (if it needs to be sent to another library).
However the hold information is not provided in the SIP2 checkin response which means having to scan in the item again in Alma to get this information.Could the following SIP2 extension fields be added to resolve this issue:
CY - Hold Patron Id
DA - Hold Patron Name76 votes -
Provide access to files FTPed to third-parties
We run a daily scheduled "Publishing to OCLC" job which sends OCLC our new and changed MARC records via FTP.
From time to time, OCLC email us to let us know that some files were not processed due to errors in the MARC (typically blanks in the leader). To fix these, we need to download the problematic files, correct them, and manually upload to OCLC again.
However we don't have access to these files in Alma. (OCLC deletes them from their server when their automated process picks them up so we can't get them from there either.)
We managed to…
24 votes -
bursar integration - option to export fine/fee credits even if minimum value > 0
Currently in order for fine/fee credits to be exported in the bursar integration, the minimum value must be set to zero, which means Alma will export fines of any amount even if they are very small.
We would like to be able to set a minimum value for the fine export, but still export credits. Ideally we'd like a checkbox to tell Alma to apply the minimum value amount to credits as well as to debits. For example if we set the minimum value to $5 and check a box to include credits, Alma would export any fines over $5,…13 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 -
Browzine : Journals with multiple sources
Libraries who are using Browzine are exporting our journals holdings file using a Google Scholar XML schema. For titles that have multiple sources, Browzine will based on their own algorithm to determine one source to be made available to the users in the Browzine interface. According to Third Iron, this "choosing algorithm" is designed to pick the source that has the widest coverage. This is fine in most of the cases but if we want to override this "decision", we will need to write in to Third Iron.
Suggestion: To consider having a designated field in the portfolio record for…
12 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
- Don't see your idea?