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

210 results found

  1. Differentiate Success & Warning colors in MDE

    It would be nice to be able to configure the colors within the Metadata Editor, specially when it comes to the success, warning and error messages. The warning messages seem to have the same color as the success messages that makes less obvious if they are very valid warning messages to look at.

    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. attachments tab for any item

    Is it possible to have an attachment tab added at the physical item editor level? So that we can attach files for anything regardless of whether the item has a POL, or is in a collection.

    For example, we have an old kit purchased prior to our alma migration, so we have no POL/invoice, nor is it in a local collection. So at present we have no way to attach a pdf copy of the guide that goes with the kit. Guides go missing all the time. We do keep a physical master, but it would be nice to just…

    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. Ability to open links in metadata editor in a new window

    The "Go to link" feature for URLs in the Metadata Editor should give the option to open the link in a new window.

    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. Mouse cursor after save

    In the Meta data editor after "save", the cursor goes to the LDR field. It would be nice if the cursor will go to the search of Alma.

    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. Controlled Vocabulary: Deploy Changes the from Controlled Vocabulary Registry Screen

    As a catalog administrator, I want to deploy controlled vocabulary changes from the controlled vocabulary registry screen with a deploy button so that don't lose time with navigating to another screen.

    Currently, controlled vocabularies that are managed in the controlled vocabulary registry must be deployed in a separate step by going to Alma configuration > Resources > Metadata management > e.g. MARC21 Bibliographic > Deploy.

    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. Controlled Vocabulary: Display locally managed controlled vocabularies in the Controlled Vocabulary Registry

    As a metadata administrator, I want one place in the Alma configuration that shows me all controlled vocabularies so that I can view and modify them more easily.

    Currently, locally managed controlled vocabularies (that are linked locally to just one specific field) aren't displayed in the controlled vocabulary registry. This makes it tedious to look them up, view and modify them. To do so, you currently have to go to the specific field and subfield in the metadata configuration. This costs a lot of clicks and feels tedious.

    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. Merge rules: Make primary and secondary records configurable

    For merge rules, it is currently fixed which of the two records involved is primary and secondary. However, for certain scenarios, it would be very handy to have the possibility to change that default configuration (a) as default for the specific rule, and (b) when applying the merge rule in the metadata editor. For example, if you want to use external search to enrich your record on the left pane with the record on the right pane. This functionality would also facilitate the re-use of merge rules (say, you want the same kind of fields to be retained for an…

    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. Metadata Editor: add filter sort by type XSL

    It would be helpful when searching for shared norm rules to be able to sort by type XSL. Right now when looking for a rule to copy and customize we have to pick thru a list of several hundred, because the majority are drool.

    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. Sort Subfields Task does not work correctly in combination with Authorities - Preferred Term Correction

    We've defined the following Sort Subfields Task but there seems to be a problem in combination with "GND Authorities -Preferred Term correction"

    700: iaqbcdtmnrpkolgfs0
    710: iagbndctkplfs0
    711: iagendctkplfs0

    The subfield i which we defined as first in 700/710/711 is suddenly put last. If this happen, the latest job that was run is always Authorities - Preferred Term correction

    In any case, the sorting should be the way we defined it in the Sort Subfields Task

    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)
  10. Return Expand From Template wide drop-down menu

    In the previous metadata editor the drop-down menu of serial patterns was wide enough so that we could see the complete description of each pattern. The new metadata editor cuts off the descriptions so that we must guess which is the correct pattern, and then remove the field and start over if the guess is wrong.

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

Feedback and Knowledge Base