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. In Advanced Search, allow filtering OUT specific locations. For example, allow use of the filer: Physical Location "IS NOT" X.

    Many searches do not allow for an "IS NOT" operator, and in some cases it is greatly missed. For example, when trying to assemble large sets of records where you want to exclude just a few locations, or filter out a single library. Please allow for an "IS NOT" operator when doing an advanced search and filtering by location or library. I'm sure there are other search filters also missing the "IS NOT" operator. Please feel free to add more suggestions via a comment! :)

    526 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. 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…

    467 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Make all tables in Alma sortable by all their column headings

    There are lots of tables in the Alma UI that come up which can be sorted by a couple of the column heads but not others. For example in Letters Configuration, you can sort by "Letter" or "Description," but not by "Enabled," "Channel," or "Retention Period." Being able to sort by column headings is a basic function of a table.

    In the example above, it would be helpful to be able to see only those letters that are enabled, or to sort so that all the email letters are grouped together and all the SMS letters are separate from them.

    430 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Other  ·  Admin →
  4. 'Not Needed After' date should be mandatory on patron physical request form.

    It would be helpful if the 'Not Needed After' date is mandatory on the patron physical request form to improve the requesting process for Patrons when there is a high demand for physical items.

    373 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. 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…

    357 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Other  ·  Admin →
  6. 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…

    325 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. comment/note field for configurations

    A comment or note field for configurations would be incredibly helpful in general, but the current pandemic has highlighted the need for a way to easily track the reasons behind changes. This would keep the notes in the places where they'd be seen by the people working on the configurations, rather than us having to track things in a separate place.

    All of the fulfillment configuration menu would benefit from this ability when short-term or emergency changes are being made. But it would also be good in places like: Letters; DARA recommendations; and all Other Settings areas. These are places…

    320 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Other  ·  Admin →
  8. Ability to edit "subscription from date", "subscription to date", and "additional information" fields on closed invoices

    For some institutions, this data did not migrate, and for others, there are invoice operator errors that need to be fixed. This is vital to subscription management. We need this.

    315 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Add a public note field in interface record

    From time to time, a vendor interface goes down temporarily. While we follow the access issue up with the vendor, we add a public note for our students and staff indicating that the interface is temporarily down. The issue is that often we have many electronic collections with the same interface, and therefore must add a public note to each and every electronic collection that uses the affected interface, and then remove all of the notes once access is restored.

    Since all of these electronic collections link back to a single interface, it would be great if there were a…

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

    The new shortloancourtesyreminder & shortloanoverduereminder 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:

    ​shortloancourtesyreminder - 105 minutes
    short

    277 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. 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…

    275 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Add ability to prevent CDI content from appearing in Primo, by Alma Electronic Collection

    With CDI we have no control over preventing CDI content from appearing in our Primo filtered search, when we have full text holdings which matches to this content.
    In many cases this may be a good thing, in not needing to worry over making sure full text content is searchable.
    However, it is clear that there are collections in CDI with very poor data, which causes linking to fail, and also has content which we do not want at all such as Journals and Books, as we manage the title level by our Alma records.
    For example, CRL Catalog has…

    258 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Display PO-Line owner in "Manage EDI Tasks"

    I would like to suggest to add a column in the Manage EDI Tasks List for PO-Line owner. That would give the option to sort the List by PO-Line owning Library.

    259 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. "Save and dismiss" button in "Manage EDI Tasks"

    In the "Manage EDI Tasks", when using the "Update Expected Receipt Date" action, updating the date and clicking on "Save", it would be great the concerned line would automatically be removed from the list without having additionally to click on "Dismiss". A new function button like "Save and dismiss" would be helpful.

    255 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Allow suppression of items from Discovery in Primo

    I would like a check-box in the item record that would allow staff to suppress individual items from discovery in Primo. This could be used for libraries that want to use only a single discoverable "dummy" item for placing requests on physical journals in Primo as well as libraries that prefer not to have items discoverable by patrons until they are done with processing and are available on the shelves. In an ideal world, if a holdings record only had suppressed items, the holding record would also not display. Moreover, if all items on all holdings attached to a bibliographic…

    253 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Add "item policy" and "temporary location" automatically to predicted issues

    Acquisition librarians want to add automatically the "item policy" and "temporary location" to predicted issues to speed up their work and limit the number of clicks. At this moment the added value of prediction pattern functionality is being restricted by the lack of functionality (parameter setting) …
    Use case: It’s not possible to add the item policy/temporary location as a parameter to continuous pol’s. If issues are created via prediction patterns the item policy/temporary location should be indicated automatically based upon parameter settings on pol level. This would save a lot of time and additional clicks when receiving the issues. …

    254 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Make physical item sort routines stick

    For those of us working with continuing resources:

    When viewing a list of physical items, the sort routine defaults to Library/Location. The items do not appear in any particular order when the results are loaded. Often I change the sort routine to Description or Receiving Date to view the most recent serial items and order them chronologically for viewing.

    It would be nice if the sort routine "sticks" so that every time I open a list of items, the sort mechanism will stay on Description (not default back to Library/Location)

    This would be especially helpful when managing items in the…

    251 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Add functionality to better manage queue for reserves/holds

    More academic libraries are checking out high-traffic electronic items (laptops, Wi-Fi hotspots, etc.) and often have a long list of patrons with holds on these items. It would be useful if we could manage the queue for user holds/reserves more effectively. We should be able to renumber/reposition users in the queue (presently you may only bump someone up to the very top of the queue or profile a priority if users are from different user groups). We should also be able to manage the queue without having the item available; presently that is not possible. We often have 12+ users…

    247 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Delete unwished licenses

    We need the feature to delete unwished licenses. We mean delete and not display those licenses to the licenses list.

    247 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. 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…

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

Feedback and Knowledge Base