A comprehensive guide to boolean logic when searching for content
Lexer Listen allows you to build your queries using boolean language, giving you the flexibility and power to ask all types of questions of your data. Every time you search in Google, you’re using boolean logic. Our products use this same approach, and the options below will help you understand that control.
There are 8 modifiers that you can use when crafting your search.
Notes on using tilde
Tilde is used when you’re looking for words near to other words. The phrase “Gorman Raincoat” expects all the terms in that exact order. However, a proximity query allows the specified words to be further apart or in a different order in a sentence. Just add a ~ after your usual phrase query and specify the maximum number of spaces you’d like between the words. Example: “Gorman Raincoat”~6 would pick up posts like “Gorman makes the best Raincoat around”, “I went to Gorman after pay day and bought a Raincoat” etc.
Tilde is used when you’re looking for words that are similar to, but not exactly like, your search terms. For example, searching for Lexer~2 will return terms that are a maximum of two changes from the query. A change includes the insertion, deletion or substitution of a single character, or transposition of two adjacent characters. Lexer~1 should be sufficient to catch 80% of all human misspellings. This is very handy if your customers are often misspelling your brand name - i.e. we get Lexar a lot!
UTF-8 characters (eg. é, ß, ü) will only match exactly, even in cases where an “equivalent” ASCII character exists. For example, touché will not match an Object containing “touche”.