Re: "Advanced" Search Algorithm
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 69877
interpreted = N
texte = I have two ideas for guessing mis spellings. 1. Have a not so skilled typer actually type of the words without letting them look at the keyboard. Someone like me who can't type without looking at the kwyboard. You will ond up with natural mistakes like the previous two I just made. kwyboard=keyboard and ond=end. Note that the o/e replacement is a dyslexia issue whereas the w/e is a bad typer issue. 2. Have someone bring in their young kid and ask them to type out words as they would spell them using phonetics. :o) Matthew A Perosi Psi Prime, Inc. http://www.psiprime.com 323 Union Blvd. Totowa, NJ 07512 P: 973.413.8210 F: 973.413.8217 Donovan Brooke wrote: > Ki Song wrote: >> We are currently able to search on all the fields in our inventory >> database. >> >> Is it possible in WebDNA to search for "misspelled" words easily? >> >> For example, if a customer wanted to search for knife, but accidentally >> spelled it as knfie, is there a built in function that would "know" >> that the >> customer intended to search for knife OR at least an intelligent guess? >> >> Thanks! > > Ki, > > A few quick ideas off the top of my head.. > > 1.) you could use the "begins with" comparison and parse out the first > two characters of the search string.. > > 2.) You could create a database of common misspelled words related > to your site content and reference this database before searching > the live database. > > So, a keyword term of nife (god forbid) would be found inside > the misspelled database field value for "knife"... then "knife" > would be used for the search term instead of knife. > > 3.) perhaps the best/easiest option would be to keep a "mis-spelled" > words field > in your products database. This "mis-spelled" words field would > be transparent to the customer and would only be used for finding > that record. Mis-spelled words could be added upon creating the product, > or editing a product. > > The trick with the later two (though they are most accurate) is > anticipating the mis-spelled words... > and knowing the way I spell, it is a trick indeed! ;-) > > Donovan > > > > > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
I have two ideas for guessing mis spellings. 1. Have a not so skilled typer actually type of the words without letting them look at the keyboard. Someone like me who can't type without looking at the kwyboard. You will ond up with natural mistakes like the previous two I just made. kwyboard=keyboard and ond=end. Note that the o/e replacement is a dyslexia issue whereas the w/e is a bad typer issue. 2. Have someone bring in their young kid and ask them to type out words as they would spell them using phonetics. :o) Matthew A Perosi Psi Prime, Inc. http://www.psiprime.com 323 Union Blvd. Totowa, NJ 07512 P: 973.413.8210 F: 973.413.8217 Donovan Brooke wrote: > Ki Song wrote: >> We are currently able to search on all the fields in our inventory >> database. >> >> Is it possible in WebDNA to search for "misspelled" words easily? >> >> For example, if a customer wanted to search for knife, but accidentally >> spelled it as knfie, is there a built in function that would "know" >> that the >> customer intended to search for knife OR at least an intelligent guess? >> >> Thanks! > > Ki, > > A few quick ideas off the top of my head.. > > 1.) you could use the "begins with" comparison and parse out the first > two characters of the search string.. > > 2.) You could create a database of common misspelled words related > to your site content and reference this database before searching > the live database. > > So, a keyword term of nife (god forbid) would be found inside > the misspelled database field value for "knife"... then "knife" > would be used for the search term instead of knife. > > 3.) perhaps the best/easiest option would be to keep a "mis-spelled" > words field > in your products database. This "mis-spelled" words field would > be transparent to the customer and would only be used for finding > that record. Mis-spelled words could be added upon creating the product, > or editing a product. > > The trick with the later two (though they are most accurate) is > anticipating the mis-spelled words... > and knowing the way I spell, it is a trick indeed! ;-) > > Donovan > > > > > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Matthew A Perosi
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Escape the Root! (2002)
Photo Album (2000)
$append (1998)
Reversed words (1997)
Error Log.db --however (1997)
webten vs. webstar (1998)
problems with 2 tags (1997)
WebCat2b13MacPlugIn - More limits on [include] (1997)
Enhanced Master Counter? (1997)
Not really WebCat (1997)
Configuring E-mail (1997)
WebDNA won't start on reboot (2003)
Re1000001: Setting up shop (1997)
[WebDNA] Stores (2013)
Next (1997)
WebDNA-Talk Digest mode broken (1997)
Softball questions (2003)
Emailer Problem (1999)
Memory Error message (1998)
WebTen Memory Error with Plug-In (1998)