Support filter exclusions and exclusion opt-out operator WAS24 #4

Open
opened 2026-04-02 23:29:11 +00:00 by firepear · 0 comments
Owner

I have a few facets in my collection which I want to keep, but only want to hear under rare circumstances (best example: Xmas).

The catalog should support a configurable exclusion filter, which keeps things out of result sets unless an operator is specified in the filter which prevents the exclusion from being applied. The implementation of this looks like:

  • Specifying a filter in the config, each element of which will become <> instead of =, and which will be appended to all incoming filters
  • Creating a NO_EXCLUDE operator for the filter grammar, to allow filters to avoid having the exclude being applied
    • The client UI would want this when the Facet/Artist select boxes are being used, to avoid subverting user intent/expectations
I have a few facets in my collection which I want to keep, but only want to hear under rare circumstances (best example: `Xmas`). The catalog should support a configurable exclusion filter, which keeps things out of result sets unless an operator is specified in the filter which prevents the exclusion from being applied. The implementation of this looks like: - Specifying a filter in the config, each element of which will become `<>` instead of `=`, and which will be appended to all incoming filters - Creating a `NO_EXCLUDE` operator for the filter grammar, to allow filters to avoid having the exclude being applied - The client UI would want this when the Facet/Artist select boxes are being used, to avoid subverting user intent/expectations
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
firepear/thrasher-media-catalog#4
No description provided.