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
-
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
-
New Metadata Editor templates: editing template v. creating new record
Previously, when opening a template in the classic Metadata Editor (MDE), a click on the template name from the list of templates would give a list of options, including creating a new record: there was no doubt as to whether you were creating a new record from the template, or editing the template itself.
However, with the new MDE, clicking on the template name takes you straight into editing the template itself. Creating a new record from the template now requires a right click first to get to the options menu, but this is not at all obvious. It is…
64 votes -
The text font ,font size and color of Metadata Editor
1.When using Metadata Editor, the font size and color of the editing area are not friendly to the editor.
2.The text in the editing area needs to be enlarged by 150% in the browser to make it convenient for users to work for a long time
3.The text color or font in the editing area causes the black text to look like gray, which makes it inconvenient to check the bibliography
4.Can workers modify the Metadata Editor environment to make them comfortable working environment, such as the font size, font type, and font color in the editing area?
This can…
61 votes -
Metadata editor: Enable moving up and down within a field using arrow keys
It would be nice to be able to move up and down within a field using arrow keys in MDE. For example, when a lengthy 505 or 520 MARC field has many lines, the cataloger must now move to the desired line using either mouse or left/right arrow keys, since pressing up/down arrow causes the pointer to move to the previous/next field.
My suggestion is that the pointer should be able to move within the field using up/down arrows and move only to the previous/next field when the pointer is on the first/last line of the field.
Using up/down arrow…
345 votesDear all, we are currently working on a design concept for a new form interface option for cataloging, which will make it easier to navigate long fields and subfields - we will take this request into account as part of this design. See our "Form Editing for MARC 21 Bibliographic Records" roadmap plans for more information: https://knowledge.exlibrisgroup.com/Alma/Product_Materials/010Roadmap/Alma_Roadmap_Highlights_(2024-2025)/Metadata_Management#Form_Editing_for_MARC_21_Bibliographic_Records
-
Subdivided LCSH headings should be flipped by Preferred Term Correction
Preferred Term Correction is not flipping all LCSH headings when the authority record changes. If there is an authority record that has a subdivision, it is only flipped by PTC if the heading in the bib has no additional subdivisions. This means there is a significant gap in the PTC process that requires manual attention and handling, which is unsustainable. The PTC process needs to be more thorough.
For example, this LCSH:
$a Germany $x Politics and government $y 19th century
was updated by LC to be:
$a Germany $x Politics and government $y 1789-1900
When the authority record changed,…
314 votes -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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 -
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
- Don't see your idea?