Facet "language" not working
The facet "language" in Primo is not working correctly. When I choose another language than german or english, e.g. italian, I got german or english titles whose authors have an italian background. This is not making any sense. Especially our chinese students expect titles in chinese when they use this facet. And as it is a global problem I think ExLibris has to find a solution. I checked with several Primo catalogues from other libraries:
e.g.
http://www.getty.edu/research/library/
https://fu-berlin.hosted.exlibrisgroup.com/primo_library/libweb/action/search.do?vid=FUB
https://library.wlu.ca/
http://primo.abdn.ac.uk:1701/primo_library/libweb/action/search.do (they obviously deactivated the language facet already while it is not working)
http://primo.tug-libraries.on.ca/primo_library/libweb/action/search.do?vid=WATERLOO&reset_config=true
http://primo.bib.uni-mannheim.de/primo_library/libweb/action/search.do?vid=MAN_UB
http://onesearch.slq.qld.gov.au/primo_library/libweb/action/search.do?vid=SLQ&fromLogin=true
http://primo.ub.uni-due.de/primo_library/libweb/action/search.do
http://catalogue.solent.ac.uk/primo_library/libweb/action/search.do?vid=SSUVU01
http://whel-primo.hosted.exlibrisgroup.com/primo_library/libweb/action/search.do?vid=44WHELF_ABW_VU1&reset_config=true
http://bvb-new-primo.hosted.exlibrisgroup.com/primo_library/libweb/action/search.do?vid=49BVB_UBG01_VU1
https://hollis.harvard.edu/primo_library/libweb/action/search.do?vid=HVD
a.s.o.
In all libraries I checked there is the same problem that the language facet is not working correctly. So I hope that other libraries will vote for this enhancement request as it is a fatal error in the facets functionality. And I think we should not accept this failure.

-
Manu_Schwendener commented
> Primo checks several code (sub)fields, like 041$b (abstract). It would be great if
> this subfield was excluded from the selection.I agree that a book should not show up as English when only the abstract is in English; this is misleading, and it corrupts the language facet.
-
Manu_Schwendener commented
-
Nancy Babb commented
From recent testing in our Primo VE instance, it seems like for us the language facet and pre-filter work well enough (or relatively so) with Alma records, but it's CDI where the function doesn't seem to work at all. And of course part of the challenge of troubleshooting in CDI is that we can't see what fields are responsible for a problem. In some records, the CTO suggests that the language value may be coming from a field like rft.place, but in many others, there's no sign of the language being filtered within the metadata or full text. Maybe it's coming from metadata in merged records we can't see? Regardless, this is a major problem for researchers who need to either filter out content they can't read or limit to content within their specific language of choice. Can nothing be done about this? It does clearly seem to be a bug that requires development attention and not suitable for enhancement or idea exchange.
-
Manu Schwendener commented
Do you have any examples (URL) of wrong results after using the facet?
-
María commented
I agree. Primo only takes into account the subfield 041$a for the language facet.
We are losing functionality and credibility. -
Rob Feenstra commented
I guess the problem is that Primo checks several code (sub)fields, like 041$b (abstract). It would be great if this subfield was excluded from the selection.