Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve filter settings User Interface #3

Open
kgruschow opened this issue May 6, 2021 · 3 comments
Open

Improve filter settings User Interface #3

kgruschow opened this issue May 6, 2021 · 3 comments
Labels
useability Issue with use

Comments

@kgruschow
Copy link
Contributor

kgruschow commented May 6, 2021

example of nonworking filters

after selecting values, graph is not actually filtered or at least there is no clear UI for changing it. It can seem like filter is not being set, and it is not, user must check the box to turn on filter:

the button for turning on filter

@kgruschow kgruschow changed the title unable to correctly set filters for race values Filter User Interface confusing May 7, 2021
@kgruschow kgruschow added the useability Issue with use label May 7, 2021
@kgruschow kgruschow changed the title Filter User Interface confusing User Interface for filters is confusing May 14, 2021
@miserman
Copy link
Contributor

miserman commented Jun 7, 2021

57c5f2b hopefully improves this.

@kgruschow kgruschow changed the title User Interface for filters is confusing Improve filter settings User Interface Jun 9, 2021
@kgruschow
Copy link
Contributor Author

That is an improvement, documenting related issues within that here:

image

The text label near the gear icon should make clear that the gear icon reveals filter/sort options for age_group or race. If possible it might be nice to literally label it as "Modify filter and settings for age_group" (or race respectively) . similarly, instead of 5/5 levels, 5/5 groups selected.

within those settings:
image

before literally asking almost everything to be changed... i think this is really good direction :)

  1. sort by Increasing/decreasing - user needs to be able to clearly see that this is a control/ toggle. it will look worse but be more accessible (literally as well vis a vis section 508/ADA concerns)
  2. the terms 'labels' and 'levels' are data science/statistics terms and should be avoided throughout the UI. Given the small number of variables, I think it is releastic to show specific names, e.g. instead of :
    image it could say "include selected racial groups:", or if it were counties says "include selected counties:"
  3. relatedly, the UI for selecting what "aspect" would preferably be something like "alphabetically by racial group" or alternately " by mean of arrests by racial group". note that mean should clearly state mean of it.
  4. in same vein if that is done, likely the ordering of the top row would logically be "sort >alphabetically by group/numerically by mean> in ascending/descending order. This resolves some of the grammar issues created by this request.
  5. the text for the exclusion should be altered to specifically state that is in addition to the above filter, e.g. if you select three racial groups and limits, it first keeps the selected groups and then excludes based on limits. Suggested terminology might be to "from the above selected groups, additionally filter out groups where:" or similar.
  6. Is there a difference between close and X? it might be good to move the reset button elsewhere and have "submit" and "cancel" as lower buttons instead of close and reset. X should also cancel.

@miserman
Copy link
Contributor

069620a makes I think all of these changes.

Relating to 6, I just removed the bottom close button for consistency. Currently everything is updated when any options are changed, so having submit and cancel buttons would involve making changes within that menu temporary, and only applying them if submit is clicked, which could be done, but would be a change from how other menus work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
useability Issue with use
Projects
None yet
Development

No branches or pull requests

2 participants