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

259 results found

  1. CDI labels in Alma to be more clear and user friendly

    User Story - Our staff are confused when using CDI and would like clearer label, so they understand where to enabled something or not.
    We would prefer the labels to be changed to more ‘symptom based diagnosis’ wording. So it would be clear for CDI operators. We have left 'CDI-only full text activation' blank, because he is still not sure what this option is for. In our example we have only given suggested wording. We are happy for this to be different, as long as the labels are more clear and user friendly about what the functions do.

    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. Add 385,386,655 to Alma export list

    Please add columns to Alma Export to List (Excel) from these fields: Creator/ contributor term (386/a), Audience (385/a), and Genre/form (655/a,2). These fields are important to include to the list.

    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. error message

    when you want to add a title into a collection, if this title already exists in the collection, an error message should appear "title already in the collection". It would be very useful.

    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. Having the ability to configure the presence of all available Licensing terms in the Repository Search in Alma

    There are a number of License terms that appear in the Advanced Repository search that are not configurable, that is there is no option to stop them appearing as options to search under in a simple or advanced search.

    We want to delete some of these terms from Advanced Search. We want to get rid of the terms that we're not using in our current Licensing workflows (they clog up the search). The terms we want to delete from the Advanced Search are not available to configure in the Alma Configuration Menu > Resources > Search Configuration > Search Indexes.

    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. 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)
  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. 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)
  8. 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)
  9. 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)
  10. 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)
  11. 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)
  12. 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)
  13. Index 049 field.

    We tie the OCLC holding library in the 049 closely to our Alma holding locations. Searching the text in the 049 field as keyword is quicker than an advanced search. If the idea below to allow free text searching of all MARC fields and subfields is implemented it would cover this request.

    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)
  14. Open second search box when "Advanced" is selected from persistent search

    The default persistent search box in Alma is one line. For a more complex search, I click on "Advanced". I then (always) have to click on the plus sign to get a second row for additional critieria. I would like for the system to automatically open that second search box when "Advanced" is chosen. Thank you.

    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)
  15. Duplicate title analyis : able to detect duplication on 856

    It would be good to be able able to detect duplication on the MARC 856 field

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

    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)
  17. Automatically deactivate any scheduling of repository import profiles when import method changed to Upload Files/s

    When the import method of a repository import profile is changed to Upload File/s, any scheduling previously set for another import method should be automatically switched off.

    Currently the scheduling status for FTP/OAI has to be manually changed to inactive, in addition to changing the import method.

    This could easily be forgotten by staff making changes to import profiles and results in the scheduled metadata import jobs continuing to run and subsequently failing.

    The process would be streamlined and more efficient if scheduling could be automatically removed when an import profile is changed to an import method which does not…

    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)
  18. function "back"

    Metadata Editor: We miss the simple function of being able to undo the last steps when cataloging or editing records. In Aleph there was the function
    CTRL + Z. This would be extremely helpful. The ability to restore an earlier version is not suitable for this.

    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)
  19. Publishing profiles should be able to produce valid MARCXML

    The ability to produce valid MARCXML exports from publishing profiles, with the namespace included, would be useful.

    Currently the "MARCXML" option produces a file that is not valid MARCXML. It doesn't include a namespace.

    The rationale given by ExL Support for not including a namespace was that it would be possible for the user to use norm rules to change the data on export, in which case the data might not be valid, so they didn't want to include a namespace. In some cases it may be necessary for libraries to produce data exports that are not valid, but even…

    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 9 10 11 13 Next →
  • Don't see your idea?

Feedback and Knowledge Base