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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. SIP2 over https

    SIP2 further development: To provide ability to develop more versatile and agile self-service concepts and processes for the staff, it would be useful to take into use ‘SIP2 over HTTPS’ in Alma. The basic message between library automation and Alma would still be in accordance with the standard 3M/NISO, but message pairs would be encapsulated in XML.

    http://biblstandard.dk/rfid/dk/rfid_sip2_over_https.htm

    160 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. 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…

    72 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. 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).

    64 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. 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 Name

    51 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Proxy for Print Daemon

    We are grateful that there is a print daemon. Since our network does not allow any application to access the Internet, version 1.2 will not run without affecting the secured network configuration.

    The improvement I request is to implement a network configuration setting to configure the proxy settings the way as it works in Browsers.

    Kind regards
    Urs Wider

    34 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. 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.)

    33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. 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…

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. 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.

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. 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…

    18 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. SRU/SRW: Increase the 10,000 record retrieval limit

    The usefulness of the SRU service is reduced substantially by the 10,000 record limit.

    If removing the limit is not an option, it would still help a lot if the limit could be increased to, say, 100,000.

    My use case is that I'm using the SRU service in combination with the Bibs API to do batch processing of catalog records.

    17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. 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…

    17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. BIBFRAME support for UNIMARC

    Currently, Alma can expose bib records in Linked Data in BIBFRAME format, but for MARC21 records only. I ask to develop the support for UNIMARC too, in order to expose UNIMARC records in BIBFRAME format through APIs, Publishing and the Alma Resource management UI.

    17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. API conf/sets - Always add member/@link

    Currently not all calls to conf/sets will return member-elements with links. This will make a call to e. g. electronic portfolios close to useless, as there is no API-call that can be done with the portfolio's ID only.

    Ceterum censeo I don't think that this is an enhancement, but Case 00874282 was not interpreted as this being a bug.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. 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.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. API "Authenticate or refresh user" - Working for all user account types, not only for internal user accounts

    API "Authenticate or refresh user" - Working for all user account types, not only for internal user accounts

    Now the "Authenticate or refresh user" works only for internal users where Alma is the identity provider.
    It would make things a lot easier in many applications around alma if it would also work for external user.
    Like:
    Internal user -> no change
    External user ->
    * Take the ID in the URL als ID in the external IDM and the passwort like in case of internal user.
    * Check ID and password against the external IDM, just as in case of…

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
← Previous 1 3 4
  • Don't see your idea?

Feedback and Knowledge Base