BallotReady
crosswalk__*
We maintain 8 different crosswalk tables linking data from BallotReady with data from Indigo. These tables include:
- Links BallotReady's election_id to Indigo's election_id
- Indigo considers an election to be a unique combination of an election date, an administrative jurisdiction, and (in the case of partisan primaries) the party of candidates eligible for the ballot. BallotReady considers an election to be a unique combination of an election date and an administrative jurisdiction – with no party-level differentiation in primaries. Because of this difference, we include some additional fields for reference, including eligible_candidate_party.
- Links BallotReady's position_id to Indigo's office_id
- Indigo considers an office to be a legal construct created by a parent jurisdiction. BallotReady considers a position to be a specific elected office associated with a specific district. In the Indigo data graph, all State Senate seats in Nebrasa have the same office_id. In the BallotReady data graph, there would be 49 distinct active position_id values associated with that body. Because of that difference, this crosswalk contains "many-to-one" connections.
- Links BallotReady's position_id to Indigo's district_id
- Indigo considers a district to be a unit of electoral geography associated with a specific elected office. When a district is redrawn via redistricting, it is deprecated and replaced with a new district – with a new district_id. BallotReady considers a position to be a specific office associated with a specific conceptual (rather than spatial) district. So in the BallotReady data graph, Florida State House District 1 would maintain the same position_id over time. But in the Indigo data graph, Florida State House District 1 would have a unique district_id for each of its spatial variations.
- Links BallotReady's race_id to Indigo's contest_id
- Both BallotReady and Indigo consider a race/contest to be a specific election for a specific elected office associated with a specific district.
- Links BallotReady's candidate_id to Indigo's candidate_id
- Both BallotReady and Indigo consider a candidate to be an individual person who has run for office – independent of their individual runs for office.
- Links BallotReady's candidacy_id to Indigo's campaign_id
- Both BallotReady and Indigo consider a candidacy/campaign to be a specific instance of an individual candidate running for office. In both data graphs, primary and general election candidacies/campaigns – as well as run-offs of any kind – are distinct
- Links BallotReady's candidate_id to Indigo's voter_id
- Links BallotReady's office_holder_id to Indigo's voter_id