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

1692 results found

  1. Location Priority

    We need Location Priority function in Alma-Primo too. IP, temp/remote, and alphabetical ordering options are not enough to show locations in the way we want to display them.

    37 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. Booking, transit and preview time

    We use the booking functionality in Alma for our Audio/Video-equipment. The equipment is administrated by our media production department, and is configured as a library in Alma.

    The AV-library is the only place on campus patrons can check out and return AV-items. Apart from that, the AV-library also supports delivery to a library at a different campus (Kjeller).

    • The transit time between the AV-library and Kjeller is set to 48 hours.
    • The preview time on the equipment booking is set to one hour.

    Use case:
    When scanning an item due for pick-up at Kjeller within the next 48…

    106 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. Add Access type in the portfolio information update job

    Since Ex Libris has added Access type for individual portfolio, there has to be a job to run to add access type to the portfolios in a collection. Currently, either we have to specify it in each portfolio manually, or we load a spreadsheet matching on portfolio ID. Unfortunately, as of today 1/23/2019, when loading a spreadsheet without the local coverage, e.g. only the access type, the local coverage is overwritten.

    93 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. Ability to convert from digital/electronic to physical request

    we have encountered issues when a citation for a digital/electronic request for an article/chapter is either beyond what is permitted within copyright policy or is insufficient to determine what is needed

    rather than cancel the request and have it hit the next institution on a rota, we prefer to be able to to convert the request to physical and route the entire item to the borrowing institution, much like the functionality available in ILLiad

    would it be possible for there to be an option to convert a digital/electronic request to a physical request?

    currently, we are required to close out…

    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)
  5. Improve 'Synchronize from CZ' job reports

    Sometimes, the information in the reports bears no resemblance to what’s in the CZ Updates Task List. For example, the 'portfolio linked to different bibliographic record' information isn't included in the CZ Updates Task List at all so you have to submit a SF case each time if you want to find out which portfolios were moved and which records are involved.

    It would be useful to have clickable counters in the 'Synchronize jobs from CZ’ job reports that take you through to the corresponding changes in the CZ Updates Task List.

    29 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. Ampersand symbol (&) in Repository search

    It's found that the repository searches using the ampersand (&) symbol and the word 'and' produce different results. Our request is to make the ampersand symbol and the word ‘and’ interchangeable when Alma does repository searches.

    SF case # 00646924

    66 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. Refine search and Search external resources function

    When using the "Search external resources" function under profiles including several external catalogs, we can only use refine search link on the first tab.

    It would be great if the refine search link was on all tabs rather than on the fisrt tab only.

    72 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. NZ EBSCO Link Resolver Plug-in

    Currently in the NZ, if you use the EBSCO Link Resolver Plug-in, it is applied all of the libraries using the NZ. We are not able to activate the plug-in for specific libraries in the NZ. Not all of the libraries want to use the link resolver plug-in. Also, along with being able to activate the plug-in for specific libraries, the plug-in will also need to be set up for the specific customer ID. Currently, when we have the link resolver plug-in activated in the NZ, all libraries are being filtered by all of the available EBSCO resources paid for…

    33 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. don't mark zero usage SUSHI reports as invalid

    When SUSHI harvests a report that has no usage for the selected dates, it is labeled as invalid. This is misleading. As long as all the correct headings for the report are in place, the report should be considered valid.

    54 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. Circulation count in item record

    Include a field in the item record which contains the circulation count or number of times the item has circulated.

    We want to be able to access the circulation count via API and Alma item record view.

    30 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. Use NZ records for full text links in Primo search results

    There is an issue with full text links not appearing in the Primo record when the incorrect ISSN is in the 022$y field. If the incorrect ISSN is in an IZ record, the search stops there and there is no full text link in Primo when in actuality there is full text available from the NZ. Can the NZ records be used in this case, not just end at the "bad" IZ record?
    My end goal would be that when looking for full text, the search doesn’t end with an IZ record that may or may not have the correct…

    26 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. Reopening closed POLs should re-encumber funds

    Currently re-opening a closed POL doesn’t re-encumber the funds. The workaround for this is to delete the fund, save the change, then add the fund back and save again.

    When we brought this up with Ex Libris they advised this can't be done automatically, but that they would instead add a popup message advising the funds will need to be manually re-encumbered. This was supposed to be added in December 2016 release but we noticed some time later that it didn't eventuate (SalesForce case #00436654).

    It would save a lot of time if re-opening a closed POL automatically re-encumbered the…

    41 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. ACQ: Improve PO Line Claiming job

    Please make the PO Line Claiming job more granular. Sending claim letters to all vendors without restriction of any kind is not really feasible.

    It should be possible to define own sets of PO lines (which should be claimed) by using the following criteria:
    - One time orders
    - Continuous orders: All / Serials / Standing orders
    - Vendors: All / only specific vendors
    - Acquistition types: All / only specific types (purchase, legal deposit, exchange, etc.)

    38 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. Bibliographic records editing history

    Here is an enhancement request concerning bibliographic records editing history.

    Currently, the "View Versions" can only tell the different version of a bib. record. However, this cannot tell logging history of updating/editing the bib. records, e.g. who add/remove a MARC fields/who suppressed/released the bib. record etc. This is no history tab to keep tracking the changes of a bib. record which is unlike other history tab functionality available in other Alma pages, e.g.

    • The PO Line Summary page when editing a PO line
    • The Physical Item Editor page when editing item records
    • The License Terms Details page…

    128 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. Displaying the "Requester Notes" from Purchase Requests in the list of Purchase Requests

    In the Purchase Request List you can't see the "Requester Note" for a Purchase Request. In many cases there are very helpful information for managing the Requests. So it would be great if you can see the information immediately.
    If the Note is very long, a mouse over with the text could be a solution.

    21 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. Add scheduled job which Recalculates Rota Assignment on Resource Sharing Borrowing Requests in Locate Failed Status

    We are trying to configure a more automated workflow for Resource Sharing in our consortium. We recently reconfigured our Resource Sharing settings. Our Partners' Locate Profiles were all changed from not checking availability (so we had time to manually manage queues) to "Check for availability" so that items will pass instantly through the Rota if an item is not available at a partner. Then each of the Resource Sharing Libraries modified their Library Details from cancelling requests on locate failure to not cancelling requests on locate failure, which keeps the request Active after it passes through the Rota unfilled, and…

    86 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. Field for academic year in user profile

    It would be good if there were a field in the user's profile that states the user's academic year, e.g., YEAR 1, YEAR 2, YEAR 3, etc.

    112 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. Make the email that is generated when an ILLiad resource sharing partner exports a request to a third party customizable

    Unfortunately, ILLiad's email import feature does not always import emails generated by Alma properly. This happens mainly when there is a copyright symbol in the requested item's publication date. Giving us the ability to remove the publication date field from the email generated by Alma would help us manage this issue until OCLC and Atlas Systems can find a proper fix.

    19 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. 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

    84 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. Improve po_line_remove_interested_users_job

    The polineremoveinterestedusers job allows institutions to delete Interested Users from PO lines that have closed. However, there are many times when a PO line is closed before the item has left the department; consequently, running the polineremoveinterestedusers job means that interested users may be deleted before the item becomes available. Additionally, while the job removes the Interested Users from Alma, it does not remove the information from Analytics.

    We request that:
    A. Institutions have the ability to set a delay on the job based on the date the PO line was closed.…

    44 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