Improvements to 7.4 Item Language Field
Currently, the new 7.4 item language field is using the same Languages table used in patron registration. For patron records, the language preference field displays in their account in PowerPAC. Patrons use this field to select their preferred notification language.
If a library wants to add a new language to the Languages table, it will be added as an option for both item records and patron accounts. This is problematic, because many libraries purchase materials in far more languages than they offer notices in. If a library adds additional language options to this table, they risk that patrons will select a preferred language in their account that notices are not offered in.
This can be fixed by:
- Using the MARC languages table for item records instead of the languages table used in patron records, OR
- Using the same table for both patron and item languages, but allowing libraries to select which languages in the table display for either option
-
Rachel Fischer commented
I think that switching the table that is used for the item records could be a very easy fix in the programming.
-
mthigpen commented
What is the point of having a language field in the item record for the language of the manifestation when the MARC language code is present in the bib record?
In any case, if a language field in the item must drive both the language of the manifestation and the print options for notices, individual libraries should have a ability to suppress display for options not available.
-
danielle ruiz commented
Yes, it would help the customer so that they can only select languages we offer and prevent less issues on the backend.
-
Julie Haase commented
This is very problematic for customers who may think we offer notices in languages we don't have. Just because we offer materials in certain languages doesn't mean that our notices are available in this language. They need to be separate tables or have the option to suppress.
-
Carl Ratz commented
We would need a way to suppress patron notification languages that are not supported by the library.
-
Eric Young commented
Yes, We request that the new language selection feature be modified. Some patrons have already selected languages we do not offer, requiring us to contact Innovative Support to fix the records. If this issue is not resolved, we will need to continuously monitor the situation and open support tickets for cleanup. Please consider enhancing this feature so patrons can only select languages we provide, preventing future record corrections and still being able to set item language. We want to avoid an ongoing need to use staff time and Innovative's resources to fix incorrect language selections.
-
Lynn Reynish commented
Yes... using the same table for both patrons and items makes no sense. As Eleanor notes, we could use the field in item records to free up collection codes but not if it adds to the languages available to patrons!
-
Yes, this would make the new functionality must more usable! Using the new item field in item records would allow greater granularity in categorizing items, by freeing up the collection code.