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. Ex Libris should provide the option to place a call and/or online chat with their support team

    We are disappointed with the technical support service provided by Ex Libris. We strongly believe that Ex Libris should provide customers with more effective, prompt and interactive service.

    There should be an option to call or chat online in real time with a support person who has a sound understanding of the product in question. This would be in line with all system vendors we have previously dealt with.

    We appreciate that there will be some issues that are designated as bugs or enhancements and will require more in depth investigation. However, a direct call/chat option with a properly trained…

    668 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Other  ·  Admin →
  2. Increase the 10MB email attachment limit for digitization requests

    Currently the limit for email attachments when filling digitization requests is 10MB. We would like institutions to be able to choose their own limit that suits their own institutional email policies (e.g. Otago's attachment limit on their email server is 30MB). Other institutions may wish to have a lower limit so it should be possible to set a limit that is appropriate up to a maximum value that can be supported by the Alma email infrastructure. Our staff frequently bump into the 10MB limit which leads to them cancelling digitization requests in Alma and then manually emailing the attachment to…

    452 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Fulfillment  ·  Admin →
  3. Fines in Grace Period should let users decide to calculate or not.

    According to the policy that our institution laid down, Fines in Grace Period shouldn't be calculated.

    If overdue fines count $5 a day and grace period value is 3, then patron returned an item in 4th day after due date, the patron should pay only $5.

    But in Alma, we cannot set grace period that won't calculate fines. Hope to add this function to let users decide grace period fines calculate or not and make alma more flexible.

    396 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Other  ·  Admin →
  4. Closed Library Management TOU apply to Resource Sharing Request

    Currently, the RS Lending Request item due date does not take into consideration of the library closed days as there is no "Closed Library Due Date Management" option in the Lending Resource Sharing Rule TOU. As a result, the due date may fall on a library closed date where clients are unable to return the item. I have received confirmation from ExLibris (SF354784) that this will need to be an enhancement request rather than a bug fix.

    369 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Add "Search within results" box on a set

    Hello,

    It would be very useful if we had a search box of "Search within results", on a set we created with indication rules.

    Thanks.

    337 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Add Statistics Notes to Search Indexes

    Currently Statistics Notes in item records are not among the options of search indexes in Alma. Recommend adding them. Evidently they can only be searched in Analytics now.

    312 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. Provide ability to turn off the Related Record functionality for physical items

    Provide ability to turn off Related Record functionality for physical items. I would like to be able to decide for each related field in the MARC record - 773, 774, 777, 786, 800, 810, 811, and 830 whether or not Primo will display the related record information for physical items.

    There are cases where displaying related record information to the user is more confusing then helpful. 830 series fields, for example, will display "related" records that may not relate at all to a users search, especially if the series is general like: "Brill's studies in intellectual history." I would like…

    307 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. A borrowing library should be notified when a lending request is put on a waiting list

    Scenario:
    A library receives a resource sharing request (lending request), and the borrowing library asks to be put on waiting list if the wanted item is on loan. When the request is put on waiting list, the borrowing library should be automatically notified. This could for intance be by change of status on the Borrowing request to "In queue".

    273 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Add generic physical material types to the current table

    My libraries circulate various pieces of equipment from microphones, to musical instruments, to 3D printers, to lockers, and the current physical material type table does not suffice without adding a slew of item policies or location codes, which is messy and makes the resulting analytics more painful than it should be.

    Ex Libris support states that "The [physical material type] codes cannot be changed, because Development needs them for statistics across libraries." However individual libraries will have items that they need to distinguish between either for fulfillment rule purposes or our own statistics.

    I would like there to be about…

    262 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Include the item barcode as part of the data published from Alma to Primo in the AVA field to improve item search in Primo

    Request for Alma item barcode be included in the data that is published to Primo as part of the Alma publishing functionality to enable barcode searchability in the Primo keyword search. We have discovered that items migrated from our previous ILS do contain the item barcode(s) in the MARC 945 $$i and is written to the search:general field of the PNX. As such, those items are keyword searchable via their barcode in Primo. However, for items created in Alma, the item barcode is not written to the bib record and is therefore not searchable in Primo. Adding the item barcode…

    259 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Other  ·  Admin →
  11. Hold Shelf policy for RS items

    When using Lender Due date for RS items (Fulfillment > General > Other Settings > ignore_lender_due_date = false) the date for Pick up from shelf is the same as the Due date. This is, according to ExLibris, working as intended, but we have a few issues with the workflow.

    This makes the workflow more manual and difficult than needed, given that we have to manually check RS items that is not getting picked up by patron within a couple of weeks. Having the RS items on Hold shelf for up to 4-6 weeks is poor use of time - for…

    243 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Short Term Loans - Courtesy and Overdue Notices

    The new short_loan_courtesy_reminder & short_loan_overdue_reminder cannot be configured for multiple locations. For institutions with several hourly loan locations (for example Boston College maintains 2 and 3 hour loan periods for Course Reserves and a 4 hour loan period for some technology items) this dictates that the reminder notice has to be set based on the location with the shortest loan period. The overdue notice must be timed to make sense for for the longest loan period.

    In our test configuration we used the following time parameters:

    ​short_loan_courtesy_reminder - 105 minutes
    short_loan_overdue_reminder - 241 minutes

    However, this creates a situation whereby…

    234 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Fulfillment  ·  Admin →
  13. Add parameters to control anonymization of requests, resource sharing and fines

    We'd want to be able to control the anonymisation of requests, resource sharing requests and fines and fees in a similar way to loans. In particular we'd like to be able to set a parameter for days since user expiry and since the request or fine was complete.

    This would allow us to create a clear policy for anonymising and purging data in Alma so that all data was treated in the same way i.e. could say that all data was anonymised or purged X number of years after user left. It would also allow us to be confident that…

    221 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Other  ·  Admin →
  14. Significant Improvements to the 'Browse Shelf List' Function Needed

    The 'Browse Shelf List" function is essential for catalogers in our library and is extremely clunky and time-consuming to use. Proposing any (hopefully all) of the following changes:

    1. Ability to view more results surrounding the exact search request.
    Said in a different way, the ability to view the result in the middle of the results page, so as to be able to see a few of the results both before and after. This makes call number adjustment significantly easier, instead of always needing to click a back button and remember what the call number were on the page before.

    220 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Extend the "interested users" functionality

    Acquisition librarians want to extend the current "interested users" functionality in order to serve the end user in a better and faster way. The current "interested users" functionality is not sufficient enough, to become useful and really benefit from this functionality we would like to extend it with:
    • The ability to sort the interested user list.
    Use case: some users (e.g. academic staff) have priority and should get the issue first!
    • Make it possible to create hold requests on these items regardless of the existing fulfillment policy:
    Use case: some libraries don't allow requests for available items, but…

    216 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Better management of serial prediction when publication frequency changes

    Sometimes providers change a journal’s publication frequency throughout the year. So, the prediction’s pattern selected / elaborated at the beginning of the year doesn’t work anymore in Alma. One part of predictions (date of receipt) will be ok until the change but all other predicted items will be false. Now, we can revise the prediction during the year but we must erase the items already received. We can also leave the prediction defined at the beginning of the year and edit manually the false items from the time of the prediction change.

    It would save a lot of time if…

    203 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. In Process Items_Move items in batches to the next work order

    In the page of “Manage In Process Items”, we would propose
    1) Adjust the number of each page so that more items can display on the page. That would be the maximum the staff can tick “Done” at one time.

    2) Given above, ideally we'd want to move a pack of items by jobs to the next work order.

    3) Sort out “Barcode”

    198 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Improve usability of 'Automatically Print Slip' in Resource Sharing

    When receiving Resource Sharing Borrowing items, the 'Automatically Print Slip' option is only remembered for the current session, which leaves this vital function open to error.

    This could be improved in one of the following ways (in order of preference):

    Option 1: Provide a configuration option in one of the code tables to set the default (this would also be desireable for all similar functions elsewhere, such as in RS Lending).

    Option 2: Make the last selected option persist across sessions so our staff can set it once and not have to remember to set it every time.

    Option 3:…

    195 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Copy and paste multiple MARC fields into the metadata editor

    We would like to be able to copy multiple lines from MARC records and paste them into the metadata editor so that multiple MARC fields are pasted into the record in one action. This would help us enormously with our workflow of importing MARC authority records from LibrariesAustralia into Alma.

    For us, this is necessary because the LibrariesAustralia headings are not in the community zone and are unlikely to ever be included there and Alma does not allow for Z39.50 import of authority headings.

    We have this functionality of copying and pasting multiple fields in the LibrariesAustralia Cataloguing Client and…

    192 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. Blocking borrowing requests on books published within the last year

    With an active automatic rota for books, borrowing requests sent from Primo to Alma are automatically sent to partner. This applies for books published within the last year as well. Before we activated the autoROTA, we would usually change most of these borrowing requests into purchase requests and place the patron on a waiting list.
    New books requested by a patron are often items we want to purchase ourselves, and not spend money on borrowing from our partners in addition. With the autoRota there is no way for us to block these borrowing requests from being sent.

    We would like…

    188 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
← Previous 1 3 4 5 89 90
  • Don't see your idea?

Feedback and Knowledge Base