- πΊπΈUnited States smustgrave
Wonder if this is still a valid task for D10?
This came up in #2020167-31: Add a name and email search field to the admin/people view β ...
...does anybody else think that we should provide a means for people to invert the filter(s) (for example allowing admins to filter people that are not of a specific role or that do not have a certain permission)?...
Currently we provide no way in the UI to select multiple arguments per property since the available filters are in drop-down menus instead of select lists. So, if for example an admin wants to filter all non-admin users in a site (admin/people) and apply an action to them, they have to select each non-admin role and apply the action multiple times. In sites with many roles this could get really tedious/frustrating - and that was only one example.
This could be done (order by increase in UI complexity)...
- by using an "Invert filter" button/link (next to the "Filter" and "Reset" buttons). This would provide some flexibility without over-complicating the UI, but it would make filtering down to the desired criteria a two-step process (people would first have to search for the opposite they wish to filter and then invert). Also, since this "Invert filter" button would only show after you have filtered once, novice users might not be aware of the existence of this feature at all. We'd need to educate them while things should be straight forward. Finally, we need to keep in mind that we "remember" the filters after form submission. How would that work in this scenario?
- by pairing the drop-downs with an additional "is/is not" drop-down. This would give users much more freedom, but at the same time add complexity to the UI and perhaps make it overwhelming.
- alternatively, we could change the drop-down menus into select lists like we do in admin/reports/dblog for example:
This would be the most flexible solution, but it seems to be as complicated a UI as it would be with the the additional "is/is not" drop-downs, but for both cases we can hide this in an "Advanced filters" section or something.
Other thoughts?
1. Decide if this is a useful feature and core-worthy.
2. If the answer above is "yes", decide what would be the best solution.
3. Implement the solution that we come up with from step 2.
TBD
...
π
[META] Provide a generic search/filter UI interface pattern for listing pages
Closed: outdated
#2020167: Add a name and email search field to the admin/people view β
#2023683: Improve the layout and usability of the admin/people exposed filters and actions β
Postponed: needs info
9.5
Last updated
Related to the Views in Drupal Core initiative.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Wonder if this is still a valid task for D10?