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.
121 results found
-
Add in the configuration the ability to make the search default of the authorities to be in CZ all the time.
Hello,
When searching in the authorities, Alma jumps from IZ to CZ and vice versa in different menus.
For institutions that do not maintain local authority file, it is frustrating that the search needs to be changed to CZ when Alma “decides” it should be in the IZ.
If there was a check box in the configuration that would enable us to choose that the search default in the authorities would be in the CZ all the time, it would be greatly appreciated.Thanks.
Dafna1 vote -
Add Library & Location Facets to Authority Control Task List
Could we add facets for library and/or location to the Authority Control Task list when already filtered by Physical Inventory?
3 votes -
Running Authorities-Preferred Term Correction job as a report
We would appreciate the ability to run the "Authorities-Preferred Term Correction" job as a report so we could see what changes it would make and then decide if we would want to run the job.
1 vote -
Visibility of extension packs and possibility of selecting them one by one for editing and/or deleting
Extension packs once added to a local MARC-based profile are not visible and cannot be retrieved in any way. It would be much better if each extension pack loaded to a bibliographic profile could be visible to system admnistrators in order to be downloaded from bibliographic profile for purposes of editing and reloading, should the need arise. This feature was part of the tentative future developments proposed by Ex libris back in 2017 (see: internal: 2017 Q1 URM-45100)
68 votes -
Currently Alma does not allow local configuration for "electronic material types" and there are limited choices in Alma for "electronic mate
Currently Alma does not allow local configuration for "electronic material types" and there are limited choices in Alma for "electronic materials types" that can not meet some specific needs of the local libraries. Therefore, the enhancement in Alma should be made to allow local configuration for "electronic material types."
1 vote -
View actually linked bib records in 'Browse bibliographic headings'
When using the Browse bibliographic headings feature, it is not possible to diplay the list of bib records that are ACTUALLY linked to one authority. We can only see the bib records that match with the authority.
On the contrary, when using the F3 index, Alma provides an extra menu in the 'View' option of a bibliographic heading where one can choose between records that match the authority or records that are linked to the authority.
This Idea requests that the same feature be added in the Browse bib heading tool.19 votes -
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 -
Don't link unauthorized headings based on 008 14-16
Alma should take into account positions 14-16 of the 008 of the authority record when "deciding" if it should link to and update a biographic heading.
In the case of the main entry if position 14 is not "b" then make the link and update. If it is "b" it should not link and update.
In the case of a subject entry if position 15 is not "b" then make the link and update. If it is "b" it should not link and update.
In the case of a series entry if position 16 is not "b" then make the…0 votesThis is a gap and will be handled as part of our backlog
-
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 -
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.
300 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.
128 votes
- Don't see your idea?