How To Change The Behavior Of Search Spell Checking And Add Custom Corrections (Doc ID 1448370.1)

Last updated on MAY 11, 2017

Applies to:

Oracle Knowledge - Version 8.1.3.1 and later
Information in this document applies to any platform.

Goal

This article explains the operation of Search Indexer/Runtime spell checking, how the default Out Of The Box (OOTB) behavior can be modified and custom corrections included.

The 8.5 Spellchecking function is slightly different than older function.  Here is the logic for 8.5:

The question is parsed into a set of tokens.  Each token is checked for spelling in this order.

1. Check ontology - is the token a synonym in the request locale?  If yes the token is not changed at all, it is considered correct and steps 2-4 are skipped.  If it is not a synonym then go to next check in 2.

2. Check dictionary spell-check list - is token in the dictionary exceptions?  This function is to correct tokens that might be wrong in wintertree or different for your business.  If the token is found here then it is changed to match the spell correction specified and 3 and 4 are skipped.  If the token is not found here then go to the next step, 3.

3. Check index - is token in index with min frequency? if the token is commonly used in the documents it is considered a valid word and the wintertree check is skipped.  If it is still not found in high enough frequency then it is checked in wintertree, 4.

4. Call Sentry/Wintertree - is token spell-corrected? if yes, correct it.

Done spellchecking.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms