Blog

Election Results: Data-Wrangling Ramsey County

Next up are several overdue reports on data wrangling of county level election data, that is, working with election officials to get legacy data needed for election results; and then putting the data into practical use. It’s where we write software to chew up whatever data we get, put it in a backend system, re-arrange it, and spit it out all tidy and clean, in a standard election data format. From...

Continue Reading >
VoteStream: Data-Wrangling of Election Results Data

If you’ve read some of the ongoing thread about our VoteStream effort, it’s been a lot about data and standards. Today is more of the same, but first with a nod that the software development is going fine, as well. We’ve come up with a preliminary data model, gotten real results data from Ramsey County, Minnesota, and developed most of the key features in the VoteStream prototype, using the TrustTheVote...

Continue Reading >
Election Results Reporting – Assumptions About Standards and Converters (concluded)

Last time, I explained how our VoteStream work depends on the 3rd of 3 assumptions: loosely, that there might be a good way to get election results data (and other related data) out of their current hiding places, and into some useful software, connected by an election data standard that encompasses results data. But what are we actually doing about it?

Answer: we are building prototypes of that...

Continue Reading >
Election Results Reporting – Assumptions About Standards and Converters

It’s time to finish — in two parts — the long-ish explanation of the assumptions behind our current “VoteStream” prototype stage of the TrustTheVote Project’s Election Result Reporting Platform (ENRS) project. As I said before, it is an exercise in validating some key assumptions, and discovering their limits. Previously, I’ve described our assumptions about election results data, and the software...

Continue Reading >
Not Just Election Night: VoteStream

A rose by any other name would smell as sweet, but if you want people to understand what a software package does, it needs a good name.

In our Election Night Reporting System project, we’ve learned that it’s not just about election night, and it’s not just about reporting either. Even before election night, a system can convey a great deal of information about an upcoming election and the places...

Continue Reading >
Election Results Reporting – Assumptions About Software (concluded)

Today, I’ll be concluding my description of one area of assumptions in our Election Night Reporting System project — our assumptions about software. In my last post, I said that our assumptions about software were based on two things: our assumptions about election results data (which I described previously), and the results of the previous, design-centric phase of our ENRS work. Those results consist...

Continue Reading >
Election Results Reporting – Assumptions About Software

Today I’m continuing with the second of a 3-part series about what we at the TrustTheVote Project are hoping to prove in our Election Night Reporting System project. As I wrote earlier, we have assumptions in three areas, one of which is software.I’ll try to put into a nutshell a question that we’re working on an answer to:

If you were able to get the raw election results data available in a wonderful...

Continue Reading >
Election Results Reporting – Assumptions about Data

In a previous post I said that our ENRS project is basically an effort to investigate a set of assumptions about how the reporting of election results can be transformed with innovations right at the source — in the hands of the local election officials who manage the elections that create the data.

One of those assumptions is that we — and I am talking about election technologists in a broad community...

Continue Reading >