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

Add a summary of groupings, with anchor links and a bar graph visualisation, so I can quickly asses relative support for a policy #1093

Closed
brtrx opened this issue Mar 21, 2016 · 6 comments

Comments

@brtrx
Copy link

brtrx commented Mar 21, 2016

Rationale

If a visitor wishes to assess relative support for a policy, they currently need to scan the entire page (which can be very long), or sometime even count the number of profile photos in each support grouping.

This change attempts to better support this assessment by offering a summary of the level of support for or against a position. The bar graph layout is here to support users with a preference for visual learning styles.

Each summary line is an anchor link to the grouping, to allow users to quickly jump to a controversial or interesting group.

Layout

option 3c category filter and summary

Notes

MVP

This "clean" version below shows the concept without features covered in other issues.

option 2c summary no cat filter

Note, however, the change to the divisions anchor link ("4 divisions"), which has been reduced in size and changed in text. IMO it should have the same prominence as the summary links (reviewing particular divisions is quite an advanced step in reviewing a policy)

@equivalentideas
Copy link
Contributor

Nice one @brtrx , I think something like this could definitely be useful in adding more context to the page. I do think we could refine it to something simpler though.

I'm reminded of the quite abstract stacked chart that Github use to show the different languages in a repo:

screen shot 2016-03-22 at 8 49 50 am
screen shot 2016-03-22 at 8 52 10 am

I actually find that pretty useless on Github, but it does add a little variety and visual interest to the page.

Could something similar be used around the header to give you a quick sense of people's voting records on the policy? You could tell quickly if the parliament was generally against something, for it, or it was very close. You could keep all the linking behaviour too.

@brtrx
Copy link
Author

brtrx commented Apr 21, 2016

I did try exactly that pattern in a version of the wireframe. It saves vertical height (arguably not a finite resource) at the expense of ease of understanding.

I found that - as with the Github feature - it was quite difficult to work out what each colour indicated without any supporting text, and there wasn't room for text descriptions when the % in any group was small.

Finally, because of party whips, there's a lot of block voting, so there tends to be two large groups close to 50% and a few small groups <10%. In that case, the key quick comparison is the large groups, which the vertical layout I've used makes easier to see.

With that in mind, here's are three variations of the summary panel, making it easier to compare the total for/against.

Option 2d: U-shape
option 2d - summary - better comparison

Option 2e: Grouped bars *My Preferred
option 2e - summary - better comparison

Option 2f: In-Line Exploded
option 2f - summary - better comparison

Option 2g: In-Line Simplified
option 2g - summary - better comparison

My preference is for an option (like 2e) that shows more detail about the totals in each group, and provides includes anchor links to the page section, but let me know what you think.

cofiem added a commit to cofiem/publicwhip that referenced this issue Nov 18, 2017
@equivalentideas
Copy link
Contributor

Great discussion and ideas on here. I'm personally not sure about this concept:

If a visitor wishes to assess relative support for a policy

I don't really see that as a priority need for most users that would justify adding such a significant element to the page. I think most people want to find out how their MP voted, which isn't that easy right now.

I think a more effective feature would be a way to filter the list of MP name or electorate, like @brtrx suggested above—but I'd say this would be pushed up in the visual hierarchy significantly.

screen shot 2017-11-21 at 11 39 46 am

Maybe replacing the divisions count/link, which could sit on the righthand side on wide screens:

screen shot 2017-11-21 at 11 42 01 am

One thing to consider when implementing the search there is what will people take 'electorate' to mean. If I searched 'NSW' would I expect to just see NSW Senators, or all MPs for electorates that are in the state, like 'Sydney'.

I'd suggest closing this issuing and making a new issue for that feature.

@cofiem
Copy link
Contributor

cofiem commented Nov 21, 2017

If finding a particular MP, or group of MPs, is the most common goal, then yes I agree, this summary doesn't add much.

However, there currently isn't any indication of the overall support/opposition to a policy. For me, in addition to finding out how my MP vote, I also want to see where the policy is at e.g. is there majority support?

I suppose a quick scroll gives a similar overview to the chart. Perhaps going with the party/indep. support/opposition idea rather than just vote counts provides more useful information? The very strong/strong/moderate bars could be changed out for party groupings, with the same For/Against/Mixed/Never sets? That would give an excellent overview of who supports/opposes/doesn't care about the policy.

@stale
Copy link

stale bot commented Oct 13, 2021

This issue has been automatically marked as stale because there has been no activity on it for about six months. If you want to keep it open please make a comment and explain why this issue is still relevant. Otherwise it will be automatically closed in a week. Thank you!

@stale stale bot added the wontfix label Oct 13, 2021
@mlandauer mlandauer removed the wontfix label Oct 19, 2021
@mlandauer mlandauer modified the milestone: Post 2022 Federal Election Nov 30, 2021
@mlandauer mlandauer modified the milestone: 2022 Federal Election Dec 15, 2021
@stale
Copy link

stale bot commented Jun 16, 2022

This issue has been automatically marked as stale because there has been no activity on it for about six months. If you want to keep it open please make a comment and explain why this issue is still relevant. Otherwise it will be automatically closed in a week. Thank you!

@stale stale bot added the wontfix label Jun 16, 2022
@stale stale bot closed this as completed Jun 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants