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
-
Copy and paste multiple MARC fields into the metadata editor
We would like to be able to copy multiple lines from MARC records and paste them into the metadata editor so that multiple MARC fields are pasted into the record in one action. This would help us enormously with our workflow of importing MARC authority records from LibrariesAustralia into Alma.
For us, this is necessary because the LibrariesAustralia headings are not in the community zone and are unlikely to ever be included there and Alma does not allow for Z39.50 import of authority headings.
We have this functionality of copying and pasting multiple fields in the LibrariesAustralia Cataloguing Client and…
544 votesDear all,
I believe we now understand the requirement better: To be able to paste a block of text in MARC 21 format, and have Alma parse it and populate the MARC tags, indicators and subfields accordingly.
This is a larger development, but we hope to be able to add a solution for it to our future roadmap.
-
Ctrl-z/Undo in the Metadata Editor
Currently, there is no Ctrl-z/Undo function in the Metadata Editor.
Please add this function.
Use case:
A record is in draft mode and the cataloger deletes a field accidentaly, there is no way of bringing it back.
Or a cataloger works on an exisiting record, makes a lot of changes and only wants to undo the last actions, but not go back to the previous version.346 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…
344 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 -
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 -
add security levels to norm rules
Because all norm rules can be edited by all staff with cataloger roles, there is great room for erroneous changes for rules that are applied to batch jobs. For example, the norm rule that is applied to records being brought in from Z39.50 targets can be edited by any staff member. A single error in the rule can break the z39.50 import process for all staff until the source of the error is identified. Likewise, if we have a rule applied to import profiles and a staff member inadvertently changes it and we load 50,000 records, that could cause huge…
287 votesWe are considering incorporating the idea and effect both templates and rules editing permission
-
Re-sequence MARC fields by each tag when running a normalization rule
Currently, after running a normalization rule on a set of bib records, the bib records display the 5XX fields out of order, e.g. 500, 546, 506 etc. This occurs even after running the CnmarcBibReSequenceTask as fields between 500 and 899 are not sorted, or sorted only by hundreds (this was the information given to us by a member of staff when we reported the issue on the ExLibris Customer Portal).
Having all fields in the correct order would ease any future cataloguing needed on these records, or when staff members view the record for work purposes.
I've attached an example…
264 votesChanging the existing re-sequencing task would impact all libraries, whether interested in this change or not - but we will look into adding a new re-sequencing task that will handle all fields, so libraries will have a choice on which re-sequencing behavior they want to apply.
-
Preferred term correction should flip headings that change tag number
Alma authority control does not handle cases where the bib heading is linked to an authority via a cross-reference, but the preferred and non-preferred terms are in different fields, e.g. preferred term is in authority field 130 and cross-reference in authority is in 410.
Alma should be able to handle this scenario. Currently when the bib heading matches the authority cross-reference, Alma won't correct these and instead puts them on this report: Preferred Term Correction - Bib Heading found no authorized term.
Example bib heading that Alma won't correct:
110/2_ $$a Allied and Associated Powers (1914-1920). $$t Treaties, etc. $$g…
249 votesWe will add this improvement to our roadmap
-
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.
-
Add notifications to Alma reminders
I appreciate the addition of the Reminders in Alma, but I think it would be even more useful if reminders could trigger email notifications when the reminder date has arrived.
219 votesA new task will be added to the tasks widget, alerting catalogers when reminders' date arrives.
-
Indication that shows I edited an open record
Icons in MD-Editor only show if a record has been saved or not. I would like to have an indication to see if the record has been edited by me after I opened it.
212 votes -
controlled vocabulary list upload
Hi,
Instead of create term by term when working with controlled vocabulary, enable the option of upload an excel file or any csv file that will do that.
172 votes -
It would be helpful if there were an option to "print MARC record" within the MD editor and from the Repository Search.
We sometimes have need of a hard copy of the MARC record for tracking certain workflows. One such example is for making notes about title changes and tracking them across several records. It would be nice if there was a "print full record" option, both in the MD editor and in the repository hit list. Right now, we need to either do print screens or do a screen capture and print from that. Thank you!
165 votes -
Allow cataloguers to choose which names are linked to authority files
Allow cataloguers to choose which names are linked to authority files
This is important because the all on or off automatic linking creates links for unqualified names and catalogers want the option to verify and thus link names in the way it is done in connexion.
This when the authority data is updated - every record attached to it is improved and unqualified or non-established names do not get affected.
145 votes -
Job or tool for extraction of related bibliographic records
We would like the ability to get a hold of or extract the related bibliographic records in bulk based on a set of (other) bib-records.
Alma already now automatically displays related records in "other details". We understand that the links are built based on bibliographic data in the MARC linking fields: 773, 774, 777, 786, 800, 810, 811, and 830 (subfield w,x,z).
An example of a related record is a title within a monographic series. In this case, the bib record for the single monograph has a 830 $w with the MMS-ID/system number of the superordinate bib record.
We would…
135 votes -
Suppress bib record when no active portfolios/services
If a record has zero active services, it should be automatically suppressed in Primo. When we choose to use the CDI records for a collection instead of the CZ records, there is a button to "change to CDI-only full text activation." This suppresses the service, but it does not suppress the bib records. We have to manually run a job on each collection to also suppress the bib records. Most of the time this is fine (even though it's an extra step), but if some of the CZ bib records overlap with other collections, we don't necessarily want to suppress…
133 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 -
Allow renaming of normalization, indication, and merge rules
Please allow renaming of normalization, indication, and merge rules. Right now you can only duplicate the rule and change the name of the copied rule.
126 votes -
Browsing Dewey in MD Editor
We noticed that in Metadata editor the browsing in the 676 - Dewey field isn't available: we would like add the feature to scroll the lists from other records, as happens for the 6xx fields (subjects) and 7xx (authors).
114 votes -
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
- Don't see your idea?