I've come across a case where someone looking for issues with ZoneAlarm used the search term 'zone alarm'. The instances of "ZoneAlarm" did not appear in search results. This would also apply to "book marks", "fire wall", "home page", "web site", etc. SUMO 1.5 worthy?
Adding infix indexing (aka: substring searches) is extremely expensive for the indexer. However, an alternative method is to add a wordforms list with specific overrides, like Zone Alarm > ZoneAlarm book marks > bookmark (singular for stem matching) fire wall > firewall etc.
Component: General → Search
Priority: -- → P3
QA Contact: general → kb-software
Summary: Search should ignore spaces → Add custom wordforms for common multi-word search terms
Target Milestone: --- → 1.5
plug-in -> plugin addons -> add-ons
Created attachment 414112 [details] [diff] [review] add wordforms.txt NB: This patch needs to be applied directly in the scripts/sphinx directory, not from /trunk/. This adds a wordforms.txt and references it in sphinx.conf (also correcting references to stopwords.txt). These .txt files are found in ROOT_PATH from localsettings.py--you may need to move things around.
Attachment #414112 - Flags: review?(morgamic)
Oh, and a good search for testing is "face book". Before adding wordforms, I found 8 results in my database from Nov 18. After adding wordforms it was over 250.
Attachment #414112 - Flags: review?(morgamic) → review?(paulc)
Attachment #414112 - Flags: review?(paulc) → review?(morgamic)
Comment on attachment 414112 [details] [diff] [review] add wordforms.txt Looks reasonable to me. Could you fix the justification for wordforms? It's not aligned with the other stuff.
Attachment #414112 - Flags: review?(morgamic) → review+
r56764. Justified both the wordforms.txt and the instructions in sphinx.conf (will attach).
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Created attachment 414294 [details] [diff] [review] justification
Attachment #414112 - Attachment is obsolete: true
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.