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
  1. Navigating list of records

    Would like to have a forward option when working in a list of catalog records. It's cumbersome to have to go backward to go forward to the next record in the list.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Working with 2 or more name authority files : Implement new Marc21 subfield $2 -

    Marc21 Format change from May 2019 introduced a new subfied $2 in bib headings.

    $2 contains the source of heading of term in name or name-title and title headings (http://www.loc.gov/m.arc/bibliographic/bdapndxg.html)

    This subfield $2 already exists for use with 6xx headings, 2nd indicator 7. With this format change, Marc21 introduce the $2 in 100-700-800/110-710-810/111-711-811/130-730-830 fields.

    In Alma, links with Name/Titles authority file can be made only with 1 unique file, unless you use the Authority Priorities. Unfortunately, Authority Priorities is not convenient to all situations.

    Other linking possibilities based on $2 value would be more consistent for authority control.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. Bibliographic records editing history

    Here is an enhancement request concerning bibliographic records editing history.

    Currently, the "View Versions" can only tell the different version of a bib. record. However, this cannot tell logging history of updating/editing the bib. records, e.g. who add/remove a MARC fields/who suppressed/released the bib. record etc. This is no history tab to keep tracking the changes of a bib. record which is unlike other history tab functionality available in other Alma pages, e.g.

    • The PO Line Summary page when editing a PO line
    • The Physical Item Editor page when editing item records
    • The License Terms Details page…

    43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. Cataloguing statistics

    I'd like to suggest to add features that make generating cataloguing statistics easier, e.g.
    1. cataloguing date
    (We want a date format field that is stored as a local field, independent of the 005 MARC field because every time the record is edited, the date and time details in 005 field will be changed, and often these activities should not be counted as a cataloguing event.)
    2. cataloguer details
    3. whether this is original cataloguing or copy cataloguing
    4. whether this is a cataloguing contribution from Institution Zone to the Network Zone, or vice versa (i.e. copied from the Network…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. Allow for multiple holdings records and item records to be opened at one time.

    Sometimes, it's helpful to look at multiple holdings records at the same time to compare. It's also helpful to have the system open all of the item records for a holdings record at one time if you're gong to be doing minor changes to each one.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. 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,…

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  7. 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

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. When editing a record it would be desirable that for cut/copy and paste fields and subfields should exist specific keys

    It's very annoying to use Ctrl v and ctrl c for fields and subfields, as we are used to use it for plain text

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  9. Access to the bibliographic access points of our own catalogue while editing a bibliographic record

    When we edit a bibliographic record it's very useful to access and add to the record the different access points of our catalogue in order to avoid typing all the string of data, even if there is no authority record. For example: there is no authority records for all de free floating subdivisions of LCSH that we add to main SH

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. DB-category-job on all bibliographic records

    In Alma there is a job that based on a specified marc-field builds up a hierarchy of categories for the A-Z Database search in Primo.

    This works fine, but the job is limited to a certian subset of records only.

    From Ex Libris:
    "The Database Categories File job runs for the benefit of Primo database search, and is therefore relevant only for bib records linked to databases." https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/050Inventory/020Managing_Electronic_Resources#Working_with_Database_Type_Electronic_Collections

    I can understand why it was designed like this, but in our consortia we see that the institutions would like to include other records in the A-Z-list as well. Records that are…

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. Lists of Name Authorities similar Subject Authorities

    Lists of Name Authorities similar Subject Authorities
    When cataloging a bibliographic record, Alma allows selecting different lists of Subject Authorities (LC, UC or UANDES, etc.). In the case of the Name Authorities, it currently only allows the use of a list of Name Authorities. We propose that the authorities of name are handled in the same way as the Matter Authorities.

    // Al momento de catalogar un registro bibliográfico, Alma
    permite seleccionar distintos listados de Autoridades de Materia (LC, UC o UANDES, etc.). En el caso de las Autoridades de Nombre, actualmente sólo permite usar un listado de Autoridades de…

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  12. Remove alert in Metadata Editor for presence of marc 019 field

    In the metadata editor, please update the Alerts so that the presence of marc field 019 in a bib record does not generate an error message on save. 019 contains the OCLC control number of duplicate records that have been merged and deleted from WorldCat. It's not a standard marc field, but it contains useful information for OCLC libraries.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  13. Add a new item level material type for 78 rpm sound recordings

    The only options for 78 rpm sound recordings currently are "sound recording" or "record (phonodisc)." There is a material type for LPs, so why not for 78s? This is very important for music libraries and archives. Thank you!

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. 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.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. Provide authority control for terms in 3XX fields.

    Terms in fields 380, 382, 385 and 386 should be matched to authority records based on the $2 code and an icon placed next to the field when the terms have been verified.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  16. Allow cataloguers to choose which names are linked to authority files

    Allow cataloguers to choose which names are linked to authority files

    This is important because the all on or off automatic linking creates links for unqualified names and catalogers want the option to verify and thus link names in the way it is done in connexion.

    This when the authority data is updated - every record attached to it is improved and unqualified or non-established names do not get affected.

    116 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Browsing Dewey in MD Editor

    We noticed that in Metadata editor the browsing in the 676 - Dewey field isn't available: we would like add the feature to scroll the lists from other records, as happens for the 6xx fields (subjects) and 7xx (authors).

    102 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Increase size of MD Editor main panel

    The Metadata editing window (main panel) is really small compared to the rest of the screen. Dragging and dropping the panes does not have much effect. There is also the Full Screen functionality which only widens the editing screen. The problem is that it should extend the view of the fields in the length. We would like to see more fields of the record at one time. The panels at the top and bottom of the screen are very wide, so there is plenty of space to make more room for the actual editing.

    44 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Create a "natural language" editor to create Normalization rules

    The process for creating Normalization rules is unnecessarily complex and difficult, particularly for those of us who are not familiar with Drools logic. Our previous LSP had an intuitive interface which made creating rules to change details in MARC records much less time consuming. Ex Libris would do well to create such an interface.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. search filters and better results display in the "search external resources" function

    When we are searching WorldCat for a record to match a newly-ordered title, we often find duplicate records. The current search results display makes it difficult and time-consuming to choose the best record.

    The external resources search would be much improved if we could limit search results by the language of cataloging (040 |b) and format. This would save us having to wade through multiple vendor records that aren't even in our local language of cataloging, and multiple records for resources in a format other than the one we are looking for.

    It would save us a lot of time…

    52 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  • Don't see your idea?

Feedback and Knowledge Base