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.

How can we improve Alma?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • 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

    116 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  2. Permanent „save and continue“-button in item record

    We would highly appreciate a permanent „save and continue“-button in the item record, so that we can use the links in the item record, after changes were done, without saving and re-open it again. One scenario is changing the location in the item record and using the link to the holding to update this, too. At the moment this link is useless after changing the location, because it links to the old holding.

    179 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…

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

    38 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. offer true author/creator browse

    Currently Alma offers browsing bib headings with using "names" type - which includes also headings from 600/610/611.
    We find it more useful to have a way to browse by author/creator headings without the subject name fields (relevant 1xx and 7xx without 6xx).

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

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

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

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

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

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

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

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

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

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

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

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

    9 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