GNOME Bugzilla – Bug 491850
Allow option to ignore stopwords
Last modified: 2010-05-20 16:34:13 UTC
Please describe the problem: It is really hard to find files or narrow down the result count because of the use of stopwords in file names. Steps to reproduce: 1. Have an album from Amon Tobin with file amon_tobin-always.mp3 2. Try to find it with two keywords: tobin and always. Actual results: All Amon Tobin songs are displayed. Expected results: Only one file should be displayed. Does this happen every time? Yes Other information: I can see two possible solutions: 1) Use stopwords only when indexing text content of the file. For file names and other meta-data the stopword list should not be used and only the three character minimum may be enforced. 2) Use shorter stopword list. #1 would be my favorite.
tracker-0.6.3, Ubuntu Gutsy final.
Wouldn't adding an option to disable stopwords be superior? * http://bugzilla.gnome.org/show_bug.cgi?id=526344
Can the reporter of this bug set the _version_ so we can target bugs to work on more easily please. We can also have an idea about if these bugs are likely to be obsolete too. If you don't set the version, we are less likely to look at them. Sorry for the spam, but I don't want to say this 88 times on each bug :)
*** Bug 526344 has been marked as a duplicate of this bug. ***
it seems like nowadays, the result is that rather than getting all the results, you get none, which is even worse. martyn, the reporter of this bug only filed this one bug, ever, and that was 2.5 years ago. i think it's unlikely that he or she is going to come back and look at your request to set the version. as i am not the reporter, i cannot set the version, but i am using tracker 0.6.95 right now.
I was stupefied by this as well. How about adding a warning to tracker-search and the GUI if some words of the search query are ignored?
(In reply to comment #6) > I was stupefied by this as well. How about adding a warning to tracker-search > and the GUI if some words of the search query are ignored? We do this for tracker-search in 0.8+, we didn't do this for 0.6 though. The tracker-search-tool could use this technique too.
I added a new "IgnoreStopWords" option in tracker-fts.cfg, by default TRUE (meaning that stopwords are not considered, as currently being done). If set to FALSE, stopwords are indexed as any other word. This patch is in the parser-unicode-libs-review branch.
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.