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. Suggestions for Normalization Rules (NR) functions

    Hello,

    Please see the attached file.
    We would appreciate it if the suggested Normalization Rules functions would be developed in Alma.

    Thanks

    152 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. 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…)
  3. 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…)
  4. 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…)
  5. Make configurable pop-up assistance in metadata editor

    Currently the po-up assistance in metadata editor for subfields 260$a$b$e$f, 264$a$b, 505$r$t and 561$a is hardcoded and it can not be deactivated. Activation/Deactivation should be configurable. We have many queries from our catalogers about that.

    55 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. 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…)
  7. Incorporation of All Indigenous Syllabics from the Canadian Aboriginal Syllabics Unicode Block

    I have a case open with Ex Libris (# 00517082) regarding this. Not all Indigenous syllabics render in Alma, and thus, do not render in Primo either. As an important aspect of Canadian Libraries' commitments to Truth and Reconciliation, and as it is UN's International Year of Indigenous Languages, it would be excellent if Ex Libris could prioritize resolving this issue so that we can allow Indigenous users full discoverability of resources in their own languages.

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

    54 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  10. Preferred term correction should flip headings that change tag number

    Alma authority control does not handle cases where the bib heading is linked to an authority via a cross-reference, but the preferred and non-preferred terms are in different fields, e.g. preferred term is in authority field 130 and cross-reference in authority is in 410.

    Alma should be able to handle this scenario. Currently when the bib heading matches the authority cross-reference, Alma won't correct these and instead puts them on this report: Preferred Term Correction - Bib Heading found no authorized term.

    Example bib heading that Alma won't correct:

    110/2_ $$a Allied and Associated Powers (1914-1920). $$t Treaties, etc. $$g…

    145 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  11. 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…)
  12. 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…)
  13. add security levels to norm rules

    Because all norm rules can be edited by all staff with cataloger roles, there is great room for erroneous changes for rules that are applied to batch jobs. For example, the norm rule that is applied to records being brought in from Z39.50 targets can be edited by any staff member. A single error in the rule can break the z39.50 import process for all staff until the source of the error is identified. Likewise, if we have a rule applied to import profiles and a staff member inadvertently changes it and we load 50,000 records, that could cause huge…

    174 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  14. Add OCLC number to physical item export

    Large scale weeding projects would be made much more efficient if Alma offered the ability to include OCLC numbers in the physical items set export details. Currently, we are in the position of using a work-around where we must create a title-level set based on the same items. There are bib-level elements present in the physical item export, so we assume this is possible. Ultimately, we would prefer the option to select which fields export for every export we perform, but the addition of OCLC number to physical item exports would be a great first step. 

    96 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  15. 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…)
  16. 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…)
  17. Copy and paste multiple MARC fields into the metadata editor

    We would like to be able to copy multiple lines from MARC records and paste them into the metadata editor so that multiple MARC fields are pasted into the record in one action. This would help us enormously with our workflow of importing MARC authority records from LibrariesAustralia into Alma.

    For us, this is necessary because the LibrariesAustralia headings are not in the community zone and are unlikely to ever be included there and Alma does not allow for Z39.50 import of authority headings.

    We have this functionality of copying and pasting multiple fields in the LibrariesAustralia Cataloguing Client and…

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

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