Since the release of Sunlight’s Open Data Policy Guidelines last June, Chicago, Madison, Montgomery County, and Utah have all enacted open data laws, and the states of Hawaii and Ohio are both in the process of enacting open data legislation. However, the recent amendment of San Francisco’s two-and-a-half-year-old open data ordinance (ancient in the open data policy world) demonstrates a new frontier for these policies: Evolution.

San Francisco is unique in having been one of three cities to have an open data policy enacted before the federal Open Government Directive and in being the only city that has revamped their open data policy not once, but twice: first in 2010, expanding their bare bones 2009 executive order into a longer, more robust administrative code, and for a second time in late March 2013, amending the administrative code language.

Sunlight identified in our Open Data Policy Guidelines the importance of future review for potential changes to policy and law, and we were glad to see that San Francisco’s most recent amendment not only incorporated many more of Sunlight’s Guidelines, but also broke ground in the United States municipal open data policy world -- arguably taking the title from New York City. Of significance, San Francisco’s amended ordinance creates new oversight authority to review implementation of their open data policy requirements (Sunlight guideline #27) by creating the position of Chief Data Officer (CDO) and requiring the appointment of Department Data Coordinators (DCs) to assist in the implementation of San Francisco’s open data policy. The CDO is tasked with working with DCs to create an open data plan for each Department including: “a timeline for the publication of the Department’s open data and a summary of open data efforts” (#22) and “a summary description of all data sets under the control of each Department” (#18). The CDO is also responsible for creating an annual citywide implementation plan, while each department is delegated to conduct quarterly reviews of their progress, the combination of which sets up procedural expectations that help ensure data quality (#17). The amended language also calls on the CDO to produce analytics on the use of San Francisco’s data portal, DataSF, (as recommended by guideline #32 and incredibly important in determining usefulness and in cost benefit analysis), but unfortunately does spell out specific requirements of these analytics.