Topic on Talk:Edit Review Improvements/New filters for edit review

the "namespace" button is unintuitive, and kinda hidden. it is also non standard UI design to put controls at the bottom or scrollable list.

the "filters" form is a form, and should behave like a form: all controls in static locations, and scrollable lists should only contain items of same kind.

same comment applies to "tagged edits" too, but this button is much less useful (for me) than "namespaces", which is a first class citizen, probably as useful as all other filters put together...

funny thing is, the form _has_ the marginally useful "highlight results" button like a form. the namespace and tagged edits buttons should be as prominent, if not more.

peace.

Hi @קיפודנחש. There are a couple of quicker ways to get to the Namespace menu.

• Simply type a colon into the search bar. (If you then follow by typing in a namespace name—or the start of one— the search will bring it up instantly. E.g., :w will instantly produce the filters for Wikipedia and Wikipedia Talk namespaces.)

• The second is by using the Advanced Filters icons at right of the search bar.

I hope that helps.

I guess i was miunderstood. I did not ask for help, i was trying to provide it, by responding to the "please give feedback" link.

Peace.

I apologize if i misunderstood your comment; it was unclear that you'd noticed that Namespace is also displayed in the Advanced Filters panel on the main level, as well as being "hidden" inside the main filter menu. Putting the Advanced Filters menu at the bottom of the main menu provides an alternative way for users to discover these tools. Testing shows it's actually a pretty common route to discovery.

If you did discover the Namespace icon on the main level, can you perhaps elaborate on your criticism? Is it that you think Namespace should be more prominent?

One issue you're probably not aware of is that we're planning to add more advanced filters: first up will be a Users filter menu, which will let you include or exclude particular usernames. After that, the plan is to add a Categories filter. Here is a ticket that shows the plans for the Advanced Filters navigation in its final state.

It actually makes more sense to remove those two buttons at the bottom, they seem like needless clutter. Also certain languages are very verbose, so those two buttons on top may overwhelm the top section (and bottom section) of the drop down.

There are some ways to improve the discoverability of the namespace / tagged edits / general filters:

1. Remove the "filter" label
2. Remove the bottom buttons
3. Use a standard toolbar right on top of the drop down, instead of the "filter" label, and use icons
4. Whenever a specific "filter type" is being used, highlight the icon so it acts as a tabbed interface

Putting the filter far away from the icon / buttons that trigger it seems downright confusing. You click them on one side, and they show up on the other. There is also no visual feedback to actually indicate that the icons were clicked. Finally more entry points mean more confusion.

Generally though, there's one thing to give kudos to the designer (or whoever thought up that system). The dropdown with prefixes (":", "#") is pure genius. Experienced users will likely start ignoring the buttons altogether. That's of course assuming that eventually there's a way to confirm the selection and close the dropdown using the keyboard.

I'm glad you like the search function. It's good to hear from experienced users like yourself, who are focused on efficiency.

I'm pinging our designer, @Pginer-WMF: so he can review your suggestions.

One of the challenging aspects in this case was to define the relationship between the different kinds of filters.

Presenting the different groups of filters at the same level requires users to make a choice upfront. However, unlike "namespaces", the group of the "general" filters and "tags" serve a diversity of purposes and it is not clear that such division is clear if you are not already familiar with the contents of such groups.

We opted by presenting the "general filters" as the main entry point from which you can reach all filters and present the complexity incrementally. If the user explores the initial list and is interested in reaching more filters, we provide options to continue. In addition we surface quick accesses to namespaces and tags for more experienced users to access them quickly as they used to.

Based on the data we analyzed about the use of the different filters it made sense. For example, most of the requests analysed in the previous UI (96%) were not filtering by namespace and more than half of the times users did, the namespace selection was to chose the main an talk namespaces. In any case, we'll keep an eye on how the filters are use and consider whether exposing the advanced filters (with their associated lists of concepts) more prominently can be helpful.

How about getting rid of the 3 separate forms ("filter", "namespace", "tagged"), and replacing it with a single, tabbed form?

It creates a challenge for displaying current filter setting, but makes entering/creating the filter more streamlined and logical.

Peace.

Thanks for the suggestion, @קיפודנחש. It makes perfect sense in the case we identify that these three groups are understood by users at the same level. Your feedback is useful and we'll be compiling more feedback and observing how filters are used to have a better understanding in that regard.

Thanks!