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. Metadata Editor should add the year automatically to the 866 field

    Currently the Metadata editor does not add automatically the year to the 866 field. If we want the year to be in our 866 we have to add it manually. Actually this is the only way our patrons can see the year in Primo.

    69 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. Mechanism to validate binary MARC record structure

    There is currently no mechanism within Alma to ensure that exported or published binary MARC records have valid record structures. Even though Alma uses MARCXML and is not impacted internally by invalid binary MARC, libraries must still provide binary MARC records to external entities in the course of regular business (vendors, outsourcers, agencies, other stakeholders).

    Structurally invalid binary MARC records significantly hamper data sharing for libraries. A third party application, MarcEdit, can be used to validate MARC record structure, but since our data is stored in Alma, there should be a mechanism native to Alma that validates binary MARC structure…

    65 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. Visibility of extension packs and possibility of selecting them one by one for editing and/or deleting

    Extension packs once added to a local MARC-based profile are not visible and cannot be retrieved in any way. It would be much better if each extension pack loaded to a bibliographic profile could be visible to system admnistrators in order to be downloaded from bibliographic profile for purposes of editing and reloading, should the need arise. This feature was part of the tentative future developments proposed by Ex libris back in 2017 (see: internal: 2017 Q1 URM-45100)

    65 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. New Metadata Editor templates: editing template v. creating new record

    Previously, when opening a template in the classic Metadata Editor (MDE), a click on the template name from the list of templates would give a list of options, including creating a new record: there was no doubt as to whether you were creating a new record from the template, or editing the template itself.

    However, with the new MDE, clicking on the template name takes you straight into editing the template itself. Creating a new record from the template now requires a right click first to get to the options menu, but this is not at all obvious. It is…

    64 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. Preferred term correction - correct coding when flipping LCSH to LCGFT

    When a 655 field is coded for LCSH and matches a non-preferred term in LCGFT, Alma flips the heading to the preferred LCGFT term but does not update the coding (it should change the 2nd ind to 7 and add $2 lcgft).

    The problem is limited to cases where:

    A bib heading 655/_0 matches a non-preferred term in an LCGFT authority

    What happens is:

    The PTC job flips the heading to the LCGFT preferred form, but it does not change the 2nd-indicator from 0 to 7, and does not add $2lcgft

    What is not a problem:

    655/0 headings that

    61 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. Ampersand symbol (&) in Repository search

    It's found that the repository searches using the ampersand (&) symbol and the word 'and' produce different results. Our request is to make the ampersand symbol and the word ‘and’ interchangeable when Alma does repository searches.

    SF case # 00646924

    60 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)
  7. Adding 'own' Covers to Alma records!

    Dear,

    This question might be related to:

    https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/38314153-how-can-we-add-a-book-cover-image-or-equipment-ima

    We would like to have the ability to add covers in Alma (and display those in Primo) for all kinds of records.

    Br,

    57 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. browse by subject headings to include 600/610/611

    currently browse bib headings by subject does not include 600/610/611 fields (they are placed in 'names'). When browsing by subject one would expect to find all subjects including those that describe people/companies etc.

    57 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. Indication rule that checks if subfields are in the same field

    Currently it is not possible to write an indication rule which checks the subfield a and b of a field only when both subfields are in the same field and not in repeated fields of the same record. Both of the following records are treated the same when looking for a subfield a "mercury" and subfield b "venus" in the 690 field:

    Record 1:
    690 $$a mercury $$b venus

    Record 2:
    690 $$a mercury $$b mars
    690 $$a earth $$b venus

    I'd appreciate an option to distinguish if I'm looking for subfields in different fields or in the same field.…

    55 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. MDE Search Resources mask should be empty

    When opening the Search Resources mask in MDE, the previous search is still in the data mask. For us there is no benefit for this behavior and we would like to have an empty mask and not to clear the mask every time before starting a new search.
    (If other libraries need this opportunity, we would suggest to make the default settings for this mask customizable)

    55 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. Add indication that the bib. record has a MDE note

    It would be helpful to have an indication that there is a MDE note regarding this record posted by a cataloger.
    One option to see this indication can be on the preview of a bibliographic record. It can appear the same way as when there is an order for the record (see photo attached), and if you click the number, it should take you to the note.
    Additionally, it should be either reportable to Analytics or searchable in Alma, so that it will be possible to find all the records that have MDE note.

    54 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)
  12. Want to view more of a bibliographic record when editing without having to scroll

    There is currently quite a lot of unused space above and below a bibliographic record. It would be great if I could drag the bottom of the bibliographic record down further when I am editing so that I can view as much of the record as possible at once.

    54 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)
  13. The text font ,font size and color of Metadata Editor

    1.When using Metadata Editor, the font size and color of the editing area are not friendly to the editor.

    2.The text in the editing area needs to be enlarged by 150% in the browser to make it convenient for users to work for a long time

    3.The text color or font in the editing area causes the black text to look like gray, which makes it inconvenient to check the bibliography

    4.Can workers modify the Metadata Editor environment to make them comfortable working environment, such as the font size, font type, and font color in the editing area?

    This can…

    54 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. Improved functionality for Authority contribution (Copy to community)

    This copy option was introduced in the November 2019 release: Authority Contribution – Copy Option:

    For institutions that are authorized to contribute authority records to the Community Zone, there is a new Record View page action (Copy to Community) that enables you to easily copy an authority record to the MD Editor, edit and save it, and contribute the saved record to the Community Zone and an external authority system such as GND, BARE, or NLI. The Copy to Community action appears when you select a title to view from your Authorities search results on the Community tab. See Copy…

    52 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. Add a drool normalization process option, to Publish to Primo job

    This will enable libraries to export to Primo their activated CZ bibliographic records, under the same conditions applied on their local bibliographic records.

    46 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. Diacritics and special characters

    When importing records from vendors diacritics and special characters should also import. Currently they come in as random characters or unicode and it takes up staff time to manually correct them.

    45 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. EuroVoc Thesaurus implementation

    Add EuroVoc http://eurovoc.europa.eu to Authority Vocabulary.
    It is the multilingual, multidisciplinary thesaurus covering the activities of the EU.

    41 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. Metadata Editor: Add More Keyboard Shortcuts and Make Existing Ones Intuitive

    The ME needs a keyboard shortcut for every function. 'Search External Resources', 'Release Record', and many other actions do not have keyboard shortcuts, so I still essentially have to use the menu for everything. This is simply inaccessible.

    Secondly, the shortcuts that do exist don't make sense. A new field is F8, but deleting a field is CTRL + F6? Why not just make it CTRL + F8? Or F9? These shortcuts are poorly thought out and confusing.

    41 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. Ability to select records to release from MD editor

    Cataloger can release 1 record per time or all records can be released, but it would be useful catalogers could select multiples records to release.

    38 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)
  20. Create a Separate Search Index for Specific OCLC Number

    Currently, the OCLC Number for a record is indexed in the search index "Other System Number." This is not ideal, since the Other System Number indexes other numbers related to vendor record, CONSER, related item, etc.
    We request that Ex Libris provide a separate search index for OCLC number based on the presence of the '(OCoLC)' prefix in the 035 $a and/or $z, or (without prefix) in the 019 $a if there is a number in the 035 with an (OCoLC) prefix. Currently these specific (OCoLC) numbers are mixed in with other numbers occurring in the 019, 035, 773, 774,…

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

Feedback and Knowledge Base