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.
204 results found
-
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 -
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…
296 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,
We are looking into this idea, and it includes several enhancement requests with varying complexity. Could you please provide a prioritized list, so we can better asses these requests according to complexity and priority (alternatively, you might consider opening dedicated ideas - like in Hanoch Roniger's comment below - to gauge the need in the community for each feature)?
Thanks!
Lili
-
Decouple the bib-level material type of Music into Scores and Sound Recordings
The bibliographic material type of Music inexplicably combines scores (Leader/06 c or d) and sound recordings (Leader/06 i or j) into a single facet. This makes no sense and makes standard statistics reporting extremely difficult as scores are usually reported with books (they are, after all, pieces of paper bound between covers) whereas sound recordings are usually reported with other media. Scores should be separated out as its own bib-level material type.
188 votesThank you for this ideas exchange request.
For the purpose of clarification:
Alma uses (among others) two levels of faceting the bibliographic records: Material type and Resource type.Regarding the Material Type: There are seven different distinct bibliographic material types in Alma, and this corresponds to the seven different distinct bibliographic material types used by the MARC standard. These MARC standards are explained at https://www.loc.gov/marc/bibliographic/bdintro.html under section “Scope of the Bibliographic Format”. Ex Libris will leave these distinct seven formats, and not add or subtract from them. This is because there are seven distinct formats in the MARC standard. For this reason we will not add another format or change the name of an existing format. Each bibliographic record has one bibliographic material type. The Material Type is considered “Music” if the LDR pos. 6 is one of the following: c d i j. This is explained in the Ex…
-
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!
162 votesDear all,
Since this idea was posted, the "Print Bib records" cloud app was developed, and support for it was added in the MDE. It is now possible to print one or more records from the MDE, in multiple formats, as described here: https://developers.exlibrisgroup.com/blog/how-to-install-and-use-the-print-bib-records-cloud-app/
Does this answer the need raised in this idea? If not, could you provide more details on what it is you're missing in the app?
Thanks!
-
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.
138 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.
138 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…
122 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…
115 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.
114 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.
113 votes -
Add ORCID ID to CZ Authorities vocabularies search
Field 0247 $$a XXXX-XXXX-XXXX-XXXX $$2 orcid used in authority records and is currently not searchable in CZ authority vocabularies.
Using a unique identifier when searching for name authority records will improve the precision of authority search results. It would also save the time and effort currently invested in establishing the correlation between a name and its authority record.108 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…108 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).
108 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 -
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.…96 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.
87 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.79 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…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.
74 votes
- Don't see your idea?