Endeca Experience Manager Rule - What happens when Auto correction happened for search term?
Spelling Correction operates by computing alternate spellings for user query terms, evaluating the likelihood that these alternate spellings are the best interpretation, and then using the best alternate spell-corrected query forms to return extra search results.
For example, a user might search for records containing the text "Dressas". With spelling correction enabled, the Endeca MDEX Engine will return the expected results: those containing the text "Dresses".
What happens if auto correction happens during keyword search :-
1. Suppose, we create a rule in Endeca experience manager with Location search term "dresses".
2. User enters a search term as "dressas".
3. For First keyword, "dressas" would auto corrected to "dresses".
4. Rule created as part of step 1 would be triggered if the user searches for "dresses" or any term that would be auto corrected to "dresses".
5. Same thing applicable for stemming as well.
For example, a user might search for records containing the text "Dressas". With spelling correction enabled, the Endeca MDEX Engine will return the expected results: those containing the text "Dresses".
What happens if auto correction happens during keyword search :-
1. Suppose, we create a rule in Endeca experience manager with Location search term "dresses".
2. User enters a search term as "dressas".
3. For First keyword, "dressas" would auto corrected to "dresses".
4. Rule created as part of step 1 would be triggered if the user searches for "dresses" or any term that would be auto corrected to "dresses".
5. Same thing applicable for stemming as well.
Discussion (0)
Technical questions and architecture discussionsNo comments yet. Have a question about this architecture pattern? Leave a response below.
Join the Discussion