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.
207 results found
-
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…
327 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
225 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.
-
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.
185 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.
159 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.
139 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 -
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.
120 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.
120 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…
116 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 -
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 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.111 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.…98 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.
92 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 -
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 -
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 -
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…
75 votes
- Don't see your idea?