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

    22 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. Enable case-insensitivity for indication and other rules

    Indication (and other) rules in Alma are case sensitive by design. Case sensitivity of course is often desirable, to ensure most exact matching and prevent inadvertent data problems. However, in some instances, especially with indication rules, it would be very helpful and time-saving to be able to use case insensitivity, as is possible with regular expressions (ex: /i). An example of a scenario in which this would be helpful is when using an indication rule to identify records which contain a particular textual note, when that note may have been entered with varying cases: sometime all uppercase, sometimes sentence case,…

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. 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…)
  5. ACTL needs to be refined: Ending ISBD punctuation issue

    There are many entries in ACTL that the only difference between BIB Heading Before and BIB Heading After is that the full stop is removed at the end of BIB Heading After. For example:

    BIB Heading Before
    Hong Kong (China). Census and Statistics Department.

    BIB Heading After
    Hong Kong (China). Census and Statistics Department

    This kind of entries should be excluded from ACTL since this is not heading update at all.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Show Brief Record Levels in Search External Resources

    It would be really useful if we could see the brief record level when searching for catalogue records via "Search External Resources".

    Currently the only way to perform a brief level analysis on a record is to import and save it. It would be really useful to see this when searching external resources, without having to save and import the record first.

    This will be useful to ensure a good level of metadata is maintained across our catalogue.

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

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

    63 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. Prevent 9xx local fields from being saved to Community Zone (CZ) records

    There is a known issue of some sites not adhering to the Community Zone (CZ) Contribution Guidelines and Community Catalog Standards.
    An example of this is the addition of local 9xx fields to CZ records.
    Ex Libris already uses a normalization routine to validate CZ records which are changed by customers.
    However, this routine does not specifically prevent the addition of local 9xx fields, even though the guidelines are clear that only changes which benefit the broader community should be made.

    Use case:
    This has been a longstanding issue, but has been fixable in the Primo Back Office to an…

    35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  17. Circulation count in item record

    Include a field in the item record which contains the circulation count or number of times the item has circulated.

    We want to be able to access the circulation count via API and Alma item record view.

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  18. Add a F3 functionality in the dropdown menu of the MDE

    In the Metadata Editor, F3 is used in order to look up to the authority headings from a specific bib heading. This is a crucial feature of the MDE, yet it is not available in the dropdown menus. As our librarians sometimes work with tablets, with no function keys, this lack is troublesome. Adding the look up functionality in the dropdown menus would be a welcome improvement of the MDE.

    51 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  19. Create a Physical Titles or Physical Items set from a list of MMS IDs

    It is possible to create an All Titles set from a list of MMS IDs, but not a Physical Titles or Physical Items set. To run certain jobs – like Change Holdings Information – a Physical Titles set is required. In order to run this job on a list of MMS IDs, you must first create an All Titles set, then extract some other key like OCLC #, then create a Physical Titles set from that list, and only then can you run your job. Since all physical titles and items DO have MMS IDs, it should be possible to…

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  20. 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…)
← Previous 1 3 4 5 6
  • Don't see your idea?

Feedback and Knowledge Base