View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013096 | MMW 5 | General | public | 2016-01-28 14:51 | 2019-11-21 20:54 |
| Reporter | Ludek | Assigned To | |||
| Priority | low | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Summary | 0013096: Option to show only top level matches in search results | ||||
| Description | Originally raised as item 11) here 0012521:0043540 Currently once user press Ctrl+F and type word 'Beatles' then artist item 'The Beatles' is in search results, but also all albums and all tracks from 'The Beatles' Jiri suggested that if artist item for 'The Beatles' is already shown in results then there is no need to show all tracks from 'The Beatles', but only those tracks that have 'Beatles' included in another field than artist, e.g. 'Beatles' as song title Possible UI: [ ] Only show top level matches (Tooltip: Shrinks search results to only show top-level matches to the search term, and not any items contained within that attribute) Note that if we implement this then it won't correspond with current Options -> Search configurations where user can set up which fields should be searched via search bar | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
1av) from #12521 is still open, and I'm not sure that we can reasonably postpone this. i.e. incremental search results are still partial and view-dependent (e.g. in the Music node). In addition, as suggested at #12521, to distinguish between global and incremental search, I would suggest that incremental search be implemented as an extension to the breadcrumb (this way breadcrumbs will work consistently always. EDIT: this has since been addressed by #13230. |
|
|
Note: I misunderstood this feature request. I think that the current implementation in build 2019 (which returns results for commonly used fields) is perfectly fine. In fact, the current implementation is preferable considering that Options > Search already allows the user to choose which fields should be searched, and implementing this feature would conflict with those settings. |
|
|
Ok, so resolved as no change required |
