geonetwork / geonetwork/core-geonetwork
index appropriate translation of keywords provided by thesaurus
- Dominant language
- Java
- Stars
- 521
- Forks
- 514
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 19
Description
The facets provide the ability to filter documents using the viewers language. However typing this same text does not find the same documents.
**Describe the solution you'd like**
When indexing the document the "any" field should pull out the appropriate keyword translation as provided by the thesaurus.
**Describe alternatives you've considered**
Adding every translation into the metadata document does not seem like a good alternative to work around this limitation.
**Additional context**
This report is based on the use of thesaurus by the luecene index (rather than specific to any schema).
Contributor guide
Research direction
Start by tracing how thesaurus translations enter the Lucene index and how the “any” field is populated, then compare that path with facet filtering in the viewer’s language. Done means typing a thesaurus-provided translated keyword returns the same documents as the corresponding facet, without requiring every translation in metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100