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

Manual Counts Policy - Ballot Count Reporting #4073

Merged
merged 4 commits into from
Oct 23, 2023

Conversation

adghayes
Copy link
Collaborator

@adghayes adghayes commented Oct 11, 2023

Overview

@mattroe and I discussed how our policy with manual results is that we always show them separately on reports where they contribute to the overall ballot count or vote count. This is what we do for the tally reports - if there are any manual results, the reports flip to show manual counts.

When I built the ballot count reporting (PDF and CSV), I included options to show the ballot count breakdown differently. 'none' would never show manual counts, and 'manual' would always show manual counts. This is in violation of our decided policy.

In this PR, I simply remove the idea the ballot count breakdown as an editable feature - it is always the maximal option - BMD, HMPB, Total and, if applicable, Manual.

@adghayes adghayes requested a review from a team as a code owner October 11, 2023 10:53
@adghayes adghayes requested review from kofi-q, mattroe, a team and kshen0 and removed request for a team and kshen0 October 11, 2023 10:53
@mattroe
Copy link

mattroe commented Oct 11, 2023

@adghayes what do you think about implementing this as a checkbox under report by instead? Such as Report By "Ballot Type" instead of having a distinct option?

@adghayes
Copy link
Collaborator Author

adghayes commented Oct 11, 2023

I think of it as a dropdown because I'm assuming we will eventually add sheet counts which will be in the same dropdown. That being said, we don't have sheet counts yet, so it could be a checkbox for now.

re: collapsing the "Report By," here's what I wrote in the polish doc:

Interesting observation. You can see on the chart that "Report By" breaks things onto new rows whereas the breakdown breaks things across rows. This is necessary to show row totals. From a technical standpoint, they are very different - what CVRs do we filter for vs. how do we display the data.

I know it seems weird as a singular option but I think that has more to do with the fact that we only have one option so far rather than that it should be with "Report By."

I would push to leave this as-is, if anything because the implementation makes more sense this way.

On the other hand, if you're simply suggesting removing the "Options" header then that's fine and easy to do.

@adghayes
Copy link
Collaborator Author

@mattroe one thing I would be more favorable toward is just dropping the option altogether and always showing BMD vs. HMPB counts. I think I went a little overboard with scope when designing this, and it's only a small downside to always have more information on the report.

@mattroe
Copy link

mattroe commented Oct 11, 2023

@adghayes Good point. Agree that we could simplify this interface by removing the option altogether and defaulting to this breakdown.

For the future: could we not apply the same "Report By" UX for sheets? I understand it's not the same query type, but I would argue a user just thinks of it as "reporting by sheet count" instead of "reporting by ballot count".

@adghayes
Copy link
Collaborator Author

Yup, there's no reason we can't apply the same UX. And maybe you're right, that the "Report By" UX would be clearer for users as it was for you. Happy to make it that way if that's the consensus.

But I personally still don't like it, even more so for the sheet example than the previous example. Because the "Report By" entails some splitting of results into its constituent parts. Separating sheet counts is sort of that, sort of not... because the sum of sheet counts is not the ballot count. It could be a cute little checkbox.

It's not a hill I'll die on but that's my gut. It's possible I just can't see through the implementation to the UX.

@adghayes adghayes marked this pull request as draft October 11, 2023 17:45
@adghayes adghayes force-pushed the drew/manual-ballot-counts-policy branch from 0524274 to d7996c7 Compare October 13, 2023 06:48
@adghayes adghayes force-pushed the drew/manual-ballot-counts-policy branch from d7996c7 to bb5557c Compare October 13, 2023 06:50
@adghayes adghayes marked this pull request as ready for review October 13, 2023 14:09
@adghayes adghayes merged commit d463016 into main Oct 23, 2023
@adghayes adghayes deleted the drew/manual-ballot-counts-policy branch October 23, 2023 19:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants