Skip to content
This repository was archived by the owner on Nov 16, 2023. It is now read-only.
This repository was archived by the owner on Nov 16, 2023. It is now read-only.

Add special-election indicator to Elex data structure #333

@mileswwatkins

Description

@mileswwatkins

The AP serves special elections alongside regular results, and typically the only indicators of specialness are in the text fields racetype, seatname, and description.

I've confirmed with AP Support that the 2018 general-election data will use these fields like so:

  • racetype will be "Special General"
  • seatname will be "a year … either the year the term for that seat began or when it was to end - we are still working that out"

2016 general special elections had similar content; for example, the special House races:

id,racetype,racetypeid,description,seatname
12979-polid-53401-state-HI-1,Special General,G,2014 - Unexpired Term,1-Unexpired Term
18848-polid-54203-state-KY-1,Special General,G,2014 - Unexpired Term,1-Unexpired Term
40288-polid-49768-state-PA-1,Special General,G,Replace Fattah,2-Unexpired Term

Obviously, we'd have to get further confirmations from the AP before we just assume string parsing like racetype ILIKE '%special%' AS is_special_election would produce an accurate new column. But I think that it'd be a valuable addition to the schema, surfacing/structuring a meaningful piece of information that is useful in data pipelines and graphics, but isn't explicitly structured by the AP.

The Elex CSV schema already has an is_ballot_measure column, which is an analogous "calculated field." This seems to suggest that an is_special_election flag would fit as well.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions