Baton Rouge Open Data Policy
Shared for feedback by City of Baton Rouge
Through its engagement with What Works Cities, the City of Baton Rouge and Parish of East Baton Rouge has created Baton Rouge's first Open Data Policy.
This policy review is one of a number of efforts designed to catalyze Baton Rouge's digital evolution, to reinvigorate the City-Parish’s open data program and Open Data BR portal, and align City-Parish data-related policies, practices and activities with national best practices.
The review of this open data policy will allow a variety of constituents and community stakeholders to provide input and share their insights into how and how well the City-Parish’s draft open data policy will facilitate public access to City-Parish public data assets, and into how City-Parish public data assets could and should be used.
Baton Rouge Open Data Policy
RESOLUTION
ADOPTING AN OPEN DATA POLICY FOR THE CITY OF BATON ROUGE AND PARISH OF EAST BATON ROUGE; EXPRESSING THE SUPPORT OF THE METROPOLITAN COUNCIL FOR THE IMPLEMENTATION OF THE POLICY BY THE MAYOR-PRESIDENT.
WHEREAS, the Metropolitan Council of the City of Baton Rouge and Parish of East Baton Rouge hereby supports the use of open data and systems, as well as citizen access to public data, and thus seeks to adopt and implement a formal open data policy; and
WHEREAS, the Metropolitan Council supports the Mayor-President in the implementation of related administrative processes or workflows, thereby ensuring compliance across all departments over which the Metropolitan Council or Mayor-President have legislative, executive, and policy authority; and
WHEREAS, there remain many datasets collected by the City of Baton Rouge and Parish of East Baton Rouge (hereafter, “the City-Parish”) that are stored in ways which impede the ability of City-Parish leadership and key public stakeholders to aggregate, analyze and synthesize it to better allocate public resources; and
WHEREAS, access to public information promotes a higher level of civic engagement and allows citizens to provide valuable feedback to government officials regarding local issues; and
WHEREAS, every citizen has the right to prompt, efficient service from the government; and
WHEREAS, the City-Parish’s existing open data program provides public and interdepartmental access to key datasets that improves the provision of services, increases transparency and access to public information, and enhances coordination and efficiencies among departments, partner organizations and citizens; and
WHEREAS, one goal of an open data policy is to proactively provide information currently sought through public records requests, thereby saving the City-Parish time and money; and
WHEREAS, the City-Parish has made significant strides in providing such information through its open data portal, thereby recognizing the benefit of adopting a formal open data policy defining an “open by default” mandate for public information; and
WHEREAS, in commitment to the spirit of open government, the City-Parish will consider public information to be open by default and will proactively publish data and data containing information, consistent with relevant public records law and not deemed to be protected or sensitive information; and
WHEREAS, information technologies, including web-based and other Internet applications and services, are an essential means for open government, and good government generally; and
WHEREAS, by publishing structured, standardized data in machine readable formats the City-Parish seeks to encourage the local software community to develop software applications and tools to collect, organize, and share public record data in new and innovative ways; and
WHEREAS, the protection of privacy, confidentiality and security must continue to be maintained as a paramount priority while also advancing the City-Parish’s transparency and accountability efforts through open data.
NOW, THEREFORE, BE IT RESOLVED by the Metropolitan Council of the City of Baton Rouge and Parish of East Baton Rouge that:
Section 1.
The Metropolitan Council adopts an open data policy as follows:
“Open Data Program
Part 1. Policy.
The Open Data Program for the City of Baton Rouge and Parish of East Baton Rouge applies to all City-Parish departments and agencies. The program requires that each department or agency comply with the following:
-
Proactively release all publishable City-Parish data, making it freely available in appropriately varied and useful open formats, using an open license 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-Parish data;
-
Measure the effectiveness of datasets made available through the Open Data Program by connecting open data efforts to the City-Parish’s programmatic priorities;
-
Minimize limitations on the disclosure of public information while appropriately safeguarding protected and sensitive information;
-
Support innovative uses of the City-Parish’s publishable data by agencies, the public, and other partners;
-
Encourage electronic methods of data collection to avoid inefficiencies of paper-based filing systems and make real-time disclosures possible; and
-
Include specifications in future Requests for Proposals (RFPs) and comparable procurements to encourage technology solutions with an open source licensing model and/or the capabilities to store and expose public data using industry standard and open protocols.
-
Develop contract provisions that promote the City-Parish’s open data policies in technology-related procurements, including, where appropriate, requirements to post data on the City-Parish open data portal or to make data available through other means.
Part 2: Definitions
A. “Data” means statistical, factual, quantitative, or qualitative information that is maintained or created by or on behalf of a City-Parish agency. This definition is inclusive of software source code developed or maintained by or on behalf of the City-Parish..
B. “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 [or a requirement of registration]. “Legal encumbrance” includes federal copyright protections and other, non-statutory legal limitations on how or under what conditions a dataset may be used. This definition is also inclusive of any software source code made available online (“open source software”).
C. “Open format” means any widely accepted, nonproprietary, platform-independent, machine-readable data format, which permits automated processing of such data and facilitates analysis and search capabilities..
D. “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..
E. “Protected information” means any dataset or portion thereof to which an agency may deny access pursuant to the Louisiana Public Records Act (La. R.S. 44:1 et seq.) or any other law or rule or regulation..
F. “Sensitive information” means any data which, if published by the City-Parish 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..
G. “Publishable data” means data which is not protected or sensitive and which has been prepared for release to the public..
Part 3: Governance
A. The implementation of the Open Data Program will be overseen by the Director of Information Services on behalf of the Mayor-President, who will work with the City-Parish’s departments and agencies to::
-
Identify and publish appropriate contact information for a lead open data coordinator for each agency, who will be responsible for managing that agency’s participation in the Open Data Program;
-
Oversee the ongoing management of a comprehensive inventory of datasets held by each City-Parish agency, which is published to the central open data location and is regularly updated;
-
Continually refine 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 additional datasets which takes into account new and existing signals of interest from the public (such as the frequency of public records requests), the City-Parish's programmatic priorities, existing opportunities for data use in the public interest, and cost;
-
Proactively consult with members of the public, agency staff, journalists, researchers, and other stakeholders to identify the datasets which will have the greatest benefit to City-Parish 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 including unique, standardized identifiers across datasets, where possible;
-
Develop and oversee a routinely updated, public timeline for new dataset publication;
-
Make recommendations for historical document inclusion and define a schedule for approved historical document publication;
-
Ensure that published datasets are available for bulk download and/or available via public application programming interfaces (APIs) without legal encumbrance; and
-
Establish a Data Governance Committee, consisting of lead open data coordinators from each relevant agency, to meet at least quarterly to encourage ongoing agency and public participation through providing regular opportunities for feedback and collaboration.
Part 4: Central Online Location for Published Data
a. The City-Parish will maintain a publicly available location on the City-Parish's website or in another suitable online location where the City-Parish’s published data will be available for download..
b. 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..
c. Each published dataset should be associated with contact information for the appropriate lead open data coordinator of that dataset as well as with a file layout or data dictionary that provides information about field labels, values, and data source or creation information..
d. City-Parish departments will specify a recommended data citation form available for viewing on the central online location for published City-Parish data to encourage responsible reuse of City-Parish data..
Part 5: Open Data Report and Review
a. Within one year of the effective date of this Resolution, and thereafter no later than January 31st of each year, the Director of Information Services shall publish an annual Open Data Report. The report shall include an assessment of progress toward achievement of the goals of the City-Parish’s Open Data Program, an assessment of how the City-Parish’s open data work has furthered or will further the City-Parish’s programmatic priorities, and a description and publication timeline for datasets envisioned to be published by the City-Parish in the following year..
b. During the review and reporting period, the Director of Information Services should also make suggestions for improving the City-Parish’s open data management processes in order to ensure that the City-Parish continues to move towards the achievement of the policy’s goals.””
Section 2.
The requirements of this Resolution shall apply to any City-Parish department, office, administrative unit, commission, board, advisory committee, or other division of City-Parish government (“agency”).
Section 3.
This policy shall become effective ____ months/days following adoption by the Metropolitan Council.
Section 4.
The City-Parish shall collaborate with internal and external stakeholders as necessary to achieve all components of this Open Data Program and gather public input into its ongoing development and management, including those in the private sector, nonprofit organizations, academic institutions, other government agencies, and public citizens.
Rhett Clement
All denials of access will be cataloged and available as part of the publicly accessible Open Data system. The record of denial will include the individuals that authorized the denial, the individuals that reviewed and approved that authorization and the legal basis on which said denial was made.
erik r
The denial must be timely so that both the recipient of the denial and the public can review it.
Rhett Clement
Departmental policies will be updated to ensure that modification of existing systems or installation of new software systems shall be reported to the Information Services department with a statement that examines the impact of said change on the department's inventory.
Rhett Clement
Prepared how? Do we need assurances that preparation will not be used to obstruct, obfuscate, or otherwise limit the capacity for governance including public accountability?
Rhett Clement
containing data that may be filtered, sorted, grouped, or otherwise structured or formatted in a specific...
Rhett Clement
Platform-agnostic seems like a more appropriate, safer choice
isral duke
Platform and editor agnostic is safe.
Rhett Clement
Has this clause been considered in light of the terms of use (contract) already in effect with Open Data BR https://data.brla.gov/terms-of-service
Rhett Clement
Remove (see previous open source comments)
Rhett Clement
I feel like open source software is being conflated with open data. What case has been made to support the benefit of this open source model for the City? I believe the City's funds are better spent by focusing on the data. Open data in support of bureaucratic transparency has a clear value to the taxpayer, I do not understand how the same could be said about open source software.
Alex Clavelle
With open source code, citizens could theoretically contribute after signing a contributor license agreement: https://en.wikipedia.org/wiki/Contributor_License_Agreement I see these for open source projects frequently online.
Open source code also allows for citizens to reuse components like api clients developed by the state to interact with state apis.
erik r
Does this include audio, video, and date yet to be unlocked or not allowed e0acces to?
Rhett Clement
@erik r I was only considering code in this comment.
Rhett Clement
Again, I would view the City as the custodian of this data, not the vendor. The vendor should develop systems that are conducive to the City's processes for aggregating and publishing this data.
Rhett Clement
It's not clear how source code licensing models are relevant to an open data initiative. However, the ability to expose public data using industry standard open protocols is relevant.
Rhett Clement
I would consider developing the expertise to store and expose public data within the City-Parish government. It's important that a vendor deliver a solution that provides documentation of the system's data: where is it, how is it stored. The solution should conducive to exporting to or synchronizing with a public data store. But I would not have the vendors responsible for publishing. If they were the implementations run a high risk of inconsistencies, pose ongoing operational challenges and drive up the cost of that solution. On the other hand, if the city develops the expertise to integrate and publish data from their systems (something that seems necessary already) then the vendor can more easily meet the requirements of the City. Proposals should carry language that ensure that the process for modifying these systems over time includes a provision to maintain current data documentation.
Independent of vendors/RFP's etc. the City should be prepared to deal with scenarios where modification to a system requires a significant change to an open data set. Many changes will just require additional documentation, but some changes will impact (break) systems that depend on the City's open data. There are different strategies or techniques used to manage the impact of public API changes like side-by-side versions, deprecation and obsolescence.
erik r
RFPs should be included on the date of issuance, any questions or emails/texts/letters/docs from persons who give reference to te RFP, and prior and after approval of the accepted contract, cooperative agreement (CE), invoice, and memorandum of understanding (MOUs)
Curtis Heroman
We may want to include this in the definitions, and potentially add technical specifications for API formats
Curtis Heroman
I would recommend establishing a public-private working group that focused on: 1) system and process solutions for information collection, aggregation, validation, and dissemination and 2) creating partnerships for additional datasets that go beyond the resources available to the city-parish government
Curtis Heroman
This is a great idea. All future initiatives should be scoped with open protocol requirements from the start as a cost savings measure.
Curtis Heroman
Not sure if the City-Parish has a data privacy policy, but this would be a good place to reference it. If we don't have one, should strongly consider implementing one for legal safety.
Curtis Heroman
Does "all released City-Parish data" mean released through the Open Data portal or released in general? If you're talking about just maintaining an archive of all data already posted on Open Data BR, that's easy. If you're talking about digitizing all archived records, that's an incredibly valuable, but difficult exercise that should follow the same prioritization process from Part 3, #4.
erik r
The archival portion must be done timely--say, every 30 or 60 days--and maintain an effective and efficient retrieval, searchable, and accessible process
Showing 16 to 30 of 36 entries