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.
49 results found
-
Add Release Displayed Records in List to Record Actions menu and a keystroke combination
In the metadata editor, the option to release all displayed records in the record list has only one button which is not accessible by a keystroke. This makes the action less accessible to different users, and is also challenging to document for library staff without including visuals.
This button, with tooltext "Release displayed records in list," should also appear in the Record Actions menu in the section with other release records options. At minimum, the function should continue the current behavior of releasing the records in the selected records tab. Though it would be useful to have an option to…
8 votes -
Improvements for the MDEs left pane
The left pane in the MDE is a very helpful tool for navigation in daily business. With the following improvements it could be even more helpful:
- Customization of the display of the different databases in all the tabs (records/templates/rules): it would be very helpful if one could select only the databases that are necessary for the daily work for display (example: I have in the record tab 14 different databases of which I only need 4, and one that I need is only accessible through the drop down menu); if a selection is not possible it would be helpful…80 votes -
Create a set from records held in the Metadata Editor
It would be useful to be able to save all of the records that you are working on in the metadata editor as a set to come back to later.
For example, this would be helpful when working on a bound with where you need to work on several records at the same time and need to add links across the records. At the moment, if this work is not completed and we need to return to it later, we would then need to create an itemised set by searching for and adding each record individually. Instead, it would be…
76 votes -
Abilty to edit the authorities from CZ
In bibliographic records and in Browse Bibliographic Records you can check the information of the linked authority - also CZ authorities. The possibility to take the authority directly in edit mode, as you have the right to edit authorities of the CZ
118 votes -
Prevent deletion in Community Zone based on field or value in specific field.
Blocking deletion in Community Zone based on field or value in specific field. Possibility to be definded as a parameter for each CZ vocabulary.
106 votesAs you all know, the Community Zone content is shared among all Alma customers, each with different requirements. Therefore, I’m not sure this request would be acceptable to the wider Alma community. That said, if there were a consensus on a closed list of fields that CZ bibliographic records should be restricted from deleting per MARC profile, this capability already exists and is managed by the Ex Libris Content Operations team. Unfortunately, this is not available for authorities. Do you think such a consensus could be reached?
-
MDE Search Resources mask should be empty
When opening the Search Resources mask in MDE, the previous search is still in the data mask. For us there is no benefit for this behavior and we would like to have an empty mask and not to clear the mask every time before starting a new search.
(If other libraries need this opportunity, we would suggest to make the default settings for this mask customizable)72 votes -
Add option to Quick Cataloging Template for Publish/Don't Publish to OCLC.
Add a checkbox option to the Quick Cataloging Template for Publish/Don't Publish to OCLC. This would prevent brief records for items created by circulation staff for professor's personal copies from being sent to OCLC and added as new records.
20 votes -
Authority data: first indicator in the bibliographic record
Now we have many mistakes in our bibliographic records in the settings of the first indicator by connecting with authority data (GND, IdRef, ..). It would be great to have an automatic process, which takes over the first indicator of the authority data to the bibliographic record when you select the authority heading.
What you have then is the following: First indicator, preferred term and authority identifier are taken over from the authority record to the bibliographic record by using “select” in the index view of the authority record.
It would be great, if this is implemented for 1XX/6XX/7XX in…148 votesI wonder if this request takes into account that certain fields in the 1XX/6XX/7XX have different first indicator definitions in the MARC21 standard for Bibliographic fields compared to their corresponding Authority fields. In such cases, copying the first indicator from the Authority to the Bibliographic heading would result in incorrect data. Is the reqeust is about Names only? Hans, I would recommend consulting with AAFG group for a details spec where this requested behavior is valid to which fields.
-
Contribute to CZ records : GND Authority File for 1XX/7XX Fields
A library wants to enhance CZ Bibliographic Records, one is asked by ExLibris to comply to their cataloguing standards (Alma Community Catalog: Cataloging Standards, Policies, Rights, and Responsibilities (exlibrisgroup.com)). On page 7 of those standards it is stated:
"Since we have a one record policy in the CZ, the issue of languages has been the most challenging part of the solution. The current decision is that the language of the item dictates the language for cataloging. (…) Similarly, the forms of name used as authorized access points in the record should be consistent with the language of cataloging--– LCNAF if…
21 votes -
Duplicate Title Analysis should include match option for Unique OCLC number match method
The Duplicate Title Analysis job and report currently include matching on only one attribute at a time, rather than on all of the attributes that might be covered by a given match rule. For instance, matching on system number provides only matches between 035$a in different records, while the Unique OCLC number match method covers both 035$a and 035$z. As a result the duplicate title analysis report is missing records that would otherwise be found by an import profile or the match method in the network zone.
26 votes -
Indication rule that checks if subfields are in the same field
Currently it is not possible to write an indication rule which checks the subfield a and b of a field only when both subfields are in the same field and not in repeated fields of the same record. Both of the following records are treated the same when looking for a subfield a "mercury" and subfield b "venus" in the 690 field:
Record 1:
690 $$a mercury $$b venusRecord 2:
690 $$a mercury $$b mars
690 $$a earth $$b venusI'd appreciate an option to distinguish if I'm looking for subfields in different fields or in the same field.…
61 votesI recommend applying XSL normalization rules with the required logic and integrating them into the Upon Save normalization process.
-
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…76 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…
66 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…
65 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)
67 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,
60 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…
64 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…128 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…
73 votes
- Don't see your idea?