Summary: | Update default Elastic mapping | ||
---|---|---|---|
Product: | Koha | Reporter: | Andrew Fuerste-Henry <andrew> |
Component: | Searching - Elasticsearch | Assignee: | Nick Clemens (kidclamp) <nick> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P5 - low | CC: | ephetteplace, jonathan.druart, joonas.kylmala, kyle, sbcornell |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Attachments: | ES mappings that were not included in default setup but are used by OPAC searches |
Description
Andrew Fuerste-Henry
2020-12-29 15:12:28 UTC
+1 I'd love to see good defaults for the libraries just starting out with Elasticseach! Andrew, maybe we should ask the list before working on this? Created attachment 145074 [details]
ES mappings that were not included in default setup but are used by OPAC searches
I reviewed all the searches that our OPAC generates and made sure that the fields they used were indexed. I found MANY missing indexes. Some of the searches SEEMED okay but were not because one of the 3 fields used in the automatically generated search was missing. So no one has to go through it again I will share the indexes I've added in an attachment.
NB: the search that the OPAC generates that might use the 775at is still under discussion. We're not sure which index is best when the search generated is ti,phr.
|