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.

How can we improve Alma?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Add API call to fetch all holdings and items associated with one bib record (MMSid)

    It would be great to have a single API call to fetch all holdings and items related to an MMS id, which would return all this data in one big XML file. The way it works now, if you want to get, say, all of the barcodes for all items associated with a single MMS id, you have to do an api call for every holding record. So if you have a bib that has one item in 6 different locations, you have to do 6 API calls.

    64 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
    • 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.

      48 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
      • faster receipt printing

        Don't use email for all print events. It's too slow for receipts and transit slips at staffed service desks. (Complex anti-spam engines and office365 hosted email typically adds up to a minute to email transit time.)

        Instead, write some local software to act as a print client that talks back to the cloud. That way, you can bridge local networked printers across large sites, back to the cloud in a more timely fashion.

        28 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
        • 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.

          22 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)
            You have left! (?) (thinking…)
          • Patron Self Registration

            Make Patron Self Registration possible via Primo. This feature would need to be configurable by libraries and able to be turned off altogether by the library. Configuration options could include: what data elements are required, whether new accounts need to be reviewed before they are active.

            20 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)
              You have left! (?) (thinking…)
            • Add more options for ILL integration

              Adding ILLiad integration to Alma was welcome but also brings more issues into the system. For example - patrons are shown in their account via Primo that ILL loaned items are not renewable. They are but not via Alma. A customizable message for the Resources sharing library that would display in "My Account" saying "Renewable via ILLiad" would be welcome. We have configured ILLiad to send courtesy notices. Now that we have integrated with Alma patrons get two courtesy and "due today" letters because Alma cannot turn off letters for specific locations. The ability to turn off those two letter…

              20 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)
                You have left! (?) (thinking…)
              • API for managing scheduled jobs configured in integration profiles

                The enhancement described and completed in the idea http://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/9592206-api-to-interact-with-alma-job-scheduler is fine as far as it goes, but the current functionality does not allow us to interact with jobs launched automatically by Alma on a periodic basis; it only supports jobs launched manually by a user.

                Our use case: we have scheduled periodic uploads of SIS student data
                configured in a SIS integration profile. We would like to get a formatted list of rejected users, errors, etc. that happened during the automatic load available as a file on our processing server, so that the list can be parsed by a script…

                20 votes
                Vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)
                  You have left! (?) (thinking…)
                • Bursar Export: Option to not close out fines/fees upon eport

                  It would be useful if the bursar export job to export fines and fees had an option to keep fines and fees active in the Alma user record upon export. Some libraries want to keep fines and fees active even as fines and fees owed are communicated to a bursar's office. Because it's possible through the fine/fee payment API for a custom solution to be developed to communicate fine/fee payment back to Alma, some libraries would choose to use a bursar export integration to export fines and then develop a custom solution to send payment information back to Alma to…

                  18 votes
                  Vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)
                    You have left! (?) (thinking…)
                  • 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.

                    15 votes
                    Vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)
                      You have left! (?) (thinking…)
                    • Purchase Requests API

                      A Purchase Request API is needed. This would allow the library to seamlessly integrate with internal systems.

                      From Francois Renaville: "We asked for this in May 2016 and were told in July 2016 (case 00222634 - API for Purchase Requests?) 'that API for purchase requests is on the Alma road map for 2017. Currently, there is no release date.' No news since then."

                      15 votes
                      Vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        Signed in as (Sign out)
                        You have left! (?) (thinking…)
                      • 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.

                        9 votes
                        Vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)
                          You have left! (?) (thinking…)
                        • 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.

                          9 votes
                          Vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            Signed in as (Sign out)
                            You have left! (?) (thinking…)
                          • API query to retrieve only those user accounts where active fines/fees exist

                            We want to export user fine/fee data to our SIS (PeopleSoft) while retaining the ability to manage patron fine/fees in Alma. The Alma bursar export does not meet our needs because it closes out the fine/fees in Alma. The user API only allows for checking accounts individually to determine whether a fine/fee exists. The 'users' query does not provide a filter for whether a fine/fee is on the retrieved user's account.

                            9 votes
                            Vote
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              Signed in as (Sign out)
                              You have left! (?) (thinking…)
                            • Add additional error code to Renew loan API when an item has been renewed but the due date hasn't changed

                              The Users / Renew Loan API (https://developers.exlibrisgroup.com/alma/apis/users/POST/gwPcGly021r0XQMGAttqcPPFoLNxBoEZNUiGwQUr+MuAI+35dTBcVUmYayAq/vUq/0aa8d36f-53d6-48ff-8996-485b90b103e4) currently only returns two errors - "Loan ID XXX does not exist." or "Cannot renew loan: Loan ID XXX." This API should return an additional status of "renewed, but due date didn't change" when that applies to the item in question. This would allow our locally developed catalog, which uses the Alma APIs for requesting items, to provide more complete information on why certain requests fail.

                              8 votes
                              Vote
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                Signed in as (Sign out)
                                You have left! (?) (thinking…)
                              • Allow patrons to request extension of hold shelf period in 'my Library account' list of requests in Primo

                                Alma-Primo integration as requires My account functionality to Requests from Alma.

                                For Patron physical item requests which have placed on the hold shelf it would be very useful to add the ability for Patrons to Request an extension of the hold shelf expiry. This should only appear if there is no outstanding queue of requests against the item.
                                This functionality would save many queries from students who ask the Library helpdesk for an extension. We are often able to extend the hold shelf period where there are no further requests but ti would be nice to automate the requesting/task handling…

                                8 votes
                                Vote
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  Signed in as (Sign out)
                                  You have left! (?) (thinking…)
                                • 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.

                                  7 votes
                                  Vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    Signed in as (Sign out)
                                    You have left! (?) (thinking…)
                                  • Please make the MARC bib. 245 subfield p from the bibliographic record available.

                                    The MARC 245 subfield p from the bibliographic record is not exposed to Primo. This means that the data in the b245p is not available to display to users in the My Account section of Primo, to letters sent to users, as part of the requesting process and on pull slips for items. This becomes important when the items have 245a data that is the same. For example, when a video game has the same name with more info in the 245p like the ones below.
                                    b245a b245p
                                    Angry birds. Star Wars
                                    Angry birds. Trilogy
                                    Assassin's creed. Brotherhood
                                    Assassin's creed.…

                                    7 votes
                                    Vote
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      Signed in as (Sign out)
                                      You have left! (?) (thinking…)
                                    • Make modification date of user account available in the User API (v2)

                                      In the earlier SOAP-based version of the Alma User API, the last modification date of a user account was an available field. However, in the current REST-based API, that field is no longer available.

                                      This piece of information is very important to us when we synchronize Alma data to ILLiad via our custom ILLiad login script. That allows to us update ILLiad as needed and insert an accurate modification date into a user's ILLiad account.

                                      6 votes
                                      Vote
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        Signed in as (Sign out)
                                        You have left! (?) (thinking…)
                                      • 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…

                                        6 votes
                                        Vote
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          Signed in as (Sign out)
                                          You have left! (?) (thinking…)
                                        • Allow patron load integration using v2 to implement override so internal elements are preserved

                                          Under General Administration when setting up a user record integration using v2 of the user.xsd, there appears to be some missing functionality to bring it in line with the REST user APIs.

                                          The suggestion is to add additional options to the synchronize method so that under Synchronization type where it currently only has 'Swap All' as the only radio button, you could toggle between this and 'Override' as per the User APIs. This would allow internal notes and other internal attributes to be preserved.

                                          It might also be useful to add the list of fields via selection that the Override…

                                          5 votes
                                          Vote
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            Signed in as (Sign out)
                                            You have left! (?) (thinking…)
                                          ← Previous 1
                                          • Don't see your idea?

                                          Feedback and Knowledge Base