Reason (Why?)
To achieve results quickly, the search should be implemented in parts. This is the first part of three (see related issues)
Solution (What?)
The first part of the new full text search should contain tabs split by types (all, artwork, artist, movement, class, material, genre, location and motif). Each tab should contain it's own query, which filters by type, and should only load when it is clicked (lazy loading). The result set should be ranked by relative rank.
The full text search should apply to label, description and abstract attributes.
Extra: empty tabs should not appear in the first place. (use count endpoint for example)
Out of scope
implementation of the list view
special ranking
fuzzy or boost functions
Relation to other Issues
Parent: #199
Part 2: #506
Part 3: #507
Acceptance criteria
The user can find results in the full text search split by their types and access these different result sets over a tabbed menu.
Reason (Why?) To achieve results quickly, the search should be implemented in parts. This is the first part of three (see related issues)
Solution (What?) The first part of the new full text search should contain tabs split by types (all, artwork, artist, movement, class, material, genre, location and motif). Each tab should contain it's own query, which filters by type, and should only load when it is clicked (lazy loading). The result set should be ranked by relative rank. The full text search should apply to label, description and abstract attributes.
Extra: empty tabs should not appear in the first place. (use count endpoint for example)
Out of scope
Relation to other Issues
Acceptance criteria The user can find results in the full text search split by their types and access these different result sets over a tabbed menu.