Closed hilah-ats closed 1 year ago
Before this commit (https://github.com/Daniel-KM/Omeka-S-module-AdvancedSearch/commit/b4ee3fa4803ec7fa5ae361dba3e8ba1578b754ad), the filters (not advanced filters) produced results that contained every value in the selection, however after this commit, filters now produce results that contain any value in the selection. This is reproduceable on a clean installation with only the Advanced Search module installed.
Is this intended? If not, is it possible to allow configuration of the operator for filters (not advanced filters)?
Behavior is still present in 3.3.6.18
Indeed, the good behavior for filter is "and" and the optimization converted it into a list, so "or". I disabled it in last version (3.4.6.19)
Before this commit (https://github.com/Daniel-KM/Omeka-S-module-AdvancedSearch/commit/b4ee3fa4803ec7fa5ae361dba3e8ba1578b754ad), the filters (not advanced filters) produced results that contained every value in the selection, however after this commit, filters now produce results that contain any value in the selection. This is reproduceable on a clean installation with only the Advanced Search module installed.
Is this intended? If not, is it possible to allow configuration of the operator for filters (not advanced filters)?