Add Australian language codes to Primo Back Office
We would like Austlang (Australian language) codes added to the out of the box language code and mapping tables in Primo and for this coding to map to language facets and language display without any additional intervention by institutions. These language codes, used by many Australian libraries, are recorded in the 041$a field(s) of the bibliographic record. These codes do not conform to the three alpha character coding found in ISO639-2 or 639-3. Australian libraries would expect to use these codes in addition to the standard language coding currently available.
The full list of Austlang codes can be downloaded from : https://data.gov.au/data/dataset/70132e6f-259c-4e0f-9f95-4aed1101c053/resource/e9a9ea06-d821-4b53-a05f-877409a1a19c/download/aiatsisaustlangendpoint_001.csv.
Primo offers a way to expose the Australian language using a dedicated facet and display field.
As mentioned in the idea the Austlang codes do not conform to the three alpha character coding supported in Primo/ Primo VE (ISO639 standard), as such it can’t be added to the standard language coding table.
The article below offers a solution for both Primo and Primo VE to add these codes to a dedicated mapping table and crate a dynamic facet that use it.
I agree with other comments here. There is a workaround option but it's not a perfect solution. It would be good to able to retrieve via language facet .
Hi everyone - Don't forget this one when you're voting in Primo NERS 2020 Round 2 right now. Closing August 31st. Submission No. 6710.
This status is NOT correct, as this is NOT 'Already Supported'.
The workaround ‘solution’ of creating a separate local facet:
• Is for local records only
• won’t blend with external content when it is available (hopefully Ex Libris will not deliberately ignore these languages in CDI too)
• will duplicate for local records in the OTB Language facet still as ‘Undetermined’ or ‘Australian languages’ depending on coding
• as well as the key issue of not including these valid and internationally recognised languages in the OTB Language facet and relegating them to a separate facet, as if they have lesser value
I agree with Bronwyn that Primo functionality currently does not actually support this idea as written, which is clearly for Austlang languages to be included in the OTB Language functions, ie the Language facet. They should not be "othered" into their own facet, as if they are not valid languages deserving of the same recognition as any other, which is quite a problematic suggestion.
Bronwyn King commented
UNSW has implemented the described configuration however this is not a full solution. In fact I would describe it as a workaround only. It should be possible to retrieve and display the AustLang codes using the standard display and facet fields. Having separate display and facet fields clutters up the UI and does not permit streamlined discoverability.
A Rowe commented
An example of how this could look can be found on our site where we used manual add facet steps to capture these codes.
I'd like to point out that the implementation of AUSTLANG should capture all languages in 041 $a of a MARC record. Especially when there are more than one $a.
It would also be good for libraries to customise or edit the language terms.
At RMIT we chose to use just the name of the language, but notice that SLQ use the language name and the AUSTLANG code.
Austlang codes are used locally at UWA. Client access via Primo VE is essential.
Peta Hopkins commented
I imagine this would also be of interest outside of Australia where there are institutions with collections focussed on linguistics and language studies.
We would like this in Primo VE also. And I agree with @Kael Driscoll - this should be a mandatory feature
Kael Driscoll commented
We really shouldn't have to vote for this!! It should be mandatory for Ex Libris to accommodate it.
Peta Hopkins commented
Also from this Primo VE institution
Lucy Cammell commented
This is an issue for us at the University of Western Australia too. We are also a Primo VE site and are very keen to have accurate language codes made of use of in Primo VE too.
Very happy to lend University of Queensland support. We definitely would like to be able to acknowledge the correct Austlang languages in the existing Language features of Primo, as standard and expected.
Lynne Billington commented
Yes, this is important to cultural institutions, especially in this International Year of Indigenous Languages.