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

31 results found

  1. We expect UNIMARC and CNMARC tag 100 could be treated as a Control Field in NRs like MARC 008 field.

    We have an issue with UNIMARC/CNMARC field 100 which is not considered as Control Field when using Normalization Rules
    The current incorrect behavior is that the UNIMARC/CNMARC tag 100 cannot be changed using a NR for "replaceControlContents" - "Failed during compilation of drools files". Changing the NR to "replaceContents" produces no error but is not working (as 100 is a Control Field)
    We expect UNIMARC and CNMARC tag 100 could be treated as a Control Field in NRs like MARC 008 field.

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

    A new function was added to enhance the Alma DROOLS to support the normalization of UNIMARC and CNMARC 1XX fixed position fields. As a result of the enhancement, UNIMARC and CNMARC tag 1XX are treated as Control Fields in Normalization Rules and no error messages are displayed.


    For more information please see Alma November Release Notes

  2. Ability to limit Authority Control task list to only Institution zone records

    It is overwhelming to have hundreds or thousands of records listed in the Authority Control task list every day, especially when most of them are Community Zone records that we're not supposed to change. We need to have the option to get a list of only our Institution Zone records that need to be worked on. This would save a lot of time and frustration from having to weed through the morass of Community Zone authority issues.

    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)
  3. Authorities ordered according to the correct order rather than subfield alphabetical

    Alma organizes the name/title results in MARC subfield order, rather than RDA/MARC order.
    For example, instead of this expected order:
    700 |a Rolvaag, O. E.,|q(Ole Edvart),|d1876-1931.|tWorks.|kSelections.|f1936

    you instead get the subfields in alphabetical order, like so:
    700 |aRolvaag, O. E.,|d1876-1931,|f1936|kSelections.|q(Ole Edvart).|tWorks.

    Please fix this so subfields are ordered properly which will allow the new browse feature to work properly.

    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)
    Completed  ·  Dana Moshkovits responded

    Subfields of MARC 21, UNIMARC, and CNMARC authority record fields used to create display, sorting, and search elements, were extracted in alphabetical order rather than in cataloging order. This was fixed. As a result, additional bibliographic record elements were created. For MARC 21 display elements, this includes 5XX note fields excluding 59X, 520 and 505; 59X local note fields and 69X local subjects. For MARC 21 search elements: this includes 59X local notes, 9XX local fields, 09X local call numbers, and 69X local subjects. For UNIMARC and CNMARC, display elements include 69X local subjects. Search elements include 69X Other Classification Number, 3XX notes, 9XX local fields, and 69X local subjects.

  4. The issue of generating 008 filed in MARC 21 Bib

    While creating a new MARC 21 bib record, Alma generates the 008 automatically, such as "191126s2013####xx######r#####000#0#eng#d"
    The value in position 7-10 is a fixed date "2013". We would like the position 7-10 can be customized and retrieved from 264$c or 260$c.

    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)
    Completed  ·  Dana Moshkovits responded

    MARC21 OTB template of Books/Computer Files/Maps/Music, field 008 positions 7-11 had the year 2013. This was modified to the current year 2021.

  5. When editing a normalization, merge or indication rule there is only an option to preview and save. There should also be a "save as" option

    What happens now is user edits his rule, is happy with it, then he must copy it to his mouse, create a new rule, and paste it into the new rule. A "save as" would be much more logical. User would do "save" as he does today to change the existing rule, and "save as" to save his changes to a new rule.

    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)
  6. New Alma Layout and New Metadata Editor: Same Icons for Different Functions

    1. In the New Alma Layout the ‘Recent Pages’ and ‘Recent Entities’ share the same icon although they serve different content (cf. attached screen clipping).

    2. In the new Alma layout, the icon for Advanced Search displayed left of the persistent search slot is essentially the same as the icon in the new Metadata Editor's left pane, which serves to filter the list of records (cf. attached screen clipping).

    We believe that using one icon for two different functions is confusing to the users and suggest replacing the icon for one of the two for both cases.

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

    Thank you for your feedback. We have changed the advance search icon to a different icon than the filtering option in the new metadata editor.
    We have checked the other idea of changing the icon for Recent Pages and the icon for Recent Entities and come to the conclusion it is the common semantic users are used to.

  7. Show if cataloguer notes exist

    When working in the meta data editor we don't know if a record has notes attached to it unless we select "View Notes". it would be helpful if record with notes attached showed the existence of a note, maybe with a small symbol?

    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. The metadata editor is not friendly for editing the bibliographic record

    It would be advisable to improve the visualization of the complete record; also that the cursor should be more precise when completing the indicators of each field; that the spaces between the subfields should be more clearly seen, etc, etc

    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. Stop adding a line and taking cursor to 2nd line when I copy/paste into a field

    Whenever I copy & paste content into a field (replacing old content), it automatically does a carriage return/enter and adds an extra line below and moves the content I just pasted to the top where it disappears until I scroll to see it again. My cursor is automatically taken to the 2nd line and the first line disappears until I scroll or back up to see it.

    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. Support SWEDISH and NORWEGIAN special diacritics in Browse

    Support SWEDISH and NORWEGIAN special diacritics in Browse
    On behalf of the Product management team we would like to understand the need and use cases of the following 'Planned' feature (which it's need was raised by a specific library) - any comment is welcome.

    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)
  11. UNIMARC to MARC21 Authorities crosswalk issues

    UNIMARC to MARC21 crosswalk should be updated
    On behalf of the Product management team we would like to hear about the improvments that are required of the following 'Planned' feature (which it's need was raised by a specific library) - any comment is welcome.

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

Feedback and Knowledge Base