etianen
commented
7 years ago django-watson delegates to the underlying database's full text seach engine. So it's the database config where you have to look to customize this sort of thing.
PostgreSQL, in general, has a better full text search implementation than MySQL, but both allow a fair degree of customization.
On Wed, 31 May 2017 at 14:36 Bob Donahue notifications@github.com wrote:
I've installed django-watson and am now getting tickets from the stakeholders that "term X isn't coming up, but term Y is...".
In the first case, the "term" they're looking for is 'JFK' (the initials - which does appear in the content in several places, in several objects). I'm suspecting that django-watson filters out "short" words (which makes sense, generally), but it would be great if there is a way to have a "whitelist" of texts that will get indexed. (I can foresee things like "DNA", etc. also being desirable search terms.)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/etianen/django-watson/issues/204, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJFCLM6CMKB9qIWd03py8mn59NtqiB-ks5r_WzxgaJpZM4NrpNE .
I've installed django-watson and am now getting tickets from the stakeholders that "term X isn't coming up, but term Y is...".
In the first case, the "term" they're looking for is 'JFK' (the initials - which does appear in the content in several places, in several objects). I'm suspecting that django-watson filters out "short" words (which makes sense, generally), but it would be great if there is a way to have a "whitelist" of texts that will get indexed. (I can foresee things like "DNA", etc. also being desirable search terms.)