Advanced NameSearch Capability — Phonetic Error ProcessingTraditional solutions to phonetic errors such as Soundex and NYSIIS used for solving name variations only
deal with phonetic errors. These solutions involved the standardization of easily confused sounds. For example, PH's would be treated as F's. In these cases linguistic rules were generated to phonetically tokenize a name. These phonetically tokenized words served as the basis for name retrieval. In some instances these rules helped find names that were hard to spell, unfortunately, the distribution pattern of common names became skewed. For example, inquiries on John also returned Joan, Jim, Jane, Jimmy, Jenn and other names which fell in the "JAN" phonetic pattern. By aggravating the skew in distribution of names both quality and performance were sacrificed.
NameSearch addresses problems due to phonetics by employing analysis routines to determine the extent
of phonetic tokenization. This enables NameSearch to overcome problems due to phonetics without the
negative consequences incurred with all other methods of name search.
Examples of phonetic tokenization: (taken directly from Robert L. Taft, "Name Search Techniques", New York State Identification and Intelligence):
More Advanced NameSearch Capabilities:
Spelling Error Processing
Rulebase Expertise
Sorting through missing, extra, or noise words
Sifting through word sequence variations
Acronym Recognition
<back>
