As we've been bringing libraries online with Elastic searching, we've run into a handful of changes to the default mappings. I'm filing this bug to remind us to push some of those back into the community defaults. I'll circle back here with details of changes we've made. Anyone else have changes they'd like to see in the community ES mappings?
+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.