You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Big question is how complex we want to make the filter system. For now (and maybe forever), we don't want a full blown super complex system with arbitrary AND/OR/NOT operators and stuff. Main focus for now should be to cover the main use cases and have a UI that's simple to use. We can make it more powerful in the future, but we should always keep it easy to use. Hiding expert features if necessary.
TODO: elaborate further, list some things to filter for. Ole already started something. I want to take a look at that before writing stuff from scratch here.
The text was updated successfully, but these errors were encountered:
Keep in mind one "separate" filter might be the source of data (DC metadata vs. slides vs. transcripts) to distinguish from "search all sources" - results of that filter have to be filtered further with the "original" filters (date/semester, language, access).
This adds a first iteration of basic filters for item type ("all",
"videos", "pages") and time frame.
There are some open questions regarding how to deal with pages while the
time filter is active, since pages do not have a timestamp. This means
they are not affected by the filter.
Lukas and I decided to split to reworking of the search into multiple
PRs with incremental improvements and features added. This is now only
laying the foundation for these work packages, and will not change
anything visible for now.
Filters are included but hidden behind the `tobiraExperimentalFeatures`
flag (this is mainly information for developers).
Part of #1063
Big question is how complex we want to make the filter system. For now (and maybe forever), we don't want a full blown super complex system with arbitrary AND/OR/NOT operators and stuff. Main focus for now should be to cover the main use cases and have a UI that's simple to use. We can make it more powerful in the future, but we should always keep it easy to use. Hiding expert features if necessary.
TODO: elaborate further, list some things to filter for. Ole already started something. I want to take a look at that before writing stuff from scratch here.
The text was updated successfully, but these errors were encountered: