Sunlight Labs

Last week Clay wrote about how we'll be evaluating /open pages released under the OGD. The post ended with a series of considerations that we think are important: completeness, primacy, timeliness, accessibility, machine readability, availability without registration, being non-proprietary, freedom from licensing restrictions, permanence and obtainability.

One thing is conspicuously missing from the list, though: quality.

We spend a lot of time talking about how Government does a lot wrong with data. And we harass them and complain a lot to the extent that even I get on my own nerves. But the fact is, the people and programmers working on these projects on the inside are neither malicious nor incompetent. The problem isn't people, but a weird system of priorities and incentives that often leaves the citizen short-handed. After all, transparency isn't even an inkling the constitution (yet!) and I'm fairly certain that the framers of our constitution weren't really considering data portability when they drafted the Bill of Rights.

The new Recovery.gov-- which we've written about and even nearly bid on-- has certainly taken the government huge steps forward in terms of disclosing information, but it is not without controversy. The press is questioning the program, pointing to wasteful spending or bad data. The White House fired back with a "reality check"(their words) saying that few of the reports have gone through the "extensive three-week review" and that the data might be particularly misleading at this point.

As of today Android and iPhone users can see recovery.gov contract data on their phones via the Layar augmented reality application. Layar is an application that overlays your view of the real world with waypoints representing your favorite coffee place, the movie theatre you're trying to find, or in this case, where some of that $787 billion from the American Recovery and Reinvestment Act is going.

Recovery.gov relaunched yesterday, and we've spent some time playing around with the site since then. The verdict? Well, it's hard to say — the site's a bit broken. There are 404s all over the place, most gallingly on the data download page. Parts of the site seem like they work, but don't: the select boxes on the front page that provide filters for the map don't actually affect its behavior in any way. It's hard to see these glaring bugs alongside the totally-unnecessary link to Facebook and not groan (am I supposed to play Scrabble with Chairman Devaney?).

Here at the Sunlight Labs, we've focused a lot on the recent bid on version 2.0 of Recovery.gov. This morning on the Labs mailing list, Rusty Talbot of Synteractive, one of the winning contractors, asked for input on the best way for Recovery.gov to publish its data.

Rusty wrote:

The Recovery, Accountability, & Transparency Board wishes to have an open discussion with all interested developers about how data should be made available via Recovery.gov.

As you are all aware, a new version of Recovery.gov will be released soon. From a data standpoint, the initial release of the new site will replicate existing functionality. However, the Board aims to set a new standard of transparency with this site and would therefore like to make the data available in the most convenient and straightforward way (or ways) possible so you can use and analyze official, up-to-date Recovery Act data. We need your input to achieve this goal.

Please let us know how the site could best meet your needs in terms of machine-readable data format(s) and standards, APIs, guidance, training, etc.

This is a great opportunity for all of us who work hard to make government data more open and accessible.

A long time ago, my grandmother-- born and raised in Albany, Georgia-- went to Germany for my brother's wedding. She'd never been outside the country before and was excited about the trip, and of course, her grandson's wedding. While she was there though, she had a bit of a problem communicating-- see, she didn't speak German. Her solution to the problem was instinctive but not logical-- just speak English loudly and slowly. Increase volume until there's understanding. One person she encountered over there responded to her by speaking German loudly and slowly.

Her response:

Here's the proposal that was released by the Recovery board on Friday. Lots of redactions, but it should serve two purposes-- one, to let us see what they're working on, and two, to let us figure out how to write these proposals.

Can you match the colors in the pie chart with the legend below?

From usaspending.gov

Last week, we announced that we were going to bid on Recovery.gov. Here, 9 days later we have a few pages of information on our bid, but I don't think it makes sense to turn anything in tomorrow. So I'm declaring this experiment a failure. Most people confuse "failure" with being "wrong" but here in the Labs, we're into experimentation -- and you can't experiment or push the ball forward if you're afraid to fail.

This was a completely worthwhile experiment and we've learned a lot. I want to share some of the reasons why we failed, and what we've learned with all of you: