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
-
Follow NACO rules when linking bib headings (reduce number of "ambiguous" headings in ACTL reports)
When linking bib headings, Alma does not follow NACO comparison rules when checking for ambiguous headings. This results in numerous headings not linking at all, and being reported as ambiguous. This reduces the utility of Alma's authority control process, because there are too many headings to link manually.
Examples of headings that Alma won't link because they are "ambiguous"
- Peabody Essex Museum
Peabody & Essex Museum
Ciné+ (France)
Cine France
Mohammad, Ali
Mohammad Ali (a cross-reference in the authority record for Ali, Mohammad)
McFarland & Company
McFarland Company (cross-reference in authority record for J. Horace McFarland Company)
Authority File Comparison…
7 votes -
Add parameter to keep bib records with digital contents while deleting inventory to Withdraw physical items job
Currently the Withdraw physical items job does not check for the presence of digital contents (or inventory), and there is not an option to delete the item and holdings records, while keeping the bib records with digital representations attached to. Please consider. Thank you!
1 vote -
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.…
55 votes -
Ability to search for duplicate varying text in two different Marc fields
It looks to be possible to find duplicate fixed text values within subfields of the same MARC field (and possibly between two MARC fields), but there doesn't seem to be a way to build a rule that would identify two matching fields for varying text by record, for example, finding a record that had the OCLC number duplicated in another field (but which the number would obviously vary title by title). The asterisk only seems to work if you have some kind of fixed piece shared among records and not if the whole field varies.
5 votes -
Add the Thesaurus for Graphic Materials to the CZ
Please consider adding this authority vocabulary to the CZ as it is used to enhance records of graphic materials such as photographs, drawings, and other visual works.
https://www.loc.gov/rr/print/tgm2/downloadtgm2.html16 votes -
Urgently needed hotkey of remove subfield
I really need a hotkey to remove subfields. Oh, please save my backspace button.
1 vote -
Urgently needed hotkey of remove subfield
I really need a hotkey to remove subfields. Oh, please save my backspace button.
3 votes -
traditional Chinese be transcribed into simplified in MDE
Can bib. records in traditional Chinese be transcribed into simplified Chinese in MDE by one click or by normalization rule? like what MS word can do.
1 vote -
Title search - index the 245 field on its own
My library catalogs most new material according to the international cataloging standard, Resource Description and Access (RDA). One requirement of RDA is that each work is given a unique access point. When cataloging a new work, our catalogers must search our database to determine if their 245 field value (subfields a, n, p) is unique. This is impossible for them to do with the out-of-the-box search fields in Alma when their title is only one or two words long because the Title field searches 38 MARC fields and over 100 subfields. In our database, a basic title search of the…
18 votes -
Add in the configuration the ability to make the search default of the authorities to be in CZ all the time.
Hello,
When searching in the authorities, Alma jumps from IZ to CZ and vice versa in different menus.
For institutions that do not maintain local authority file, it is frustrating that the search needs to be changed to CZ when Alma “decides” it should be in the IZ.
If there was a check box in the configuration that would enable us to choose that the search default in the authorities would be in the CZ all the time, it would be greatly appreciated.Thanks.
Dafna1 vote -
Running Authorities-Preferred Term Correction job as a report
We would appreciate the ability to run the "Authorities-Preferred Term Correction" job as a report so we could see what changes it would make and then decide if we would want to run the job.
1 vote -
Subject Index search: the comparison is not to contain a certain string but the entire field
PrimoVE enriches the search with terms from the 150 or 450 fields of the authority record when searching by subject index. Still, we would need the match not to contain a certain character string but to match the entire 150 or 450 fields with the subjct being searched for with an exact search in PrimoVE.
This would prevent subjects sharing part of the string (but not all) from appearing in an exact subject search in PrimoVE.For example, if we search for records on "Right to life" in Subjects index, Primo VE also retrieves records on "Right to private life"…
4 votes -
MD Editor: Release specific record(s) from another cataloger
Currently, the MD editor has an option to release ALL records from another cataloger. It would be ideal to have more granularity in choosing records to release. A common use case: Someone assigns a record to another cataloger but then realizes they should have edited something first. Rather than release all of the other cataloger's records (potentially catastrophic), it'd make sense to have the option to release the single record they need to edit.
1 vote -
MD editor: Release specific record(s) from another cataloger
Currently, the MD editor has an option to release ALL records from another cataloger. It would be ideal to have more granularity in choosing records to release. A common use case: Someone assigns a record to another cataloger but then realizes they should have edited something first. Rather than release all of the other cataloger's records (potentially catastrophic), it'd make sense to have the option to release the single record they need to edit.
1 vote -
Currently Alma does not allow local configuration for "electronic material types" and there are limited choices in Alma for "electronic mate
Currently Alma does not allow local configuration for "electronic material types" and there are limited choices in Alma for "electronic materials types" that can not meet some specific needs of the local libraries. Therefore, the enhancement in Alma should be made to allow local configuration for "electronic material types."
1 vote -
Add Library & Location Facets to Authority Control Task List
Could we add facets for library and/or location to the Authority Control Task list when already filtered by Physical Inventory?
3 votes -
Ensure that CZ & CDI Metadata is Linked Data Ready
I was advised by the Linked Data Group to post this idea here because I submitted the following for the LOD Working Group webinar in December:
Broader strategic and commercial alliances required to ensure that data is ready to be linked?
To engender confidence in CZ and make it linked-data ready, why don’t the Company do business with e.g. Backstage Library Works for authority control clean-up and maintenance?
Metadata is a global commodity so all stakeholders have responsibility for creating, sharing, enriching and maintaining it, and of course there are costs for all of these elements which we could share.
…
13 votes -
Some Important Shortcuts in Alma and OCLC -- Consider User Friendly Changes
Some often used shortcuts in Alma are similar to those used in OCLC Connexion, except for their function. Control + D will delete a record in Alma (and any keystroke after the shortcut is interpreted as confirmation by the popup window), but in Connexion the same shortcut adds a delimiter $.
F8 keyboard function in Alma adds a field, but in OCLC it produces and adds a new record. Many of us, especially special collections catalogers use first OCLC and then Alma for local notes.
Please, consider shortcut changes, which support both important platforms, used daily by many of us.…7 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 -
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
- Don't see your idea?