Closed laurenbarker closed 7 years ago
Does using a normalizer like this mean the sources facet/donut will be all lower case?
Ew. Yes it does.
Maybe we should add a sources.exact
field for aggregations/filtering? Then once preprints/dashboard/whoever have switched over, sources
could be text
, which would be nicer for typed queries.
That would probably make the most sense.
@chrisseto would you be okay with splitting the case insensitive search stuff into two releases? One for adding an exact field for sources and another for making the sources field a text field. It would probably be easier than coordinating a release with preprints and the dashboard.
Would it make more sense to use an analyzer/tokenizer given that they are officially supported?
@chrisseto, analyzer/tokenizer can't be used on a keyword field
Keyword fields are only searchable by their exact value.
So are you saying your on board with switching to a text field or am I missing something?
@laurenbarker Do you remember what the final decision on this was?
@chrisseto, we still haven't heard back from product on this one. I would say move it out of the sprint and close the PR until a decision is made.
@laurenbarker alright, thank you!
Purpose
Allow case insensitive search for sources.
Changes
Add a normalizer for keywords.
Side effects
Need to re-index everything.