Islands in search results should be configurable
Bug #794935 reported by
Thomas Krause
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ANNIS |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
Search nodes that are too far apart to be shown in the same context (distance > context_
* context_
* NUMBER (e.g. 10 tokens)
* none (never use islands, always give all tokens between hit nodes)
There should also be an option to display a control in the front-end which allows users to configure this in real-time. The admin can determine if this control is displayed/enabled depending on the corpora in the system (e.g. for legal reasons).
Revision history for this message
| Thomas Krause (krause) wrote | #1 |
| Changed in annis: | |
| status: | Triaged → Fix Released |
| Changed in annis: | |
| status: | Fix Released → Triaged |
| milestone: | 3.0.0-beta2 → 3.0.0 |
To post a comment you must log in.
Support for "none" has been implemented. This has to be done in the service since the generated SQL already filters out nodes that match the condition or not (there no such code in the frontend).
Currently there is some global default configuration and you can create corpus specific configuration files in the service folder. Beeing able to change this behavior from the frontend would need more work and an expansion/
For the fixed number things are a little bit more complicated. We don't know the token-order of the nodes at the time of the SQL-generation. Thus it's not clear howto implement this in a proper and consistent way.