As stated in the note from the Sunlight Foundation′s Board Chair, as of September 2020 the Sunlight Foundation is no longer active. This site is maintained as a static archive only.

Follow Us

Tag Archive: OpenGov

Boilerplate Open Data Policy and Why It’s a Problem

by

In preparation for the revamping of our Open Data Policy Guidelines, we reviewed all twenty-three  of the current local (city, county and state) open data policies on the books since their debut in 2006. These “open data policies” ranged in form from government administrative memos ordering the release of “high-value” datasets to legislation calling for open data policy planning to the newest member of the open data policy family, South Bend, Indiana’s executive order. Our main takeaway: There has been a lot of copying and pasting amongst policies, confusion on common open data terminology, and missed opportunities for information disclosure, but best practices are emerging.

Copying and pasting boilerplate legislative language is as old as law itself. In fact, legal precedent is built on throwbacks, edits, and remixes. The modern day copying and pasting feature has served as a technological blessing in legal matters that require a high level of repetition, such as producing demand letters for common legal claims, or, for one of Sunlight’s favorite exercises of individual rights, completing a public records or freedom of information request. However, when copying and pasting enters more nuanced areas of law, such as contract or legislation drafting, significant complications can arise. Without the proper edits or engaged collaborative thinking required in policy drafting, the ever tempting copy/paste model falls short. Below we explore just how borrowed open data legislative language thus far has been and examples of where it’s been the least helpful.

Continue reading

Empowering The Open Data Dialogue

by and

The first question most open data advocates hear is, “Why?” Whether you’re trying to make the case within government or coming in from the outside, many, many advocates in our space spend a lot of time justifying open data’s potential instead of playing with its possibilities. We crowdsourced ideas that can help answer questions and move the conversation along.

Continue reading

Reasons to Not Release Data, Part 10: Say What?

by and

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, Say What?, celebrates a grab bag of challenges.

Continue reading

Reasons to Not Release Data, Part 9: “Already” Public Data

by and

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.

servers

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 "Already" Public Data. (Kudos if you find the Easter Egg.)

 

Continue reading

NYC’s Plan to Release All-ish of Their Data

by

nycdata

On Monday, September 23rd, New York City released a plan to, as Government Technology put, open “all” its data. Pursuant to section two of Local Law 11 of 2012 (§23-506 of the Administrative Code of the City of New York) — also known as NYC’s Open Data Policy — the long awaited agency compliance plan does complete the monolithic task of  listing all NYC agency public datasets, with scheduled release times of no later than the end of 2018, but there are ways it could have been more inclusive and comprehensive.

Continue reading

CFC (Combined Federal Campaign) Today 59063

Charity Navigator