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.
122 results found
-
Add a linking job for mass linking of NZ records to IZ
Currently the only way to use records from NZ in an IZ is to search them in the NZ and perform an action like "order" or "link" on every single record one by one. There are, however, situations where an IZ wants to use a bulk of records. For this purpose we need a possibility to link records in bulk and create inventory for the linked records.
We imagine a linking job that takes as an input a logical or itemized set of records saved from a search in the NZ. The linking job can create physical and electronic (and…
112 votes -
Create a new an authorities search index “Matching Information” (or the like) for field 885
As Alma GND User Group we represent staff users that are tasked with data management in the Integrated Authority File (GND), the most widely used authority file in the German speaking library community.
We would like Ex Libris to introduce an authorities search index that makes the content of MARC 21 Format for Authority Data field 885 available for search purposes.
As a QA measure several different algorithms are applied to the content of GND to find potential duplicate records and mark these candidates in field 885. In cases where the confidence value does not reach a certain threshold, the…106 votes -
Automatic dismissal of corrected authorities from the Authority Control Task List.
Automatic dismissal of corrected authorities from the Authority Control Task List.
Improve the Authority Control Task List linking functionality so that when an authority is upgraded/corrected in the metadata editor, it is automatically dismissed from the Task List. Items are added to the Task List before an institution has had a chance to upgrade the catalogue record. Many of these authorities will routinely be upgraded at the cataloguing stage. The need to then manually remove substandard authorities from the Task List which no longer exist in the bibliographic records adds a huge burden of extra work, especially for large institutions.…101 votes -
Identify headings linked to authority records in Simple Record View
I frequently consult the Simple Record View page of bibliographic records when working on the Authority Control Task List. This view, however, does not indicate which headings are linked to authority records and which are not. The only place in Alma to confirm this is through the Metadata Editor.
This proposal recommends adding a marker (such as the binoculars icon found in the Metadata Editor) to those fields in the Simple Record View with headings linked to authority records. This would save a step in the Task List review process, not to mention being helpful to any Alma user looking…
97 votes -
Prompt message if you have not saved a record before releasing
Currently if you edit a record and then go to release it before you have saved, you do not get any kind of prompt asking if you want to release it without saving.
There is also no prompt message if you try to save a record that has blocks to let you know that the action was not done.
95 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 -
Reminders : extend the Add reminder functionality to other roles (only Cataloger now)
Reminders functionality could be more effective if extended to other roles than only cataloger role. At least Electronic and Physical inventory operators should be able to add a reminder on a Bib record in a repository search result.
The managing of reminders from Cataloging menu can be limited to catalogers.82 votes -
Sorting Authority Task List
It would be highly helpful to have a sorting filter in the Authority Task List that would allow us to sort the list by Fields (e.g. 100's,600's, 700's, 830's,): Personal Names, Corporations/Conferences, Subject, Title, Uniform Titles, and Series. This way work loads can be created and assigned for these specific areas. As things are now, all items are mixed together and it takes far too much time to find/create a single list.
80 votesWe will consider addressing the requirement as part of the Authority Control Task List enhanced UX in the Alma roadmap: https://knowledge.exlibrisgroup.com/Alma/Product_Materials/010Roadmap/Alma_Roadmap_Highlights_-_January_2021/Metadata_Management#Authority_Control_Task_List_-_enhanced_UX
-
Position sensitive NRs (Normalization Rules) - ISBD punctuation
ISBD punctuation is determined by the following subfield.
For example:
In 245 the subfield preceding $$b must end in one of the following:
1. space + colon
2. space + semicolon
3. space + Arabic semicolon (if your cataloging language is Arabic)
4. space + equal signThe NR syntax currently does not offer any straightforward solution for correcting ISBD punctuation.
We request the development of an NR function that will suffix the subfield with a string based on the subfield that follows it, including the case in which a subfield is the last one.
I think it would be…
78 votes -
search filters and better results display in the "search external resources" function
When we are searching WorldCat for a record to match a newly-ordered title, we often find duplicate records. The current search results display makes it difficult and time-consuming to choose the best record.
The external resources search would be much improved if we could limit search results by the language of cataloging (040 |b) and format. This would save us having to wade through multiple vendor records that aren't even in our local language of cataloging, and multiple records for resources in a format other than the one we are looking for.
It would save us a lot of time…
78 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 -
Alma MDE: Filter by Marc21 field and subfield
As a cataloger I would like to have the possibility in MDE to filter the Marc21 data by field and subfield
value to have a better overview over the current part of the data which is to be checked/edited.
Further I would like to have the possibility to quick access filters which i use often.Proposal:
Add a possibility to filter by field and subfield, e.g. by having an input form for the Marc21
field (rows filtered by "Begins with {value}") and for the Marc21 subfield (rows filtered by
"Contains {value}"). The filtering should by done by "AND" condition. (See…73 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 -
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 -
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 -
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 -
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 -
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 -
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
- Don't see your idea?