Last active
December 21, 2015 01:38
-
-
Save damour/6229183 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Stop Words | |
| In search parlance, a “stopword” is a word that’s so common that adding it to a query rarely | |
| increases the quality of results, and frequently decreases it. For example, if you did a search for | |
| “the City of Chicago”, “Chicago” would certainly provide good results. “City” might as well. But | |
| how many billions of documents that have nothing to do with Chicago contain the words “the” | |
| and “of”? | |
| Fortunately, LucidWorks Search understands the concepts of stopwords, and in most cases, | |
| will eliminate them from your query. It also understands how to handle stop words on the back | |
| end so that they help improve relevance (for example, by judging the proximity of two words) | |
| rather than hinder it. | |
| LucidWorks Search starts with a list of several dozen stop words, such as “a”, “and”, “for”, and | |
| so on. You may find, however, that you need to add your own. To do that, click the Querying | |
| menu item, and then the Stop Words menu item. As with synonyms, you can use this interface | |
| to add, edit, or delete stopwords. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment