Closed JohnMwashuma closed 1 year ago
@JohnMwashuma for the sections: male_voters, female_voters and unisex_voters. I would like to confirm that we are showing the number of voters registered for each of these categories and not not the number of votes by people in these categories.
@JohnMwashuma for the sections: male_voters, female_voters and unisex_voters. I would like to confirm that we are showing the number of voters registered for each of these categories and not not the number of votes from people in these categories.
Actually thinking about this, it should be number of votes from people in these categories.
ok
@JohnMwashuma for the filters, do we want to allow the ux workflow where:
Context
The turnout report is used for displaying the current voter turnout per administrative area. Administrative areas of interest are Regions, Constituencies and Sub Constituencies. That said, the current report structure does support Admin area reports but with a bad user experience, hence the need for updating it.
Proposed changes
Administrative area
column value's should be the last Administrative Area selected so that we can display turn out per Administrative Area i.e.Task check list
[ ] Create filter drop-downs for filtering the report per the Administrative area's. The filters will the following in the exact order:
The following Django queries should help with logic:
[ ] Create a turnout report per Administrative areas selected. The following Django queries will help with this logic:
Regions turnout report:
Constituencies turnout report:
Sub Constituencies turnout report:
[ ] Update the
TurnoutReportDataView
view filterqueryset method with the above logicRelated to
https://github.com/onaio/tally-ho/issues/394