Our volunteers have been gathering election metadata for several months now, and while we finish up that task we’re ready to start showing you some of the results of that work. Fleshing out the efforts detailed on our wiki, we’re releasing an election metadata API that will deliver information about the availability and scope of results data within the project.
Our initial API response contains most of the data that volunteers have put into our admin via the data-entry process, along with an OpenElections-specific unique identifier for each election. The API currently delivers JSON, but we’re working on a CSV response as well that provides the same information. Here’s the response for elections in Maryland in 2012. You can play around with other states and years by changing the state postal abbreviation and the year, with the caveats that we don’t yet have metadata for all states and we’re focusing on elections between 2000 and 2012. We’ve begun a basic documentation page for the API, too.
Among the details we’re providing in the API are the availability of results at different reporting levels, such as racewide, county or congressional district, and the broad categories of offices represented in those results. For our volunteers, who have gathered much of this information, it’s a chance to see your work in action, and another chance for us to thank you for those efforts. We’ll also be adding 2013 and 2014 election metadata as part of our process, and we hope you find it useful.
OpenElections’ adoption of the Open Civic Division identifiers also is evident in this API. We’re using the OCD identifiers for individual states right now and when we release results data we’ll add them to our custom output.
This release isn’t just for end users who want to check on the status of our efforts (although we hope that it will be useful for that and similar purposes); we’re also using it in our own efforts to load and parse the actual results data. That process is beginning with a handful of states and will continue this fall into 2014. Our goal is to have those initial results ready for preview later this year for feedback and testing. As always, you can keep up with developments on our Google Group or follow the project on Twitter.