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

133 results found

  1. Create a Set of Inventory from a Title Set

    It would be very useful to be able to take a set of titles, and convert it into a set of inventory attached to those titles. Specifically, I would like to create a Portfolio set from a set of Electronic Titles. I have regular need to move groups of portfolios from one local e-collection to another. I have only a list of ISBNs to start with, which I use to create an itemized Electronic Titles set. However, moving portfolios requires a Portfolio set, which can only be created with Portfolio IDs. It is very cumbersome to arrive at the appropriate…

    53 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. Authority linking issue with bibliographic field 240

    We'd request that when Alma links up bib field 240 with a uniform title entered in authority record, it should take into account of bibliographic contents in field 240 PLUS field 100 ALTOGETHER, and link these combined contents with uniform titles entered in authority records.

    Currently, it links up the uniform title in field 240 only with authority record. So, those generic uniform titles e.g. Works, Poetry, etc. will be ambiguous, and do not have proper linking with their authority records established with author's name.

    Details, please refer to Salesforce case # 823121

    31 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. Option to export Alma search results and sets as CSV

    Right now Alma search results and sets can only be exported in XLSX-format. For performance (and other) reasons it would be good to have the option to export in CSV format.

    (Publishing this as an enhancement request was suggested by Ex Libris in public Salesforce case #00825531)

    27 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. Make approved Purchase requests searchable in Primo

    By default, Purchase Requests are suppressed from search and discovery in Primo, whatever their status (In review, Approved, Rejected).
    We would like the library to have the possibility to automatically unsuppress Purchase Requests and to make them searchable once they have been Approved.

    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)
  5. Add the NOT Boolean operator to the Advanced Search in Alma

    Advanced Search in Alma contains currently only AND and OR Boolean operators - it would be very useful to have the NOT operator included, so that we can exclude particular records from Logical Sets, rather than creating 2 Logical sets and then combining them with NOT, resulting always in an Itemized set.

    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)
  6. New role for Manage Import Profiles

    Currently users must have a Cat Admin role or Gen Sys Admin role to be able to Manage Import Profiles (change/add profiles). This also gives them access to the Configuration area of Alma. There should be a role to permit users to Manage Import Profiles that does NOT also give them access to the Alma configuration area. Access to the Alma configuration menu should be separate from the ability to Manage Import Profiles.

    173 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. Alma User Role for Editing/Deleting only Quick-Cataloged Records

    Scenario:
    Library staff frequently need to create records for resources using the Quick Cataloging feature. Often, those records need to be edited after creation, due to mismatching resource types, updated information, operator input errors, etc. Most of the staff using the Quick Cataloging feature are not trained as catalogers, and do not have cataloging roles in Alma.

    Problem:
    Quick-Cataloged records are not editable by staff without cataloging roles in Alma - who are frequently the creators/managers of these records. This has led to several different workarounds at various institutions:

    Some institutions have given their non-cataloging staff full cataloging permissions to…

    65 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. Multiple Quick-Cataloging Templates

    Scenario:
    There are multiple workflows and purposes for which the Quick Cataloging interface is used. For example, in course reserves, staff frequently need to create records for different resource formats beyond book and article. Staff at the circulation desks need to create records any time an item brought to the desk is not found in Alma, and these resources can take any form - from sound recordings on CD to equipment like laptop chargers.

    Problem:
    Not all of these materials fit the current “book” and “article” templates provided for Quick Cataloging. To enable efficient use of the Quick Cataloging feature,…

    159 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. Display the date a work order is created

    When a work order is created to put an item in process internally ("Technical Services (CAMS)" or "Show to supervisor" or "Preservation") it would be helpful to have Alma display the date this status change happened.

    It could be in the "item history", and/or the "In process" display, and /or in the "list of items." Currently, the receipt date is the last date displayed in these locations, which does not help with locating an in-process item.

    88 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. Use of parentheses in advanced search

    Currently advanced search does not allow the use of parentheses. We'd like to suggest the capability of using parentheses in doing some complicated search logic. This can shorten the search query a lot. Currently, we have to repeat the search queries, and apply a combination of AND/OR search logic. The attachment explains the situation with a screen shot of current search logic.

    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)
  11. Show orders and requests in repository search regardless of role

    Every staff member should be able to see if there are orders or requests for a title regardless of their roles.
    It's important e.g. for staff at info/circulations desks to see why a title without items is found - as well as for receiving operators to see if there are any patron physical item requests...

    Still, of course, one should only be able to edit orders or requests with the respective privilege.

    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)
  12. 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

    62 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. Analyse and normalise special characters and diacritics in Alma records

    In order to enable correct and consistent automatic linking between Bib. headings and authority records, Alma's treatment of diacritics needs to be normalised, and made configurable according to the Authority file being used. In addition there are special characters in use (such as quotation marks), that have more than a single graphic representation that should be normalised in order to prevent discrepancies in Almas' match and link mechanisms.
    SFC#00533813, SFC#00375370 relate to the issue.

    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)

    Dear community,

    We are sorry to inform you that we have found an issue with this development, and as we want to be sure all features are high quality, we are delaying its release until we can test and make sure it is up to standard.

    We will update when we have a final release date.

    Regards,

    Alma team

  14. Add a lock feature to prevent selected items from being withdrawn when running a job

    I envisage this as a simple checkbox within an item's record which prevents that item from being accidentally withdrawn. (A parallel exists in many photo editing software packages.)

    I also envisage this as being a property which could be engaged or disengaged on a set of items via a job.

    When running a withdrawal job, any such "locked" items which were not withdrawn should be listed individually in the job report so that the user can determine whether this was correct (in case an item has been accidentally locked by a user, for example).

    A use case is as follows:

    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)
  15. 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.

    73 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. Task list customization

    Currently, the task list is automatically configured based on user roles. However, there are many features assigned to a role in Alma that a user may not actually deal with. For example, as electronic resources manager, I do not need to see print order lines to claim for print titles. This is particularly an issue because other departments do not always use the task list in their workflow, so mine can become cluttered with their content. We would like additional customization to be available within the task list, so that we only see relevant tasks.

    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)
  17. Fix Call Number Sorting for certain classifications

    Certain call number classifications that don't follow the typical format (LC class code, class number, Cutter code, title code, pub date) aren't sorting correctly in Alma's Browse Shelf Listing or Primo's call number browse.

    One example is from a classification concerned with books about Civil War troop regiments:

    E
    577.5
    24th
    .T55
    2010

    Which should typically sort like this:
    E577.5 1st
    E577.5 2nd
    E577.5 3rd
    E577.5 10th
    E577.5 24th
    etc.

    However, it seems as though the call number normalization isn't set for these specialized classifications and they end up sorting incorrectly, like this:

    E577.5 1st. P48 2004
    E577.5 10th .W35…

    45 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. A way to set the Scan-in-Items drop-down-menu Status to our specific workflows

    In Cataloging when we scan in item barcodes to send a work order to shelf preparation or end-processing, the scan-in-Item Drop-down menu defaults to Cataloging. Acquisitions uses this to send material to us --but we want to send material to Shelf Preparation/End-Processing. So we have to manually mouse down to insert this everything single time. This is slow (uses up time). It would be faster and healthier (on our hands) if Ex Libris could reconfigure so any library unit in a library could unit set the Scan-in-Item Drop-down menu to default to (--or to "persist" or "stick" at--)the specific status…

    97 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. Conversion job for any part of the record to any other part

    Hello,
    It would be nice if there was a job of conversion of every part of a record (bib, hol, item, portfolio) into another part, for example:
    Bib records into Items
    Bib records into Holdings
    Bib records into Portfolios
    Bib records into Orders
    Items into Bib records
    Items into Holdings
    Orders into Bib records
    Orders into items
    Orders into Portfolios
    Portfolios into Bib records
    Portfolios into Orders
    This way, we will not be limited by the search for any job.
    For example, we would be able to search Bib records, convert the set into items and run a job for…

    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)
  20. Add Melingo to ALMA

    Hello,

    The assimilation of Melingo in Primo for the customers in Israel proved to be a useful solution.
    It would be nice if it can also be implemented in ALMA.
    If Melingo will indeed be in ALMA, the catalogers will no longer need to add Ktiv Maleh or Ktiv Haser in Hebrew in variant titles.

    Thanks.

    57 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