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

129 results found

  1. Allow multiple Z39.50 to be setup in Alma

    Right we use the only Z39.50 setup for Interlibrary Loan's ILLiad. One of our librarians would like to connect a new Z30.50 to search through Endnote to run systematic reviews. We had previously wanted to use another Z39.50 setup to input a more comprehensive search in Search Resources in Alma. If we can get multiple Z30.50s setup in Alma it would help us connect various sources to Alma and make it more robust.

    1 vote
    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. Option to publish new set with Publishing Profiles

    Currently, when you change the set in a publishing profile, the previous set is first published as deleted, and then the new set is published by the job. This behavior means that we have to duplicate an existing publishing profile each time we want to publish a new set with an existing publishing profile in order to get a "clean" output and to avoid overly long processing times publishing the old set as deleted. This results in the needless duplication of institutional publishing profiles and extra staff time to duplicate the publishing profiles to publish new sets. The current publishing…

    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)
  3. Provide ability to turn off the display of Related Records in Alma

    Our staff find the appearance of related records in Alma that appear as part of a search result to be distracting and add no value. I'd like to suggest that we get the ability to configure whether these related records appear at all.

    4 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 Push Selected to MDE button available for Itemized Sets

    'Push Selected to MDE' (pushing records in bulk to Metadata Editor) is not available for Itemized sets, but it is available for Logical sets in the current Alma implementation. While the option to Push Selected to MDE is plainly visible in the Logical Set Results view (please see the attached screenshots), it is replaced by the 'Remove Selected' button in the Itemized Sets Members’ view. We would be very interested in having the Push Selected to MDE available for both Logical and Itemized sets. Is it possible to add the 'Push Selected to MDE' to he Itemized view and keep…

    28 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. Please add the ability to use the facets for Archival Materials according to LDR pos. 8 = a

    Hello,

    Most archival materials are cataloged as follows:
    LDR pos. 6 = p
    LDR pos. 8 = a
    Currently, the facet in Alma show these kind of materials as "Undefined".
    Adding a facet of "Achieve Material" according to LDR pos.8 = a, would be very useful.

    Thanks.

    63 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)

    Hi. 1. Are you stating that you want a new “Resource Type”?
    2. The definitions of the resource types are explained in the table titled “Rules Used to Create the Resource Type Field – MARC 21/KORMARC and UNIMARC” at https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/010Getting_Started/050Alma_User_Interface_%E2%80%93_General_Information/Searching_in_Alma#The_Resource_Type_Field
    3. Do you want a new row in this table which would be as follows?
    Archival materials. LDR pos. 8 = a
    4. The table is read top to bottom and as soon as match is found it stops. Where in the table would you like this new row to appear?
    5. How come the title of this suggestion states “LDR pos. 8 = a” but the comment from Feb. 2 also has “LDR pos. 6 = p”? We do not think “LDR pos. 6 = p” is a good idea. That is used for “mixed materials”. On the other hand “LDR pos. 8…

  6. Searching titles with "&" vs. "and" in Alma

    In Primo VE, when a title in the 245 contains "&", if the title is searched with "and" in place of the ampersand the correct record will come up. This does not work the same way in Alma, however.

    https://www.screencast.com/t/1mlHd3mIv

    In some cases, a 246 field could be added to have "and" spelled out but that is not a universal solution. We would like to ensure that "&" and "and" could be used interchangeably in Alma title searching as it seems to work with Primo.

    1 vote
    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. Show linked purchase requests in 'Other details' beneath title record

    It would be great if purchase requests that are linked to titles could be accessible via other routes rather than just the 'Manage purchase requests' section. Please could purchase requests that are attached to a title and a POL be added to the 'Other details' section beneath a title record in a repository search? This would allow us to quickly ascertain which titles have purchase requests linked to them.

    1 vote
    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. Add an option to search the repository by "Assign to" cataloger / operator

    Currently there is no way to know which records are assigned to a certain user except for the "assigned to" note indication. We need a way to retrieve the records that were assigned in order to restore them back to the users' MDE, in case they dissappeard from the opened records pane. See full usecase in SFC#00957311.

    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)
  9. Report list of records changed after abort job

    After a user was running a discovery suppression job, and aborted they assumed nothing was changed. It would be very useful if the records that were changed before the abort were reported to the user.
    Here's an example showing an abort that occurred and the user running the job assumed since they aborted the job, nothing was changed:

    https://www.screencast.com/t/PoFqKwEjHIuH

    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)
  10. Local Authority Automation and Workflow

    Currently, Alma requires quite a bit of manual intervention when creating local authority records and linking them to the relevant records in the catalog. In order to relink an authority controlled field (ie. 1XX, 6XX, and 7XX) someone from the library must go through and change the second indicators from 0 to 7 and add a $2 with the local authority profile code. This can be done using normalization rules but it still must be done manually. There are no scheduled jobs that will do this.

    An example might be helpful to both show the problem and a possible solution.

    3 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. Ability to create sets from "Manage Deleted Repository" search

    We would like the ability to create a set from a "Manage Deleted Repository" search.

    Some vendors cannot use the "delete" files currently generated by Publishing Profiles. We would like to create sets (especially logical ones) from a "Manage Deleted Repository" search so that they can be attached to a Publishing Profile and help automate delete processes for these vendors rather than using an external script with the API and analytics.

    This way, someone would only have to update the deleted date range of the set periodically, or even better, more search options and filters could be created for "Manage…

    14 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. Reading lists - notification on Alma if an attempt is made to delete an item on a Leganto reading list

    We would like there to be a notification on Alma if any attempt is made to delete an item that is on a Leganto reading list, whether it is deleted individually or as part of a batch-job. The deletion could be because the physical item is in poor condition or has been lost by a user, in which case we would need to know to purchase another copy. Alternatively, we may be deleting because we have purchased a newer edition, and would need to make sure that our reading lists are updated. This would apply to both physical and e-resources.…

    15 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. "Display in Discovery" from any screen in Alma

    Make the Display in Discovery action available in any screen/view of a record in Alma, not just in a repository search or in portfolio lists. There is often the need to see how a resource displays in Primo when working in an item, orders, and other areas of records.

    60 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. 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…

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

    178 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. 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,…

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

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

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

    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)
  • Don't see your idea?

Feedback and Knowledge Base