In the Asset Publisher, you can dynamically build a list of filters that are applied when searching for assets. This way, you would think it would be possible to perform e.g. the following "query" (C means Category here, see also screenshot attached for a real-life example):
C1 and (C2 or C3) and (C4 or C5)
However, this doesn't work as expected. The front-end filter is converted to an AssetEntryQuery object. This object has two fields for storing categoryIds: allCategoryIds and anyCategoryIds. For the example above, the AssetEntryQuery would have the following values:
- allCategoryIds = [C1]
- anyCategoryIds = [C4, C5]
According to Users Guide, any number of filters can be created, so Asset Publisher should be able to handle any number of filters.
Extend AssetEntryQuery class to be able to store all the necessary information, and update the AssetEntryFinderImpl to be able to handle the additional information.