Mercurial > p > roundup > code
comparison doc/user_guide.txt @ 6613:2eec7a500333
Doc updates for indexers.
change word size max from 25 to 50
phrase search syntax updated
clear up wording for automatic selection of xapian/whoosh
link user_guide to admin_guide for finding syntax for native_fts
searches.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Mon, 07 Feb 2022 22:52:03 -0500 |
| parents | 828e2eaee7cd |
| children | e7b4ad2c57ac |
comparison
equal
deleted
inserted
replaced
| 6612:d05800c6bdfa | 6613:2eec7a500333 |
|---|---|
| 375 @filters=status,keyword& | 375 @filters=status,keyword& |
| 376 @columns=title,status,fixer | 376 @columns=title,status,fixer |
| 377 | 377 |
| 378 Full text search using the xapian, whoosh and native indexers treats | 378 Full text search using the xapian, whoosh and native indexers treats |
| 379 the search query as a series of space separated words. Any word less | 379 the search query as a series of space separated words. Any word less |
| 380 than 2 characters or more than 25 characters is discarded. Also a | 380 than 2 characters or more than 50 characters is discarded. Also a |
| 381 stoplist is used to remove common words like "with", "and" | 381 stoplist is used to remove common words like "with", "and" |
| 382 etc. Additional stoplist words can be added in the tracker's | 382 etc. Additional stoplist words can be added in the tracker's |
| 383 config.ini file. Once filtering of the word list is done, each indexed | 383 config.ini file. Once filtering of the word list is done, each indexed |
| 384 item (e.g. title, file or message content ...) is searched and if all | 384 item (e.g. title, file or message content ...) is searched and if all |
| 385 the terms are found in the item the item is returned. Then the items | 385 the terms are found in the item the item is returned. Then the items |
| 387 | 387 |
| 388 Other searching backends such as native-fts can be used in which case | 388 Other searching backends such as native-fts can be used in which case |
| 389 the filtering above is not used. The search query can support | 389 the filtering above is not used. The search query can support |
| 390 structure such as quoted phrases, matching one term or another rather | 390 structure such as quoted phrases, matching one term or another rather |
| 391 than both (or search), prefixes etc. In this case you should look at | 391 than both (or search), prefixes etc. In this case you should look at |
| 392 the documentation for the native-fts backend to find the supported | 392 the `documentation for configuring the native-fts`_ backend to find |
| 393 format and features. | 393 the supported format and features. |
| 394 | |
| 395 .. _`documentation for configuring the native-fts`: admin_guide.html#configuring-native-fts-full-text-search | |
| 394 | 396 |
| 395 Access Controls | 397 Access Controls |
| 396 --------------- | 398 --------------- |
| 397 | 399 |
| 398 User access is controlled through Permissions. These are are grouped | 400 User access is controlled through Permissions. These are are grouped |