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

9 results found

  1. Improve Alma Job Reports for Failed Record

    It would be extremely helpful if more details were given when there are failed records or records with exceptions on the jobs we run in Alma. Many of the job reports only report the number of failed records. It would be great if the report would provide MMSID information so the we know what records failed.

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

    174 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. Add Previous and Next buttons to various screens

    After conducting a search and selecting a record to view, it would be nice to have Previous/Next buttons for navigation, rather than needing to always go "Back" and then select the next record in the list for viewing. This could also be useful in other areas, like the physical item editor, and perhaps in some Fulfillment functions.

    125 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. Display all related records instead of 500

    When looking for related records (Brief results list > Other > Related records), only 500 titles are displayed.
    Especially when working with series/journals with many issues, monographs, or analytical records, having all related records would simplify the daily work.

    70 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. 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)
  6. 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…

  7. Normalization rules - adding dates

    It would be great if the normalization rules could be enhanced to use variables such as date, or add datestamps.

    We would like the ability to insert dates into MARC notes fields via normalization rules.

    Ideally inserting variables something like %DAY%/%MONTH%/%YEAR% in a rule would add today's date in the format DD/MM/YYYY once a rule is run.

    59 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. option to delete bib when relinking physical inventory

    When relinking electronic inventory, a pop up occurs asking what to do with the bib (nothing, delete if no other holdings, or suppress).

    It would be a time saver to have the same pop up when relinking physical inventory

    16 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. Textual holdings statement fields 866-868

    Currently, you are only able to search the 866 field in Alma and Analytics. To record holdings more accurately, the 867 (supplemental material) and 868 (indexes) should be used. We have data stored in these fields and are unable to search/report on them easily. We would like the 867 and 868 fields to be searchable and perhaps even indexed in Alma, and reportable in Analytics. Reporting on any standard MARC field should be possible in both Alma and Analytics.

    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)

    Hello. What is the reason for not doing this as follows?
    Add the 866 – 868 as local fields for Alma Analytics Holdings Records. Each institution is allowed up to 10 holdings fields and 10 bibliographic fields as local fields.
    Further, as described at https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/Add_bibliographic_fields_to_Alma_Analytics it is possible to have subfield delimiters in the local fields added to Alma Analytics.
    So you can already have 866 subfield x and z (for example) in Alma Analytics using existing functionality.

  • Don't see your idea?

Feedback and Knowledge Base