Feature/add more election results data

[VirginiaDooley]

Closes #935 and #1663
Dependent on DemocracyClub/yournextrepresentative#2174

This work adds election results for past elections, when results are available.

• Add turnout, ballot papers issues, electorate and spoilt ballots to Election model
• Display ^^ results data in a new table on the ballot template as shown below, only when they exist
• Add Welsh translations
• Import this data as part of the import_ballots process
• Add election results to YNR ballot serializer
• Switches candidate lists to a single column

To test:

• run migrations
• run the ballot importer for recent elections with python manage.py import_ballots --current
• visit a recently past election with results to view a new table similar to the one shown below

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1205303544790826

[coveralls]

coverage: 61.513% (+0.04%) from 61.476% when pulling 36ac9ea on feature/add-turnout-and-spoilt-ballots into 82d9834 on master.

[VirginiaDooley]

@pmk01 Would you prefer the table not appear at all if results are not available? Or should it read, as is the case currently, eg "Electorate not available"?

[VirginiaDooley]

@symroe This works well with current ballots, but for a full import, I hit an issue with formatting. For example: https://candidates.democracyclub.org.uk/api/next/results/local.reading.norcot.by.2023-08-03/ which points to an issue with the way I've formatted it in the serializer or the way it's arriving via resultsbot

[pmk01]

@pmk01 Would you prefer the table not appear at all if results are not available? Or should it read, as is the case currently, eg "Electorate not available"?

We should not show the table until we have some results.

It will be common for us to lack some numbers. It's often the case that councils only publish turnout percentage and nothing else, for example. We could just leave the field blank if we don't have the number? I think this is preferable to "[thing] not available".

[VirginiaDooley]

@pmk01 Would you prefer the table not appear at all if results are not available? Or should it read, as is the case currently, eg "Electorate not available"?

We should not show the table until we have some results.

It will be common for us to lack some numbers. It's often the case that councils only publish turnout percentage and nothing else, for example. We could just leave the field blank if we don't have the number? I think this is preferable to "[thing] not available".

I think we have to have something in the box if a data point isn't available - if nothing else to maintain the formatting of the table, is "None" ok?

[VirginiaDooley]

@pmk01 Would you prefer the table not appear at all if results are not available? Or should it read, as is the case currently, eg "Electorate not available"?

We should not show the table until we have some results.
It will be common for us to lack some numbers. It's often the case that councils only publish turnout percentage and nothing else, for example. We could just leave the field blank if we don't have the number? I think this is preferable to "[thing] not available".

I think we have to have something in the box if a data point isn't available - if nothing else to maintain the formatting of the table, is "None" ok?

This is done with b4d20ae

[pmk01]

Sorry, no, 'none' wouldn't work becuase turnout: "none" doesn't make any sense. If we have nothing at all, does the column disappear? I am fine with that if the case.

[symroe]

Sorry to throw a spanner in the works late on, but would it be better for the table to be flopped 90°?

So we have

a: 1
b: 2
c: 3

rather than

a    b    c
1    2    3

Thinking about mobile interfaces mostly,

[VirginiaDooley]

I think this is what you suggested? @symroe