Earlier this month, we shared a crowdsourced collection of the top concerns data advocates have heard when they’ve raised an open data project with government officials at the federal, state, and local level, and we asked for you to share how you’ve responded. Dozens of you contributed to the project, sharing your thoughts on social media, our public Google doc, and even on the Open Data Stack Exchange, where 8 threads were opened to dive deeper into specific subjects.
Drawing from your input, our own experience, and existing materials from our peers at the National Neighborhood Indicators Partnership and some data warriors from the UK, we’ve compiled a number of answers -- discussion points, if you will -- to help unpack and respond to some of the most commonly cited open data concerns. This mash-up of expertise is a work in progress, but we bet you’ll find it a useful conversation starter (or continuer) for your own data advocacy efforts.
Click here to see other posts in this series.
Over the next few weeks, we’ll be sharing challenges and responses from our #WhyOpenData list that correspond to different themes. Today’s theme is Difficulty.
Continue readingReasons to Not Release Data, Part 2: Confusion
Earlier this month, we shared a crowdsourced collection of the top concerns data advocates have heard when they’ve raised an open data project with government officials at the federal, state, and local level, and we asked for you to share how you’ve responded. Dozens of you contributed to the project, sharing your thoughts on social media, our public Google doc, and even on the Open Data Stack Exchange, where 8 threads were opened to dive deeper into specific subjects.
Drawing from your input, our own experience, and existing materials from our peers at the National Neighborhood Indicators Partnership and some data warriors from the UK, we’ve compiled a number of answers -- discussion points, if you will -- to help unpack and respond to some of the most commonly cited open data concerns. This mash-up of expertise is a work in progress, but we bet you’ll find it a useful conversation starter (or continuer) for your own data advocacy efforts.
Click here to see other posts in this series.
Over the next few weeks, we’ll be sharing challenges and responses from our #WhyOpenData list that correspond to different themes. Today’s theme is Confusion.
Reasons to Not Release Data, Part 1: Apathy
As many open access advocates, journalists, and government employees will tell you, broaching the subject of data disclosure can raise a lot of concerns for government data providers. Pioneers looking to move their government toward exploring information release have already come up with rebuttals to many of these challenges, but the collective knowledge is hard to share, usually trapped in email groups, discussion boards, blogs, and the memories and experiences of individuals. In the wake of re-releasing our Open Data Policy Guidelines, we wanted to probe these concerns and see what information we could share that data advocates could keep in their back pocket.
So, earlier this month, we shared a crowdsourced collection of the top concerns data advocates have heard when they’ve raised an open data project with government officials at the federal, state, and local level, and we asked for you to share how you’ve responded.
Dozens of you contributed to this project, sharing your thoughts on social media, our public Google doc, and even on the Open Data Stack Exchange, where 8 threads were opened to dive deeper into specific subjects. We also learned about resources akin to this one from our peers at the National Neighborhood Indicators Partnership and this awesome, bingo-card inspired round-up from the UK made by Christopher Gutteridge and Alexander Dutton. (The latter has even been translated into German!)
Drawing from your input, these materials, and our own experience, we’ve compiled a number of answers -- discussion points, if you will -- to help unpack and respond to some of the most commonly cited open data concerns. This is mash-up of expertise is a work in progress, but we bet you’ll find it a useful conversation starter (or continuer) for your own data advocacy efforts.
Over the next few weeks, we’ll be sharing challenges and responses from our list that correspond to different themes. You can follow along on our blog and on Twitter via #WhyOpenData. Today’s theme is Apathy.
Reasons (Not) to Release Data
Earlier this year, Sunlight was issued a challenge: Collect and refute the most common reasons not to release data. As many open access advocates, journalists, and government employees themselves will tell you, there are a variety of "no's" given when the question of data disclosure arises. Many are predictable, some are political, some personal, many practical, and all deserving of attention. Pioneers looking to move their government toward exploring and advancing information release have already come up with rebuttals to many of these refusals, but the collective knowledge is hard to share, usually trapped in email groups, discussion boards, blogs, and the memories and experiences of individuals. So, we're going to meet our challenge with an experiment.
Continue readingOpen Data Creates Accountability
A series of recent blog posts raised questions on the value of open data and transparency. While thoughtful skepticism is constructive, there appears to be some significant confusion about the meaning of “open data," and about transparency and accountability. When activist developers like Aaron Swartz are concluding that “the case for opening up data to hold government accountable simply isn’t there,” or former government leaders like Beth Noveck are suggesting that there are “serious doubts” whether “open data” make government “more transparent or accountable,” then it’s time to engage. We should clarify something straight away -- this term “open data.” Open data wasn’t invented in 2009; open data isn’t born in a data portal. Construed most broadly, open data is people knowing things with technology. This information can be tabular, or not, structured, or not (though our preferences are clear.) When people ask whether open data can create government accountability, they’re essentially asking whether it’s helpful to know things about the government, and, strangely, coming up with uncertain answers. These answers are flawed, in part, because “open data” is being narrowly conceived of as the thing that fuels data contests and populates data portals, that is, the thing that sprang into vogue as Obama came into power. While Sunlight has been deeply involved in the last 3 years of “open data,” we’re also deeply grounded in the last 50. Every bit of open data we have now to be mashed up, evangelized, or opened exists, in part, through the accountability laws and norms that decades of work have created, about where citizens stand before their governments, and vice versa. If our first question is “does knowledge of government create accountability,” then the answer is clearly, definitively yes. Knowledge of the government creates accountability. As surely as ignorance and secrecy empower manipulation and abuse, information and knowledge empower self-determination. This is baked into Sunlight’s mission -- the idea that understanding the government changes how it works. The Brandeis quote that is the source of Sunlight’s name encapsulates that idea, and our work is intended to embody it. To suggest that open data can’t create accountability is to ignore the open data that helps create the accountability we already enjoy, and work to strengthen.
Continue reading- « Previous
- 1
- 2
59063
