Mercurial > p > roundup > code
comparison doc/user_guide.txt @ 6592:828e2eaee7cd
Document full text search
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Mon, 24 Jan 2022 23:23:27 -0500 |
| parents | 24e2eeb2ed9a |
| children | 2eec7a500333 |
comparison
equal
deleted
inserted
replaced
| 6591:feab8c878d08 | 6592:828e2eaee7cd |
|---|---|
| 373 @group=priority,-status& | 373 @group=priority,-status& |
| 374 @sort=-activity& | 374 @sort=-activity& |
| 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 | |
| 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 | |
| 381 stoplist is used to remove common words like "with", "and" | |
| 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 | |
| 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 | |
| 386 are mapped to an issue and the list of matching issues is generated. | |
| 387 | |
| 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 | |
| 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 | |
| 392 the documentation for the native-fts backend to find the supported | |
| 393 format and features. | |
| 378 | 394 |
| 379 Access Controls | 395 Access Controls |
| 380 --------------- | 396 --------------- |
| 381 | 397 |
| 382 User access is controlled through Permissions. These are are grouped | 398 User access is controlled through Permissions. These are are grouped |