How do municipalities measure up to standards for releasing campaign finance data? Today, we look at Albuquerque.
Continue readingOpen Data Policies to Promote Transparency and Engagement
In an upcoming session at the National League of Cities Congress of Cities and Exposition in Seattle, we'll take part in exploring how open data, and open data policies, can help increase and improve civic engagement.
Continue readingA Roadmap for Releasing Municipal Campaign Finance Data
We've created a Municipal Campaign Finance Data Guidebook to help local policymakers and advocates create stronger disclosure around this crucial information.
Continue readingThe Impact of Opening Up Municipal Campaign Finance Data
What kinds of information municipalities release about campaign finance and how they release it varies widely, but the impacts that come from its release are fairly universal.
Continue readingBoilerplate Open Data Policy and Why It’s a Problem
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 readingThe Landscape of Municipal Campaign Finance Data
With our new municipal focus, we were curious: What does local campaign finance disclosure look like?
Continue readingEmpowering The Open Data Dialogue
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 readingReasons to Not Release Data, Part 10: Say What?
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 readingReasons to Not Release Data, Part 9: “Already” Public Data
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 "Already" Public Data. (Kudos if you find the Easter Egg.)
Continue reading