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.
105 results found
-
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 -
In addition to LCSH, LSNAF, MeSH, GND and VIAF, Wikidata is at least an another good source to enrich the bibliographic information.
ALMA currently adds URIs of 5 authoriities sources to enrich related bibliographic records. It is a good way for patrons to "crawl from one data description to another" if we push the information to Primo. Those 5 sources are good. However, information coming from Wikidata or Wikipedia seems nowadays to be more accessible and acceptable by the users. We suggest ALMA should add URIs of Wikidata (or the like) , so the users can retrieve more information on related entities.
23 votes -
Adding 'own' Covers to Alma records!
Dear,
This question might be related to:
We would like to have the ability to add covers in Alma (and display those in Primo) for all kinds of records.
Br,
58 votes -
Add management information when publishing authority records using OAI-PMH
We want to publish our local authority data to a third party system. Adding management information such as Creation date, Modification date, Created by, etc. would be extremely valuable. Yet, management information enrichment is available for other kind of records, but not authorities (cf. in the documentation page https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/090Integrations_with_External_Systems/030Resource_Management/080Publishing_and_Inventory_Enrichment).
Could you please add manangement information when publishing authority records using OAI-PMH?15 votes -
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
221 votesDear all, since this idea combines various very different enhancement requests for Alma's normalization rules infrastructure, we are unable to add these to our roadmap at this time. This may change as we get more information on prioritization and needs. In the meantime, we suggest opening dedicated ideas for specific enhancements you would like to promote.
-
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 -
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 -
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…
68 votes -
Manage Cataloger Roles at the Library Level
We would like the roles Catalog Administrator, Catalog Manager, Cataloger, and Cataloger Extended to be set at the Library level instead of the Institution level. We have special collections that we only want only some of our staff to edit. Assigning catalogers to one or more libraries is much more efficient than assigning cataloging levels to users and records.
15 votes -
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.
77 votes -
Version control/history of normalization, merge, and indication rules
Alma should store the version history of normalization, merge, and indication rules - just like bibliographic metadata - in case someone makes an inadvertent edit. This would allow users to restore the rule to a previous, working state.
24 votes -
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.
125 votes -
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,…
20 votes -
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 DepartmentThis kind of entries should be excluded from ACTL since this is not heading update at all.
18 votes -
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 -
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 -
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…88 votes -
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 -
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.
15 votes -
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
- Don't see your idea?