You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 28, 2020. It is now read-only.
At the moment the source hard-codes two elections, referred to consistently by the slugs "2010" and "2015". These also have metadata associated with them, e.g. the dates of those elections, and (less explicitly):
The default start and end dates of candidacies for those elections. Since it's very rare (in the UK anyway) to have a defined date for the start of a candidacies, and tracking changes with precise dates is similarly, we just use a start date for the candidacy as the day after the previous election.
For the UK, these are implicitly elections for posts with the role "Member of Parliament"
[... etc. probably others, which I'll come back to]
Instead, this should be a data structure in a country-specific settings.py which might look something like:
Would it make sense to have this at the PopIt/Popolo level? For example, these could be Events connected to[1] the Organisation and Term for which the election is happening.
This would then also make this data re-usable, from the same source, in consuming apps, rather than them needing to duplicate it themselves (this becomes more valuable when there are multiple parallel elections, rather than just a single general election).
@tmtmtmtm I see what you're saying, but that would have added some complexity to the time-constrained development of YNR - I'll create a new, more specific, ticket for your suggestion so we can deal with that in the future, but close this one.
At the moment the source hard-codes two elections, referred to consistently by the slugs
"2010"
and"2015"
. These also have metadata associated with them, e.g. the dates of those elections, and (less explicitly):Instead, this should be a data structure in a country-specific
settings.py
which might look something like:... and then any code that refers to elections as
"2010"
or"2015"
be updated to use theELECTIONS
setting instead.The text was updated successfully, but these errors were encountered: