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.
2 results found
-
Add ISO 639-3 microlanguage names to Alma title search facets
In Alma titles search facets, display the microlanguage name instead of its code. PCC recently approved the implementation of the ISO 639-3 language codes for use in MARC 008/35-37 and also 546$b.
Example: where the language facet for a title search shows...
Language
Chinese (1)
wuu (1)...the following would be more useful...
Language
Wu Chinese (1)16 votesDear all,
We agree that support for ISO 639-3 languages in 041 is important, and are working on a solution for this.
Language marc codes are used in several places in Alma, including controlled vocabulary, advanced language search by selecting a language from a list of languages (which are mapped to marc codes in the metadata) and search facet.
The ISO 639-3 list introduces some complications to several of these workflows, such as languages that are mapped to different codes (e.g. French, which is mapped to fre / fra in the different coding systems). Our solution concept is therefore:
- Introducing a new search index, "Language code", which will allow searching for the language code from the MARC record directly, regardless of the source of code - planned for the coming November release (to be fully operational after the November re-indexing).
- We are working on future plans to offer more comprehensive…
-
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…
275 votes
- Don't see your idea?