I have a question regarding sorting logic - is there a way to dictate how Searchable Fields are prioritized?
I have three fields I am having issues with. The Name field, the Body field (set to Document Search), and a duplicate of the Body field that I created so that I could enable Phrase Match in addition to Document Search.
The Body field will always need to be set to Document Search so this feature is available.
The Duplicate Body field will always need to be set to Phrase Match as the client wants direct phrases to surface the most relevant entities first that have the exact phrase match in the body.
The issue I am having is that I also need the Name field to be searchable, and none of the Searchable Field settings seem to be suitable for what the client is expecting.
If I have the Name field set to Phrase Match, Document Search overrides the search and the most directly related Phrase Matched results for the Name field do not appear.
If I have the Name field set to Text Search, the Name field shows the best search results, but then the Duplicate Body field won’t show results based on the best Phrase Match.
If the Name field is set to Semantic Text Search or NLP filter, it also overrides the Duplicate Body field in its Phrase Matching, which is very important to the client.
I am looking for a solution where Document Search works to surface relevant featured snippets, and then in the results below, when a search term is Phrase matched with content in the Duplicate Body, that entity surfaces first, and when a search term is Phrase matched with the name of an entity, that result is surfaced first. With the current versions of the configuration I have tried, I can’t accomplish this.
Could anyone please advise on if there is a workaround here? I am happy to send more details offline as well.
Thank you so much!