City of Syracuse Open Data Policy
Shared for feedback by City of Syracuse
City of Syracuse Open Data Policy
City of Syracuse Open Data Policy
Section 1: Purpose
This policy establishes guidelines for an open data program in the City of Syracuse. The city collects and creates large amounts of valuable information on aspects of life in Syracuse. Through this program, the public as well as internal departments and bureaus, will have faster and easier access to data and information via an online portal. The city recognizes that making data available in this way increases civic engagement, internal efficiencies, and transparency, while also fostering communication. It is also anticipated that this will improve government efficiency for the Freedom of Information Law (FOIL) officer and various staff who must satisfy FOIL requests. Data will be gradually released in a responsible manner, consistent with relevant public records law, and in consultation with the appropriate department heads. The information will be released in machine-readable formats. Finally, the protection of privacy, confidentiality and security will be maintained as a paramount priority while also advancing the government’s transparency and accountability through open data.
Section 2: Definitions
- “Data” means statistical, factual, quantitative, or qualitative information that is maintained or created by or on behalf of a city agency.
- “Open data” means data that is available online, in an open format, with no legal encumbrances on use or reuse, and is available for all to access and download in full without fees. “Legal encumbrance” includes federal copyright protections and other, non-statutory legal limitations on how or under what conditions a dataset may be used.
- “Machine-readable” means data in a format that can be automatically read and processed by a computer, such as CSV, JSON, and XML. Machine-readable data is structured data.
- “Dataset” means a named collection of related records, with the collection containing data organized or formatted in a specific or prescribed way, often in tabular form.
- “Protected information” means any dataset or portion thereof to which an agency may deny access pursuant to New York State’s Freedom of Information Laws or any other law or rule or regulation.
- “Sensitive information” means any data which, if published by the city online, could raise privacy, confidentiality or security concerns or have the potential to jeopardize public health, safety or welfare to an extent that is greater than the potential public benefit of publishing that data.
- “Publishable data” means data which is not protected or sensitive and which has been prepared for release to the public.
Section 3: Open Data Program
-
The city commits to develop and implement practices that will allow it to:
- Proactively release all publishable city data, making it freely available in open formats, with no restrictions on use or reuse, and fully accessible to the broadest range of users to use for varying purposes;
- Publish high quality, updated data with documentation (metadata) and permanence to encourage maximum use;
- Provide or support access to free, historical archives of all released city data;
- Measure the effectiveness of datasets made available through the Open Data Program by connecting open data efforts to the city’s programmatic priorities;
- Minimize limitations on the disclosure of public information while appropriately safeguarding protected and sensitive information; and
- Support innovative uses of the city’s publishable data by agencies, the public, and other partners.
- The development and implementation of these practices shall be overseen by the Chief Data Officer, reporting to the Chief of Staff.
- The requirements of this policy shall apply to any city department, office, administrative unit, commission, board, advisory committee, bureau, or other division of city government, including the records of third party agency contractors that create or acquire information, records, or data on behalf of a city agency.
- Priorities for data release will be determined by the Chief Data Officer with guidance from heads of departments or assigned designees, input from the public, and ultimately approval by the corporation counsel’s office and the Mayor or another top-level administration designee.
Section 4: Governance
-
Implementation of the Open Data Program will be overseen by the Chief Data Officer, who will work with the city’s departments to:
- Identify and publish appropriate contact information for a lead open data coordinator who will be responsible for managing that agency’s participation in the Open Data Program;
- Oversee the creation of a comprehensive inventory of datasets held by each city agency which is published to the central open data location and is regularly updated;
- Develop and implement a process for determining the relative level of risk and public benefit associated with potentially sensitive, non-protected information so as to make a determination about whether and how to publish it;
- Develop and implement a process for prioritizing the release of datasets which takes into account new and existing signals of interest from the public (such as the frequency of public records requests), the city's programmatic priorities, existing opportunities for data use in the public interest, and cost;
- Proactively consult with members of the public, agency staff, and other stakeholders to identify the datasets which will have the greatest benefit to city residents if published in a high quality manner;
- Establish processes for publishing datasets to the central open data location, including processes for ensuring that datasets are high quality, up-to-date, are in use-appropriate formats, and exclude protected and sensitive information;
- Ensure that appropriate metadata is provided for each dataset in order to facilitate its use;
- Develop and oversee a routinely updated, public timeline for new dataset publication; and
- Ensure that published datasets are available for bulk download without legal encumbrance.
- In order to increase and improve use of the city’s open data, the [individual or group] will actively encourage agency and public participation through providing regular opportunities for feedback and collaboration.
Section 5: Central Online Location for Published Data
- The city will create and maintain a publicly available location on the city's website or in another suitable online location where the city’s published data will be available for download.
- Published datasets shall be placed into the public domain. Dedicating datasets to the public domain means that there are no restrictions or requirements placed on use of these datasets.
- Each published dataset should be associated with contact information for the appropriate manager of that dataset as well as with a file layout or data dictionary that provides information about field labels and values.
Section 6: Open Data
- Within one year of the effective date of this directive, and thereafter no later than December 31 of each year, the Chief Data Officer shall publish an annual Open Data Report. The report shall include an assessment of progress towards achievement of the goals of the city’s Open Data Program, an assessment of how the city’s open data work has furthered or will further the city’s programmatic priorities, and a description and publication timeline for datasets envisioned to be published by the city in the following year.
- During the review and reporting period, the Chief Data Officer should also make suggestions for improving the city’s open data management processes in order to ensure that the city continues to move towards the achievement of the policy’s goals.
Tom Cappetta
Proactive to me is having the Mayor & Corp Counsel clearly define what is NOT allowed prior to the start of the initiative.
Tom Cappetta
Also note - high-quality & transparency ==> simple github location to encourage collaboration & contributions from the broader community - e.g http://ny.github.io/open-data-handbook/
Tom Cappetta
It will have to be a requirement to have I clearly defined "operational" process which all departments MUST adapt to publish their data. I believe this process needs to be defined on Day 1 & adapt operationally to constantly adapt. The ability to measure total-time to deliver a "publishable dataset" milestone will be key to operational efficiency & there is no indicator that process even has a framework
Tom Cappetta
correction -- "defined on Day 1 & adjusted operationally (e.g. and through documentation) to constantly adapt"
Tom Cappetta
redundant - protect & sensitive are ultimately the same
Tom Cappetta
I would prefer to define protected information as something which raises privacy, confidentiality or security concerns.
Clinton Blackburn
Can you be more specific? What constitutes a privacy, confidentiality, or security concern?
Frank Cetera
As Vice-Chair and Westside Board Delegate for Tomorrow's Neighborhoods Today, I personally whole-heatedly support this, and hope that the TNT organization and sectors can be effective in helping the public access the data.
Samantha Linnett
This is really important, but I would be interested to see practically how these can be measured against departmental goals and targets, etc.
Tom Cappetta
+2 for transparent department objectives, goals, metrics, & SLA's
Tom Cappetta
Adding a note about defining automation standards to support effectiveness...
Samantha Linnett
YES
Tom Cappetta
I believe this is a governance bulletpoint related to data owners & a supporting dictionary
Samantha Linnett
Should this be CDO? Or does it refer to departments/agencies/public spoken about above?
Samantha Linnett
Processes for this will be key.
Barbara Bouton
Fantastic, forward thinking idea. This data was collected at public expense and should be available as freely usable public domain data. Jumping through an information gatekeeper like FOIA was never a good idea.
Paul Crickard
Data may not need to be published to a repository. Link to existing location. See Play it where it lies (1, 1.5) http://chriswhong.com/open-data/thoughts-on-open-data-part-1/ My experience has been when files require exporting from a Dept then imported to Open Data (manual process), data gets old because employees stop exporting or corrupted because new employees don't know process. Location of data/database is not important if the link to it or an API is available on central location.
Scott Davis
Very excited to hear this is happening! To get the most out of this open data initiative, it would be nice to see, 1) Data provided in its most raw form without aggregation (allows for more flexibility in analysis), and 2) A list of issues/challenges/topics the City is trying to address. Equipping the public with these two things could lead to highly creative solutions.
Peter Smith
An implementation of this as a RESTful API that returns JSON would attract the most software developers.
Peter Smith
Given most modern web development relies on APIs and given that most APIs return JSON, a dataset in JSON would receive more interactions than an XML dataset.
Peter Smith
Clinton Blackburn
This is the definition section. Regardless, policy should not define data formats. The policy should be broad enough that the data formats can evolve as technology evolves.
Sam Edelstein
The data the city releases will be available in JSON. In this case, XML was just used as an example.
Adelaide Rosa
This will be incredibly useful for effective policy of all sorts! I can only hope that someday Onondaga County will have a similar initiative, with the capacity for interface and data synthesis.
Showing 31 to 45 of 50 entries