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

130 results found

  1. 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)
  2. 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)
  3. Improve search for ayn diacritic directly after hyphen

    In a romanized Hebrew search when an ayn diacritic appears directly after a hyphen, there is zero results with the expected search: "gozeret ha-orot" (no spaces). This very search has the expected result in Primo but not Alma. That search also works in OCLC Connexion. I was told to use a space instead of a hyphen in Alma, which brought up the record but it is not the way one expects to search in this instance.

    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)
  4. Add a tab to Manage Sets that shows Sets linked to Publishing Profiles

    From Admin - Manage Sets we can see My Sets, Public Sets, and All Sets. It would be useful for there to be a way to more easily distinguish and find sets that are used in Publishing Profiles. As more and more integrations with third party services rely on Publishing (HathiTrust, Google Books, RapidILL, BrowZine, Syndetics, etc.) more and more sets need to be created and maintained and occasionally tweaked if locations or libraries are added, removed, or changed, or if new materials within the sets become unshareable for some reason.

    The current workflow to find the right set is…

    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)
  5. Add Call Number to all Overlap and Collection Analysis Reports that include Print

    Add Call Number to all Overlap and Collection Analysis Reports that include Print

    The new Title Look Up function that permits comparing a list of print to various electronic collections is excellent. However, the output reports don't include the print call numbers. That would be a significant improvement; staff could then easily use the report to go to the shelves. As it is, we have to do a separate process in Analytics just to get call numbers which seems like a waste of time.

    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)
  6. automated import profiles - create log file with useful information if process fails

    We are finding Alma less than helpful in cases where the automated download fails due to a parsing error. Apart from actually creating a log file as suggested here, there would be other ways to improve this experience.

    This is what currently happens:
    - for automated import profiles, no log file is created when the process fails, the emailed report simply states that the import failed, there is nowhere in alma where I could find any further information
    - because of this, we then need to try and run the import manually, so we can see what the issue is…

    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. Allow Correction of MARC21 Field Data in Metadata Configuration List

    In Config-->Resources-->Metadata Configuration-->MARC21 Bibliographic, Alma users can add a new MARC21 field not currently included in the suite of out-of-the-box MARC21 fields by using the "Add Extensions" command to upload a XML file that contains field definitions and prescribed indicator and subfield values. The values in that file trigger error warnings in the Metadata Editor if that field contains incorrect indicator values or unauthorized subfields in a given bibliographic record. However, it is currently NOT possible to delete a newly added MARC21 field or upload a revised XML field definition file without deleting the entire extension pack.

    What we're requesting…

    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. Overview of linked bibliographic records in chronological order

    When cataloging, it is beneficial for catalogers to view an overview of linked bibliographic records in chronological order, rather than solely in alphabetical order. This pertains to the presentation after selecting F3 - view - bibliographic records. Currently, there seems to be no option in Alma to change this presentation. While it is possible to search from authorities outside the Metadata Editor, this process is more time-consuming.

    Catalogers can work more efficiently if they can quickly determine whether an author/corporation, etc., is the correct one. Being able to promptly view the most recently published editions aids in this process.

    As…

    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)
  9. No relation "Replaces/Replaced by" between records due to entry of invalid ISBN (020 $z)

    If there are two records in Alma, one that has 020 $a u and another that has 020 $a v and 020 $z u, the both records will be related by the system with the relation: Replaces/Replaced by. The 020 $z is understood as a "cancelled" ISBN and therefore included in the job that calculates the relations.

    In the vast majority of cases we know 020 $z is a false/invalid ISBN: a publisher mistakenly(!) uses the same ISBN in two different resources that have nothing to do with each other. However, according to the international rules for describing resources, the…

    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)
  10. OAI publishing profile

    At the moment Alma can have only one OAI publishing profile. However this doesn't always meet customers needs.
    We already have one OAI profile which we use with RapidILL to control books and is restricted to our main library via the set rules. However we have now been asked to set up another OAI profile to link to a service which would use books in two of our other libraries. At the moment this is impossible.
    Could this functionality be added? I imagine it would be of benefit to other Alma users.

    0 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)
1 2 3 4 5 7 Next →
  • Don't see your idea?

Feedback and Knowledge Base