-
-
Notifications
You must be signed in to change notification settings - Fork 493
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect multilingual searching #5660
Comments
Consider reading #4727 when moving to 4.0.x. Multilingual support is still work in progress. Don't hesitate to contribute! In you case, you may want to define which multilingual fields to search on. You could experiment changing |
Fixes #5660 Solve use case: search with a word in the non default lang title return no result Then the question is what to do next eg. index translation in any field, choose language to search on depending on UI ...
Fixes #5660 Solve use case: search with a word in the non default lang title return no result Then the question is what to do next eg. index translation in any field, choose language to search on depending on UI ...
Fixes geonetwork/core-geonetwork#5660 Solve use case: search with a word in the non default lang title return no result Then the question is what to do next eg. index translation in any field, choose language to search on depending on UI ...
We are working with GeoNetwork 4.0.3 against a PostgreSQL database with multilingual metadata records. All our metadata records are in three languages: Spanish, English and Catalan.
The search engine doesn´t work properly on all the languages, it only works with the main language.
If we make a search in the main language (Spanish), the result is correct:
But if we perform a search in other language, even if the results appear on the dropdown list, when clicking on Search button, no result is returned:
We have also checked with terms that are not on the title of the metadata and GeoNetwork doesn´t return any result. In previous versions of GeoNetwork, all metadata fields were indexed and the terms of the search where looked for in any of them. Can you confirm it is the same for this version? Maybe there is a Elasticsearch setting we are not using.
Thanks for any help provided.
The text was updated successfully, but these errors were encountered: