Skip to content

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

107 results found

  1. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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 –…

    23 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Alma “scan-in” API: Marc21 field 852 - call number prefix and suffix

    We are using the Alma “scan-in” API
    /almaws/v1/items?itembarcode={itembarcode}
    which redirects to
    /almaws/v1/bibs/{mmsid}/holdings/{holdingid}/items/{item_pid}
    to print book labels.

    Some sublibraries also use call number prefixes or suffixes in some cases.

    Please see the following example record:
    - Marc21 field 852 in the Holding record
    - XML output

    (1) Example: Call number with prefix 852 $$k
    852 8_ |b XHOG |c XGRY |h G-1234567 |k Präfix

    XML output:
    item/holdingdata/permanentcallnumber: Präfix G-1234567
    item/holding
    data/callnumber: Präfix G-1234567
    item/holding
    data/accession_number: G-1234567

    item/itemdata/parsedcallnumber:
    <parsed
    callnumber>
    <call
    no/>
    <call_no>Präfix</call_no>
    <call_no>G-1234567</call_no>
    </parsed_call_number>

    (2) Example: Call number with…

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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.

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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…

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. API for terms of use

    An API to retrieve the terms of use would allow us to display borrowing rules on our website which are completely synced to our Alma configuration.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Improve z39.50 tab in ILLiad to search individual volumes of serials/monographs

    Improve z39.50 tab in ILLiad to search individual volumes of serials/monographs. Currently searching z39.50 will turn up one random volume from multi-volume set

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Allow Z39.50 and other search results to include the barcode

    Alma's APIs need to provide greater flexibility in fields searched. Too often the MMSID must be used but this is not a particularly useful ID as it is internal. It's also not particularly helpful as it does not integrate with other systems like Remote Storage management systems, Bindery, NCIP, and the like. Yet Primo displays the barcode so clearly it's not difficult to pull out of a record.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Add a function to automatically notify users when a Resource Sharing Request converted to an ILL request via ALMA API

    We implemented the ALMA API to convert Resource Sharing Request to Illiad ILL request. Currently, we can't find a way to automatically notify users when their requests being converted/transferred to Illiad. Since processing the ILL requests usually take longer than processing a regular consortium wide Resource Sharing Request, it will be very helpful to notify users automatically about this information.

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Allow MarcEdit Alma Integration to update Community Zone records (via API)

     Ex Libris has allowed us to edit Community Zone records, except 022 field.  Currently, we can only open the records in the metadata editor and add a MARC field one at a time.  Using MarcEdit Alma Integration to update a record one at a time results in an error, because the Alma API documentation states that “…updating a linked Community Zone record is currently not supported.”
    
      I am requesting Ex Libris to allow updating Community Zone records via MarcEdit Alma Integration., so that we can update records one at a time, instead of adding MARC fields to a record one
    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Allow more information to be included in the Webhook Failure letter

    As things stand, the Webhook Failure letter cannot be customised to include a reason for the failure, forcing recipients to trawl through the opaque and confusing logs to work it out. Allowing administrators to add more information to this letter (such as information from the webhook response body) would simplify the process of dealing with webhook issues.

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base