Oregon relying on its pioneering heritage and Nike spirit says, "Just Do It" for automatic voter registration. And this move seems to provide a worked example for our CTO's recent blog post about the technical simplicity to do so. Oregon already being a vote-by-mail state with online voter registration to boot, was likely able to benefit from those prior innovations. But regardless, as our Foundation's Secretary and General Counsel points out in this post, its a smart move...
Viewing entries tagged
Ms. Voting Matters tackles all your Online Voter Registration questions.
This week the PCEA finally released its long-awaited report to the President. Its loaded with good recommendations. Over the next several days or posts we'll give you our take on some of them. For the moment, we want to call your attention to a couple of under-pinning elements now that its done.
The Resource Behind the Resources
Early in the formation of what initially was referred to as the "Bauer-Ginsberg Commission" we were asked to visit the co-chairs in Washington D.C. to chat about technology experts and resources. We have a Board member who knows them both and when asked we were honored to respond.
Early on we advised the Co-Chairs that their research would be incomplete without speaking with several election technology experts, and of course they agreed. The question was how to create a means to do so and not bog down the progress governed by layers of necessary administrative regulations.
I take a paragraph here to observe that I was very impressed in our initial meeting with Bob Bauer and Ben Ginsberg. Despite being polar political opposites they demonstrated how Washington should work: they were respectful, collegial, sought compromise to advance the common agenda and seemed to be intent on checking politics at the door in order to get work done. It was refreshing and restored my faith that somewhere in the District there remains a potential for government to actually work for the people. I digress.
We advised them that looking to the CalTech-MIT Voting Project would definitely be one resource they could benefit from having.
We offered our own organization, but with our tax exempt status still pending, it would be difficult politically and otherwise to rely on us much in a visible manner.
So the Chairs asked us if we could pull together a list -- not an official subcommittee mind you, but a list of the top "go to" minds in the elections technology domain. We agreed and began a several week process of vetting a list that needed to be winnowed down to about 20 for manageability These experts would be brought in individually as desired, or collectively -- it was to be figured out later which would be most administratively expedient. Several of our readers, supporters, and those who know us were aware of this confidential effort. The challenge was lack of time to run the entire process of public recruiting and selection. So, they asked us to help expedite that, having determined we could gather the best in short order.
And that was fine because anyone was entitled to contact the Commission, submit letters and comments and come testify or speak at the several public hearings to be held.
So we did that. And several of that group were in fact utilized. Not everyone though, and that was kind of disappointing, but a function of the timing constraints.
The next major resource we advised they had to include besides CalTech-MIT and a tech advisory group was Rock The Vote. And that was because (notwithstanding they being a technology partner of ours) Rock The Vote has its ear to the rails of new and young voters starting with their registration experience and initial opportunity to cast their ballot.
Finally we noted that there were a couple of other resources they really could not afford to over-look including the Verified Voting Foundation, and L.A. County's VSAP Project and Travis County's StarVote Project.
The outcome of all of that brings me to the meat of this post about the PCEA Report and our real contribution. Sure, we had some behind the scenes involvement as I describe above. No big deal. We hope it helped.
The Real Opportunity for Innovation
But the real opportunity to contribute came in the creation of the PCEA Web Site and its resource toolkit pages.
On that site, the PCEA took our advice and chose to utilize Rock The Vote's open source voter registration tools and specifically the foundational elements the TrustTheVote Project has built for a States' Voter Information Services Portal.
Together, Rock The Vote and the TrustTheVote Project are able to showcase the open source software that any State can adopt, adapt, and deploy--for free (at least the adoption part) and without having to reinvent the wheel by paying for a ground-up custom build of their own online voter registration and information services portal.
We submit that this resource on their PCEA web site represents an important ingredient to injecting innovation into a stagnant technology environment of today's elections and voting systems world.
For the first time, there is production-ready open source software available for an important part of an elections official's administrative responsibilities that can lower costs, accelerate deployment and catalyze innovation.
To be sure, its only a start -- its lower hanging fruit of an election technology platform that doesn't require any sort of certification. With our exempt status in place, and lots of things happening we'll soon share, there is more, much more, to come. But this is a start.
There is a 112 pages of goodness in the PCEA report. And there are some elements in there that deserve further discussion. But we humbly assert its the availability of some open source software on their resource web site that we think represents a quiet breakthrough in elections technology innovation.
The news has been considerable. So, yep, we admit it. We're oozing pride today. And we owe it to your continued support of our cause. Thank you!
GAM | out
Many thanks to the engaged audience for OSDVer Anne O'Flaherty's presentation yesterday at National Institute of Standards and Technology (NIST), which hosted a workshop on Common Data Formats (CDFs) and standards for data interchange of election data. We had plenty to say, based on our 2012 work with Virginia State Board of Elections (SBE), because that collaboration depends critically on CDFs. Anne and colleagues did a rather surprising amount of data wrangling over many weeks to get things all hooked up right, and the lessons learned are important for continuing work in the standards body, both NIST and the IEEE group working on CDF standards.
As requested by the attendees, here are online versions of the poster and the slides for the presentation "Bringing Transparency to Voter Registration and Absentee Voting."
I hate to see news outlets casting in a partisan political view the issues of voter registration and ready access to the voting booth. But don't give up on the NYT article Waiting Times at Ballot Boxes Draw Scrutiny despite its partisan lead sentence. I rarely do political commentary, but I'll to a little today, specifically in the context of this article, which is very revealing about a traditional -- and I think healthy -- polarity of the American political tradition. One side of the polarity sees issues like this not a problem per se, but a defect in the implementation of current rules. You might call this a "conservative" side of American political problem solving -- don't change the rules, but do act to improve the way that they're put into practice. In this case, for this view, the issue of long lines at polling places is an issue of capacity that's "very easily handled" as NYT quoted Sen. Grassley. The implied solution is more and smaller precincts, more polling places, more voting stations in the polling places, and faster procedures for voter check-in. (I should add that in the latter case, there are tech solutions, like our DIY voter check-in via the Voter Portal we did in 2012, or the Digital Pollbook project of this year.)
That really comes down to pumping more money into existing election operations.
The other side of the polarity, which you might call "progressive", sees issues like this as a problem that needs a solution by changing the current rules, which currently define a system that's not working. Further, the progressive sees such rule changes as an inherent part of a process of evolution of rules (a progression). In this case, for this view, traditional polling place operations are inherently flawed in practice; empirically, we have seen that it leads to hot spots where people wait a long time to check in to vote. The implied solution approach is to create or promote more changes in the voting processes -- early voting, voting centers, more absentee voting, approaches to absentee voting that don't depend on the USPS, separation of Federal elections form those messy local elections with mile-long ballots, … lots of ideas. (And some of them are partly technologically enabled!)
That really comes down to coming up with potentially a lot of money to run new programs to use these new voting methods.
I'm a conservative by temperament: don't fix it unless you're sure it's broken, try some incremental tweaks before replacing it, keep it simple, every change brings in a host of unintended side effects, better the devil you know, and so on. But I like both of these approaches, because they both have a common factor -- increased Federal spending on Federal elections. Believe me the local election officials need it!
Lastly, there's also a tech analogy in the nethead vs. bellhead polarity. Netheads see problems not as structural but in terms of capacity and scale; if your network isn't working right, throw in some more network capacity and compute capacity, but conserve the simplicity of the current structure. Bellheads want to implement progressively more careful control systems. It's a long story about how we now have both in a sort of wave/particle duality, but for this political issue, the geek approach of "both!", is really easy to say: Throw lots more resources at the long lines problem in the current system (line up to vote in person in one specific place on election day), while at the same time doing more with alternative methods; see what happens, and use the results to drive better application of more resources where that has a positive effect, and also use the results to drive more progress in tuning the new approaches (alternate voting methods) in parallel to the existing system with its preserved simplicity. I rarely expect the political process to be informed by the geek view, but there it is.
So, in regard to this supposed political tussle coming, I say: "I hope you both win!"
In this New Year, there are so many new opportunties for election tech work that our collective TrustTheVote head is spinning. But this week anyway, we're focused on next steps in our online voter registration (OVR) work -- planning sessions last week, meetings with state election officials this week, and I hope as a result, a specific plan of action on what we call will "Rocky 4". To refresh readers' memory, Rocky is the OVR system that spans several organizations:
- At OSDV, we developed and maintain the Rocky core software;
- RockTheVote adopted and continues to adopt extensions to it;
- RockTheVote also adapts the Rocky technology to its operational environment (more on that below, with private-label and API);
- Open Source Labs operates Rocky's production system, and a build and test environment for new software releases;
- Several NGOs that are RockTheVote partners also use Rocky as their own OVR system, essentially working with RTV as a public service (no fees!) provider of OVR as an open-source application-as-a-service;
- For a growing list of states that do OVR, Rocky integrates with the state OVR system, to deliver to it the users that RTV and these various other NGOs have connected to online a a result of outreach efforts.
With that recap in mind, I want to highlight some of the accomplishments that this collective of organizations achieved in 2012, and paved the way for more cool stuff in 2013.
- All told, this group effort resulted in over a million -- 1,058,994 -- voter registration applications completed.
- Dozens of partner organizations used Rocky to register their constituents, with the largest and most active being Long Distance Voter.
- We launched a private-label capability in Rocky (more below) that was used for the first time this summer, and the top 3 out of 10 private-label partners registered about 84,000 voters in the first-time use of this new Rocky feature, in a period of about 12 weeks.
- We launched an API in Rocky (more below), and the early adopter organizations registered about 20,000 voters.
That's what I call solid work, with innovative election technology delivering substantial public benefit.
Lastly, to set the stage for upcoming news about what 2013 holds, let me briefly explain 2 of the new technologies in 2012, because they're the basis for work in 2013. Now, from the very beginning of Rocky over 3 years ago, there was a feature called "partner support" where a a 3rd party organization could do a little co-branding in the Rocky application, get a URL that they could use to direct their users to Rocky (where the users would see the 3rd party org's logo), and all the resulting registration activity's stats would be available to the 3rd party org.
The Rocky API - But suppose that you're in an organization that has not just its own web site, but a substantial in-house web application? Suppose that you want your web application to do the user interaction (UI)? Well, the Rocky Application Programming Interface (API) is for just that. Your application do all the UI stuff, and when it's time to create a PDF for the voter to download, print, sign, and mail, your web app calls the Rocky API to request that, and get the results back. (There's an analogous workflow for integrating the state OVR systems for paperless online registration.) The Rocky backend does all the database work, PDF generation, state integration, stats, reporting, and the API also allows you to pull back stats if you don't want to manually use the Partners' web interface of Rocky.
Rocky Private Label - But suppose instead that you want something like that, but you don't actually want to run your own web application. Instead, you want a version of Rocky that's customized to look like a web property of your organization, even though it is operated by RockTheVote. That's what the private-label feature set is for. To get an idea of what it looks like, check out University of CA Student Association's private-label UI on Rocky, here.
That's the quick run-down on what we accomplished with Rocky in 2012, and some of the enabling technology for that. I didn't talk much about integration with state OVR systems, because enhancements to the 2012 "training wheels" is part of what we're up to now -- so more on that to come RSN.
And on behalf of all my colleagues in the TrustTheVote Project and at the OSDV Foundation, I want to thank RockTheVote, Open Source Labs, all the RTV partners, and last but not least several staff at state election offices, for making 2012 a very productive year in the OVR part of OSDV's work.
Much as I admire everybody at the New York Times, I have to disagree with Nick Bilton on his piece Disruptions: Casting a Ballot by Smartphone. I have to say I don't blame him though, especially given the broad range of coverage of the many many kinds election dysfunction that occurred and are still occurring now during state canvassing....
Good Evening-- On this election night, I can't resist pointing out the irony of the USPTO's news of the day for Election Day earlier: "Patenting Your Vote," a nice little article about patents on voting technology. It's also a nice complement to our recent posting on the other form of intellectual property protection on election technology -- trade secrets. In fact, there is some interesting news of the day about how intellectual property protections won't (as some feared) inhibit the use of election technology in Florida.
For recent readers, let's be clear again about what election technology is, and our mission. Election technology is any form of computing -- "software 'n' stuff" -- used by election officials to carry out their administrative duties (like voter registration databases), or by voters to cast a ballot (like an opscan machine for recording votes off of a paper ballot), or by election officials to prepare for an election (like defining ballots), or to conduct an election (like scanning absentee ballots), or to inform the public (like election results reporting). That covers a lot of ground for "election technology."
With the definition, it's reasonable to say that "Election Technology 'R' Us" is what the TrustTheVote Project is about, and why the OSDV Foundation exists to support it. And about intellectual property protection? I think we're clear on the pros and cons:
- CON: trade secrets and software licenses that protect them. These create "black box" for-profit election technology that seems to decrease rather than increase public confidence.
- PRO: open source software licenses. These enable government organizations to [A] adopt election technology with a well-defined legal framework, without which the adoption cannot happen; and [B] enjoy the fruits of the perpetual harvest made possible by virtue of open source efforts.
- PRO: patent applications on election technology. As in today's news, the USPTO can make clear which aspects of voting technology can or can't be protected with patents that could inhibit election officials from using the technology, or require them to pay licensing fees.
- ZERO SUM: granted patents on techniques or business processes (used in election administration or the conduct of elections) in favor of for-profit companies. Downside: can increase costs of election technology adoption by governments. Upside: if the companies do have something innovative, they are entitled to I.P. protection, and it may motivate investment in innovation. Downside: we haven't actually seen much innovation by voting system product vendors, or contract software development organizations used by election administration organizations.
- PRO: granted patents to non-profit organizations. To the extent that there are innovations that non-profits come up with, patents can be used to protect the innovations so that for-profits can't nab the I.P., and charge license fees back to governments running open source software that embodies the innovations.
All that stated, the practical upshot as of today seems to be this: there isn't much innovation in election technology, and that may be why for-profits try to use trade secret protection rather than patents.
That underscores our practical view at the TrustTheVote Project: a lot of election technology isn't actually hard, but rather simply detailed and burdensome to get right -- a burden beyond the scope of all but a few do-it-ourself elections offices' I.T. groups.
That's why our "Election Technology 'R' Us" role is to understand what the real election officials actually need, and then to (please pardon me) "Git 'er done."
What we're "getting done" is the derivation of blue prints and reference implementations of an elections technology framework that can be adopted, adapted, and deployed by any jurisdiction with common open data formats, processes, and verification and accountability loops designed-in from the get-go. This derivation is based on the collective input of elections experts nationwide, from every jurisdiction and every political process point of view. And the real beauty: whereas no single jurisdiction could possibly ever afford (in terms of resources, time or money) to achieve this on their own, by virtue of the collective effort, they can because everyone benefits -- not just from the initial outcomes, but from the on-going improvements and innovations contributed by all.
We believe (and so do the many who support this effort) that the public benefit is obvious and enormous: from every citizen who deserve their ballots counted as cast, to every local election official who must have an elections management service layer with complete fault tolerance in a transparent, secure, and verifiable manner.
From what we've been told, this certainly lifts a load of responsibility off the shoulders of elections officials and allows it to be more comfortably distributed. But what's more, regardless of how our efforts may lighten their burden, the enlightenment that comes from this clearinghouse effect is of enormous benefit to everyone by itself.
So, at the end of the day, what we all benefit from is a way forward for publicly owned critical democracy infrastructure. That is, that "thing" in our process of democracy that causes long lines and insecurities, which the President noted we need to fix during his victory speech tonight. Sure, its about a lot of process. But where there will inevitably be technology involved, well that would be the TrustTheVote Project.
Tomorrow is Election Day 2012, and with many people experiencing pre-election angst, perhaps now is not the time to start telling our patient readers what the heck we've been doing in technology land for the last several months. Right now, we're in a bit of a breather, as election officials and other partners have been focusing solely on the final slog to election day, and readying for a couple intense weeks of work post-election. So instead, I'll be focusing on sharing with you a technology spin on current election news, and get around to our own accomplishments a little later. The news of the moment I want to share is this: there is a good chance that Ohio's state and federal election results won't be available on Election Night or even the next day, and root of the problem is technology. To continue the tree analogy, the trunk is process, the branches are people, the leaves are provisional ballots, and the possible storm blowing through the tree is litigation about the ballots. The technology root is balky; the trunk process of finding absentee voters is tricky; election officials didn't do the process correctly; thousands of absentee voters will instead vote provisionally; the delay in counting those ballots can create the opportunity for a storm.
As a result, there is Florida-2000-style election meltdown looming in Ohio. Due to problems with Ohio's voter records database, perhaps as many as 100,000 Ohioans will vote on provisional ballots, a huge number when you consider that every one of them requires human decisions about whether to count it. And those decisions must be monitored and recorded, because if the decision is "yes" then it is irrevocable. Once a provisional ballot is separated from the voter's affidavit (explaining why they are entitled to vote even if the poll worker didn't think so) and counted, then you can't un-count it. Likewise, the "no" decisions lead to a pile of uncounted ballots, which can be the focus of litigation.
"How does a voter records system lead to this?" you might well ask, thinking of a voter registration system that mainly handles new voter registration (creating a new voter record), and updates or re-registration (e.g. changing the address in an existing voter record). Technology glitches could disenfranchise a voter, but create an election integrity meltdown? Yes - and that's because we're not talking about a voter registration system or database, but rather a voter records system that local election officials use for many purposes. And in this case, it's the hinge for absentee voting.
Here's how it works. An Ohio voter requests absentee status via a voter registration form, either a new registration or an update of an existing record. If that request is granted, the voter record's absentee status is updated. Later on, 50-something days before the election, local election officials use the system to find all the people in their county who will be voting absentee, and send each of them their absentee ballot via U.S. Post. But what if the "find all the absentee voters" part doesn't work? Then some people don't get an absentee ballot, and many of them will try to vote in person, and hit a snag, because:
- The find-the-absentee-voters part is tricky to do with the voter-records system, and many county officials were not given the correct instructions for the lookup. As result, many absentee voters didn't get an absentee ballot.
- What does seem to work OK is preparing the pollbooks for in-person voting, where the poll books indicate for each voter whether they have absentee status. As a result, you get voters with absentee status -- but no absentee ballot -- showing up on Election Day, and being told that they already have a ballot.
Then what? Well, if a voter is persistent and/or the poll workers well-trained and not swamped, then a poll worker will help the voter understand how to vote provisionally -- mark a ballot that does not go into the ballot box, but rather into an envelope with the voter's info. After the election, all these provisional ballot envelopes go to county election HQ, where election officials have to process each envelope, to decide whether the ballot inside should be counted.
Now, the 100,000 estimate kicks in. In a small county with thousands of provisional ballots, or a large county with tens of thousands, the provisional ballot processing can easily go all night and into the next day, because it can't even begin until all absentee ballots have been centrally counted, folded into the results from precincts, and tabulated as preliminary election results. Now suppose that statewide, the margin of victory for the presidential election is only tens of thousands of votes, and statewide there are 100,000+ provisional ballots that are yet to be counted?
In that case, provisional ballot processing is going to receive a lot of scrutiny, and every one of those non-counted ballots is going to be subjected to the type of controversy we saw in Minnesota 4 years ago with the Franken-Coleman senate contest that took weeks to resolve. And this is the situation that has many Ohio election officials (and me) praying that whatever the election result is, the margin is wider than the number of provisional ballots.
This situation is rooted in a voter records system that's too complicated and clunky for harried, under-funded, under-staffed, hard-working election officials to use reliably. So if you doubted that ordinary information technology could create a possible election meltdown just as easily as flaky proprietary voting systems, well, now you know. And that's just one reason why we've been hard at work on registration-related technology -- try to help create the public benefit of an election that is and can be seen to have been administered correctly, before the ballot counting even begins.
Keep those fingers crossed …
Some feedback on a couple recent blogs showed that I didn't do such a great job on defining how our OVR work creates public benefit. So let me try again, with thanks to a canny reader who pointed out the subtlety involved. But first, let me restate what our OVR work is: online voter registration assistance technology for NGOs like RockTheVote and government organizations like state and local boards of election. Through our work with RockTheVote, a large and expanding number of good government groups and other NGOs can quickly get an OVR system of their own, without deploying software or operating computers; and some can take advantage of options to largely re-work the appearance of the OVR web application, and/or integrate with mobile clients and social media. We're also helping drive registrants to the government organizations as well, for those states with a strong online voter registration systems, who have requested that the Rocky OVR system give users the option of registering with the state board of elections. Then, out at the bleeding edge, it is even possible for local or state election officials to piggyback on the OVR system to have their own 100% election-official-managed online voter registration assistance system, with the same look and feel as other county or state web sites, and all without any procurement or deployment.
So, fair enough, we're the technology provider in a mix of many organizations who either want to help people register to vote (NGOs) or are have a basic mission of helping people register -- county registrars and state election officials. So where is the public benefit? And where is the subtlety that I mentioned? Many people would say that in a broad way, the public as a whole benefits when more eligible voters are registered and participate in elections -- but not all. In fact, that is a political issue that we at OSDV want to steer clear of, especially given the political conflicts between some, who wish to aggressively register people in droves and who are more concerned about participation than eligibility, and others who are concerned about possible fraud and are more concerned about eligibility that participation. The debate about voter registration practices goes from one extreme where an election is tainted if it seems that a single eligible voter was barred from participation, to the the other extreme where an election is tainted if there is a suspicion about a single ineligible person having cast a ballot.
So where do public benefits arise separately from these political issues? In a word: access, from a citizen perspective; and duty, from an election official perspective. Every eligible citizen deserves and is entitled to access to elections. It is the duty of election officials to provide that access to the eligible citizens who demand access, and to fairly and expeditiously assess every request for eligibility. Whether or not one is a fan of voter registration drives, or of voter roll purging, there is this shared value: eligible citizens who are trying to participate in elections should not have the access blocked by election officials. Yet in many cases that does occur because well-meaning public officials simply lack the resources, staff, or budget to be responsive to citizen needs. In OSDV's wheel-house, the lack that we address is lack of election technology, or lack of an effective way to acquire and deploy relevant technology.
And the technology angle is particularly important for younger citizens, who have been using computers and smart phones for practically everything for their whole lives. And network and mobile technology is in fact appropriate for registration and all manner of other voter services -- unlike voting which has unique anonymity and integrity requirements -- and so people expect it. Many election officials use technology to help them more effectively carry out their duties, meeting those expectations -- including those relating to voter registration. But for other election officials, there is gap between what they need, and what they are actually able to do within limitations of budget, procurement, staff; or products that simply don't provide the functions appropriate to their jurisdiction. So the gap has multiple dimensions, but across them all, government officials are doing less than they could, in performance of their duties to provide election access to those who are actively seeking it and are eligible.
So when we or anyone else helps to fill that gap with new or better or more available technology, then we have enabled public benefit: election officials can do more in spite of having less resources every year; entitled voters can vote; and thirdly and often overlooked, good government groups and watchdog agencies have more visibility to assess how well the election officials really are doing their job. And that third factor is quite important. Just look at the horror-show of suspicion, vituperation, conspiracy theory, litigation, and Internet-speed dis- or mis-information that spun up recently in Talahassee and Memphis and elsewhere, over removal of people from voter rolls. It may be that nefarious people really were rigging the poll books, or it may be the electronic voter records are in significant dis-array, or it may be voter record databases are antique and prone to administrative error. But we'll never really know. Resource constrained election organizations, that run old election technology with demonstrated flaws, and little or no self-record-keeping, find it extremely difficult to demonstrate to interested and entitled observers, exactly what is going on inside the computers, when one of these election year firestorms brews up.
And when the firestorm is big enough, it essentially prevents election officials from delivering on a fundamental duty: performing accurate and trustworthy elections. In other words, those firestorms are also a detriment to public confidence in elections. We, in addition to helping election officials perform their duties, are also passionate about delivering technology that can help with the transparency that's part of firestorm prevention, and reducing their public detriment.
And lastly that brings me to a related point for another day: how the technology that we're developing now can help deliver that transparency, along with the improvement in the technical infrastructure for U.S. elections. The next chunk is still in the oven, but I really look forward to sharing it here, when it is fully baked.
My last posting was a bit of a cliff-hanger (sorry) for the claims that:
- We're doing useful work to enable NGOs and election officials to offer online voter registration assistance to voters ...
- ... without doing a major acquisition or system integration of the scale that VA is doing now (with OSDV help) or that WA has done or CA is doing in a similar way ...
- ... but rather using a middle way, between those large projects and the "download this PDF to fill out by hand" kind of support.
The key here is to enable election officials to extend a major change in usability, while spending modest time and effort to quickly stand up an online voter registration assistance service.
As I wrote earlier, we took the first step a few weeks ago when we went live with a new release of the "Rocky" OVR assistance system operated by RockTheVote and hosted by Open Source Labs. The main feature of the new release was a web services application programming interface (API) that provides other web applications with access to all of Rocky's functions for voter registration assistance. Now it is time for me to connect the dots from there to actual benefit for voters and election officials -- starting with an explanation of what the API is.
If you take a test drive of "Rocky" you will see a human interface for people and their browsers to interact with Rocky. By contrast, the programming interface is for other web sites to interact with Rocky, or indeed any software including mobile apps and FaceBook apps. Another web site could implement its own separate human interface -- different branding, different workflow -- while a mobile app could assist the user by pulling information stored on the mobile device. But either way, the web site or mobile app does not need to have any back-end. Instead, they rely on Rocky for checking user data, constructing PDFs, storing registrant data, sending email reminders, and so forth.
As a result, we've substantially lowered the cost in time and effort for any elections officials or NGOs to develop and deploy their own online-voter-assistance system, by opening up Rocky to be the back-end for these systems, so that all the complexity -- and cost of deployment! -- of the back-end functionality just drops out of these systems. No database to set up and manage, no computational heavy lifting. For organizations that already have a web site, it can be as simple as adding one or a few new forms pages, with a link to Rocky that will submit the voter's registration information, and present back to the user the PDF with their completed form and mailing instructions.
Any organization can use Rocky via the API in this way, including local elections offices that already have a Web site that they can update to use the Rocky API. And for local election officials in particular, there is an additional benefit. Via the API they can obtain a digital copy of the voter registration form data, and a tracking number. When the signed paper form arrives in the mail, they can type or scan in the bar-coded tracking number, and get the form data, so that they don't have to retype all the information on the form -- a time consuming (and in peak voter registration season, expensive) task with much scope for human error.
There's a lot to like about this approach, but it gets even better. In an upcoming release there will be even more features that will help organizations have the very own Rocky OVR system, but without having to have an existing web site that is easy to modify. Depending on how fancy an elections org wants to customize the look and feel, it could be a matter of a couple hours work to get up and running. Even better! More on that when the system is live.
Much of OSDV's currrent work relates to election technology for voter registration.* In recent blog posts, I've been talking about voter registration in the context of OSDV's mission to put much needed, innovative election technology into the hands of elections officials and voters who are underserved by the best that the for-profit election technology market has been able to deliver so far:
- clunky, arcane, and opaque registration systems,
- clunky, arcane, and opaque adminstration technology, and
- voting systems that don't accurately record votes.
(The latest in the latter saga of woe is NY state BoE's report from an investigation of how the "phantom vote" phenomena manifested itself in voting systems that recorded votes not actually cast by anyone.)
Specifically for voter registration, among the many needs is one at the front end of the process: just getting people to fill out the administrative forms that are required for voting "eligibility management:
- register to vote,
- update a voter record,
- request an absentee ballot or absentee status,
or the even more arcane forms that overseas and military voters use for
- the same purposes but with different administrative rules, plus varying state-specific requirements.
The good news for citizens of the Commonwealth of Virginia is that help is on the way, with a new voter service that will step a voter through each of several complex and VA-specific application forms and combinations -- and produces properly formatted paper documents that regular people can actually understand, both voters before they sign and mail the forms, and local election officials who process them.
But what about other states and localities that don't have the resources for the type of comprehensive project that the VA SBE has undertaken with OSDV and other participants? The good news for them is that there is a middle way. We took the first step a couple of weeks ago when we went live with a new release of the "Rocky" OVR assistance system operated by RockTheVote and hosted by Open Source Labs. The main feature of the new release was a web service application programming interface (API) that provides access to all of the Rocky functions. However, rather than via a browser of a user, the API provides those functions to other web sites.
How is that a benefit to elections officials, and a public benefit to voters? Sorry to make this post a cliff-hanger, but the explanation of the API will have to wait for next time. Stay tuned, it's worth it!
* (As some readers may have figured out already, even-numbered years to focus on registration and reporting as the voter-visible bookends of an election, while odd-numbered years have more focus on the mechanics of casting and counting ballots and data interperability to enable public transparency.)
As I wrote last time, I had the wonderful opportunity to observe a citizenship oath ceremony. It had a big emphasis on voting, and included San Francisco elections department people on hand to help the new citizens register to vote. Today, I wanted to share the flip side of what I saw, and I want to start to connect it to some election technology work that we're doing now -- work that I think can deliver some real public benefit. After the ceremony, I saw a real distinction between two groups of people. One group was clearly enthusiastic about voting as a benefit of their new citizenship. Some had already filled out the somewhat cramped and confusing voter registration application form from the packet of many administrative documents they were handed earlier. Others very sensibly got some help in filling out the forms by walking up the the table where the elections division folks were offering to help people with the form. Either way, most of them were very appreciative of the elections folks being there to help and to make sure that the completed forms got to the right place quickly.
Another group was markedly un-interested, despite the encouragement to vote, in the dealing with yet another form, more government officials, and an additional disclosure of personal info to yet another part of the government. I found it sad but understandable. But for part of this group I also felt frustrated, because I was seeing right in front of me a form of barrier to franchise, albeit largely unintentional. The enthusiastic group tended to be younger, more voluble and confident speaking English (for most of the new citizens, English is a second or third language - about 2/3 of the new citizens that day were born in El Salvador, Mexico, or the Philippines), and more technologically literate (if fiddling with a smart phone is a sign of that). The rather sizable less enthusiastic group had a lot of grandparents being assisted by younger family or friends.
For these people, the application form might well be daunting: two pages of instructions in small font in addition to a form with little boxes that are hard to read for anyone, much less a user of reading glasses. And for those who actually read the instructions, there is some real confusion over whether you can vote if you lack a driver's license or SSN. (I expect that some people lacked one or maybe both.) More vexing, the elections department people told me how conscious they were about people's need for help in doing the application form correctly, and having to deal with more paperwork, and having to take the initiative to walk over to speak to more government people, in order to get the help.
In fact, one of them said that they wished they had the voter registration form on an iPad, and each of them could work the crowd with iPad in hand to get people filling the form with as large print as needed, in whatever language was convenient, with as much online assistance as possible, and no pages of daunting instructions. That really great idea really got to me, because I had 90% of it on my laptop in my backpack. I could have pulled out the laptop, which like an iPad, could be used for browser access the online voter registration assistance service that's operated by RockTheVote, with OSDV/TrustTheVote technology that I helped build. We were so close to what the elections folks needed to be more helpful to the people standing right there!
But even with a few iPads and a printer and wireless network to connect them, the elections department folks would not quite have had what they need: an online voter registration (OVR) assistance system that is used by the government, not by an NGO that might (incorrectly) be construed as partisan. Particularly in the setting of the citizenship oath ceremony -- outside, a madhouse of partisan political organizations clamoring for attention -- the government folks need to be using government systems.
And they don't have it, at least not most elections folks, even though it is so close.
So what we need to do is get this OVR technology delivered in a way that lots of elections officials can adopt quickly, adapt and localize quickly and easily, and get into production operation quickly and easily without having to spend a bunch of money, with all the government procurement hassles that that would entail.
We need to do that; the citizenship ceremony experience made that plain, as well as the government officials' need, and so … well, so we are doing that, specifically, right now. More on details next time.
I'm sitting in the historic grand Paramount Theater in Oakland, California. Perhaps an odd place from which to return to blogging after some time, but I wanted to re-start on a personal note that's also quite connected to the voter registration technology work that we've been doing over the last many months. I've just witnessed a naturalization ceremony where 994 people (one of them very special to me) from 104 nations have taken an oath to become citizens of the United States of America. It's impossible for this to sound other than trite, but it's true: these people worked hard -- some of them very hard indeed -- to reach this point, while all I had to do was be born. It is so inspiring that I think everyone should witness one of these ceremonies, to really get a feeling for what it is like to choose to be an American.
And (no surprise) for me a big part of being American is voting. That's why I was so pleased and thrilled with the amount of time in this ceremony devoted to voting rights and elections and participation. But just as gratifying to me was the presence of election officials from the San Francisco elections division, who briefed the audience in 3 languages on how they should register to vote. And the easiest option that they offered -- and kudos to them for it -- was to fill out the voter registration form that was already in their hands, and bring it to their table in the lobby. There, the elections division folks made sure the form was complete and correct, and took the completed forms right then and there, no mailing required, even for other counties than San Francisco. They even let me help pass out forms to people in line, in case they didn't get one.
My personal experience was great, but also a cause for some reflection on the experience of others present in the theatre. But because this has been a great day, I'll save those reflections, including a technology angle of course, for a better time to consider room for improvement via technology.
At the end of our last visit to the fictional Town of Bedrock, we left Fred as he applied to run for mayor. Now we'll continue the story, but with a focus on Bedrock itself, in order to continue building up a detailed, yet simplified, account of actual U.S. election practice. The focus is on Bedrock rather than its colorful denizens, because the answer to the current question -- can Fred be a candidate for mayor in the upcoming election? -- lies partly in the details of Cobblestone County and Town of Bedrock, how they are structured and administered for elections. At a first glance of the Bedrock County map, you'll see that the Town of Bedrock is entirely in Cobblestone County, dividing the county into two regions, the part that is incorporated in the Town, and the unincorporated portion.
Look a bit more closely though, and you'll see the Mineral District -- not a town but a political division called an electoral district (in some states in the U.S., called a jurisdiction rather than a district). The Mineral District in the part of the county that's affected by quarrying operations at the Bedrock Quarry, and the Bedrockites who live there get to elect the Quarry Commission to regulate the Quarry. Look a bit more carefully and you'll notice that part of the Mineral District is in the Town of Bedrock, and the rest is in the unincorporated county.
To keep our Election Tale simple, that's almost all of the electoral structure of Cobblestone County that is the jurisdiction of the Bedrock BoE. The remaining part may be a bit more familiar: the precincts. Each precinct is a region in which all of the voters are entitled to vote on exactly the same ballot items; put another way, in one precinct all of the voters reside in exact same set of electoral districts. So in Bedrock County, there are 4 precincts:
- The "Downtown-001" precinct, part of two districts: the district of the Town of Bedrock, and the district for Bedrock County;
- The "Quarrytown-002" precinct, part of those same two districts, plus the Mineral District;
- The "QuarryCounty-003" precinct, part of the Mineral District and the County;
- The "County-004" precinct, part of just the district for the County.
Looking a little more carefully, you'll notice the Flintstone residence is in the QuarryTown-002 precinct, which means the Flintstones (or at least those of them that are registered voters) are eligible to run for offices in either the Town or the Quarry District. To say that more generally, in order to be eligible to run for an office, you have to reside in the district that the office is part of. Fred wants to run for Mayor of the Town of Bedrock, so he has to reside in the Town of Bedrock.
Back at the BBoE, Rocky has completed the eligibility check for Fred, having ensured that:
- he resides in the Town of Bedrock,
- he is registered to vote,
- his current address matches the address in his voter record,
- he is not serving jail time,
and perhaps some other eligibility requirements in Stone Age election law that we are not aware of. Fred is satisfied to find that on the Bedrock slab-site's Upcoming Election slab, he is listed as a candidate for mayor. However, there is also a bit of a surprise: his neighbor Betty Rubble is running against him! And also Barney Rubble is running for Fred's old Quarry Commission seat. Also, the commission's clerical errors seem to have been resolved, and the quarry fee referendum will be on the ballot. With a few more days of filing time left, an irritated Fred ponders who lives in the Mineral District, that might be convinced to run against Barney.
Next Time: it's time for ballot design - get out your Chisel!
I came across an interesting article about voter registration: "The Alternative to Universal Voter Registration" where John N. Hall strongly supports Automatic Registration (AR) over Universal Voter Registration (UVR). To people who are not election experts the distinction is a bit subtle. UVR has states proactively try to register everyone to vote, while AR has the federal government somehow use Social Security records to automatically register people.
In Mr Hall's words, AR can be implemented by doing the following:
"Computer programs read through the Social Security Administration database, extract the data of age-eligible citizens, then send that data to the states." (from The Alternative To Universal Voter Registration)
Now that I started writing this post and did some more googling I see that this is already a heavily debated topic that has flown back and forth, starting with John Fund's (of the Wall Street Journal) original talk, to Rep. Barney Frank's angry denunciation that he had nothing to do with the claims that he was involved in any way with Universal Voter Registration, to Mr Fund's retraction of the claim, to more links than you can shake as stick at about the topic.
Anyway as usual I am johnny come lately. Phew. My original thought though was about the original post. You see, John Hall, being a "computer programmer" makes it sounds simple:
"Voila! Why make mandates on all those state agencies and dragoon all that manpower entailed by UVR when a computer program can register everyone? A competent programmer could write the extract program in his sleep." (from The Alternative to Universal Voter Registration)
Any description of this that starts with "Voila" and ends with "in his sleep" is ... well let's just say, it must be a bit of a simplification....
For example I would imagine that there would be major privacy concerns about sending information out of the social security systems out to each of the states. I am not sure that the states registration records even include social security information. And what about all the voters who don't have social security numbers, there must be some, or many? And how quickly are the social security databases updated when people die?
Twelve days ago without a lot of fanfare and perhaps overshadowed by the MOVE Act enactment, the House took a small step forward in pushing a modest voter registration modernization initiative when Congressman Kevin McCarthy, who is the most senior Republican on the House Administration Subcommittee on Elections, introduced the Responsible Online Voter Empowerment Registration Act (H.R. 4449). Of course, those looking over the innovation horizon will always return to the same question of whether voter registration shouldn't be an opt-out verses an opt-in matter. I'll leave that policy food fight for others, but will point out that there can be no "Frankenswitch" solution to modernizing voter registration. In other words, even if more aggressive voter modernization initiatives are to succeed -- such as declaring every citizen who attains the age of majority in their State as de-facto registered to vote unless they otherwise opt-out, there will be a need to manage one's registration details and status. And that will, for some time to come, require the appropriate technology to do so. In a digital age, that means online services, which brings us back to Representative McCarthy's legislation introduced on Wednesday the 13th.
Rep. McCarthy introduced this legislation to increase states’ online voter registration services without compromising existing safeguards that protect against fraud. Congressman McCarthy issued the following statement:
In an era of unprecedented technology, I am pleased that we could work with election officials across the country to produce a solution that will provide incentives for states to implement online registration programs that will increase accuracy, protect against fraud and reduce administrative costs. As Americans utilize more technology in their daily lives, it is important that the systems that are used to elect our official representatives at all levels stay up-to-date to allow all voters to let their voices be heard on election day.
H.R 4449 provides incentives for States to implement online registration services that should (the Congressman's web site reports "will" and we'd be inclined to agree, but prefer to wait and see due to some of the potential complications of the clerical processes involved) increase the accuracy of registration records, reduce the administrative costs associated with data entry, and protect against the processing of fraudulent registrations by requiring voter eligibility and identity verification.
Kewl. For those who've been paying closer attention, you'll recognize those points from many of our writings in recent months. We applaud the Congressman's initiative and hope it comes out of Committee and reaches the House floor for a vote. Its a small, but necessary step in the direction of modernizing one of the most important components of America's aging elections technology framework.
Now, if we could only get Congress to acknowledge that the Nation's elections technology is tantamount to critical democracy infrastructure (our words) and as such, should be open, transparent, publicly owned technology. That's another step for another day; easier to take once there stuff that people can see, touch, and try.
We have a special treat today with a guest blog from Barbara Simons, an eminent computer scientist who is on the Board of Advisors of the U.S. Election Assistance Commission. (More on Barbara: her bio.) She has an excellent account of part of the story about where voter registration came from, and why it is controversial that U.S. citizens must proactively request permission to vote, and then pass muster w.r.t. eligibility requirements as evaluated by an election official. The controversy, in a nutshell, is that registration can be a way of preventing people from voting, including via the practice of disenfranchising felons. So where did the practice of registration, and the controversy, come from? Barbara: take it away ... [Ed. Note: The following commentary from Barbara Simons incorporates for referential, historical, and explanatory purposes only quotations that by any standard today would be considered controversial, inappropriate, and simply reprehensible. They are only quotes pulled from history to explain the point and are not the opinions or positions of Ms. Simons, the TrustTheVote Project, or the OSDV Foundation.]
Felon disenfranchisement was introduced in the South after the Civil War as a way of disenfranchising the newly freed slaves. Southern whites even invented new felonies that were applied almost exclusively to African Americans. Here are some quotes from that era.
From a Mississippi Supreme Court decision upholding the state's disenfranchisement law (Ratliff v. Beale): "The [constitutional] convention swept the circle of expedients to obstruct the exercise of the franchise by the negro race. By reason of its previous condition of servitude and dependence, this race had acquired or accentuated certain peculiarities of habit, of temperament and of character, which clearly distinguished it, as a race, from that of the whites -- a patient docile people, but careless, landless, and migratory within narrow limits, without aforethought, and its criminal members given rather to furtive offenses than to the robust crimes of the whites. Restrained by the federal constitution from discriminating against the negro race, the convention discriminated against its characteristics and the offenses to which its weaker members were prone."
The following is from John Field Bunting, who introduced disenfranchisement legislation in Alabama in 1901: "The crime of wife-beating alone would disqualify sixty percent of the Negroes." Perhaps the bluntest acknowledgment of the purpose of the felon disenfranchisement laws was provided by Carter Glass, a delegate to the Virginia Constitutional Convention in 1902. Glass stated that Virginia's felony disenfranchisement scheme
... will eliminate the darkey as a political factor in this State in less than 5 years, so that in no single county will there be the least concern felt for the complete supremacy of the white race in the affairs of government.
The end of Reconstruction marked the beginning of disenfranchisement for the newly freed slaves. In the South during the Jim Crow era that followed, African Americans were prevented from registering by a combination of poll taxes, literacy tests, felon disenfranchisement, and threatened or real violence. For example, there were 130,334 African American voters in Louisiana in 1896, but only 1,342 in 1904.
According to "Registration of Voters in Louisiana": "Six pages of [the Constitution of 1898] are devoted to suffrage and elections. The object of the convention was, of course, to establish white supremacy by reducing the number of Negroes voting to a minimum. The qualifications to vote as well as
the entire system of registration were written in such a way that most Negroes could be disenfranchised.
Other clauses were incorporated to permit the poor white to vote and yet not admit the Negro to the ballot."
Felon disenfranchisement laws still have a disproportionate impact on African Americans. Only Maine and Vermont (both of which have small African American populations) have no felon disenfranchisement laws. Felons can vote from prison in those states. Southern states are disproportionately represented among states with the extensive felon disenfranchisement laws, as are states with large non-white prison populations. African American males have been significantly impacted, with roughly one in six disenfranchised in the early 21 century because of felony convictions.
It seems likely that if the U.S. didn't engage in felon disenfranchisement that a number of election results, including at the presidential level, would have had different outcomes. The U.S. is the only democracy that has lifetime felon disenfranchisement. We are still living with the legacy of slavery.
-- Barbara Simons
PS: Thanks again to Barbara for a valuable history lesson of background for our work at TTV to include registration as a legally required part of a broader effort voter record management technology, that also includes some of the changes contemplated by the "election modernization" efforts in Congress. -- John Sebes, CTO TrustTheVote Project
Yeah this is old hat to election-insiders (I am not yet one, so I can still have that sense of wonder :) but I just took a drive through the "Voting Information Project" web site. I think it's a cool idea that could be a template to catalyze very useful election related information resources in a totally decentralized manner, where each state or locality can elect when and how to join in. In case you haven't heard about it, this is from their site:
"...As a fundamental step in this initiative, the Voting Information Project is partnering with a group of state election officials to develop and implement a technical standard, known as an "open format," by which state and local election officials can more efficiently disseminate voting information. " (from Voting Information Project)
If a state chooses to provide election related information in this format, at a known URL, this information will be pulled into the VIP system and in turn be deliverable to web sites, cell phones, twitter, facebook, yadi yada.
In other words, the one fairly simple piece of work is leveraged multiple times and brought to where it can be used by voters. Pretty cool, and maybe a template for decentralized adoption and deployment of election info services of other kinds in the future.
Here's the FAQ of the Voter Information Project.
The Military and Overseas Voter Empowerment (MOVE) Act is probably not high on your radar screen of activities in the U.S. Congress -- but it is important to me, for two reasons, aside from the most basic one that it enables broader access for overseas voters.
- The bill avoided partisan politics that usually sidelines any election reform.
- The bill calls for sensible, incremental use of technology, including the Internet, to help voters.
I recommend the excellent National Journal Online article for a more in-depth view behind the scenes, with quotes from some of the organizations that helped identify the problem and its scope, and suggest solutions -- such the Pew Center on the States, and Brennan Center for Justice at New York University's School of Law. The article also has a concise look at the current Congressional activity around technology and election reform - in the area of voter registration. My thanks to Eliza Newlin Carney for this fine reporting.