opendatainitiative / opendatalegislation

To make good policy permanent, the policy must be made into a law

Project Overview

Many open data implementations are the result of good management and their policies. But any good policy can be modified by a change in management. To make good policy permanent, the policy must be made into a law. The law must cover just enough detail to establish a framework that the open data implementation can be built upon. We highlight and review open data legislation.

Published Legislation Results

https://opendatainitiative.github.io/legislation

Project Details

• Project Overview
• Project Issues to be Completed

Contributing

1. Fork it (https://github.com/opendatainitiative/opendatalegislation/fork)
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create a new Pull Request

License

The underlying Jekyll source code that used to format and display content is licensed under the MIT license, the non-code text content displayed by Jekyll is licensed under the Creative Commons Attribution 4.0 license, and code created by the project contributors is licensed under the Apache License 2.0.

opendatalegislation's Issues

Convert yml review section to a post

The review section will contain a link to the post

Dependent on to #22

Score United States legislation

Add license file

Add a title to page https://opendatainitiative.github.io/legislation-review/2017-01-25-ohio-legislation-review/

Utilize Sunlight Foundation's open data policy tools

Score California legislation

Remove new page when selecting scoring, detailed, or summary

correct README formatting error

https://github.com/opendatainitiative/opendatalegislation/blob/master/README.md

1. add new line between project details

Score Hawaii legislation

correct comments formatting error https://opendatainitiative.github.io/detailed-legislation

the comments section width is too small

Identify, score, and review existing laws and policies

Texas rates their cities on transparency

fold this and some background into the incentives

detailed legislation source field returns %7B%20name.source%20%7D%7D

ohio and california legislation reviews use 2017 filename instead of 2018

add legislation detail row to the top of the legislation review

add sorting to indexes

Score New Hampshire legislation

CSS:html hover is broken on touchscreen devices, replace with JS

https://codepen.io/mickeykay/pen/wiLno

Score Utah legislation

add CA bill 2015-2016 SB-1029 to be scored

https://leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id=201520160SB1029

Scored page has the wrong title

Score Florida open data legislation

Correct CA legislation review first line to not public

fix spelling errors in california legislation review

Calfornia
score’.

convert csv data to yml to encourage collaboration

add a title to https://opendatainitiative.github.io/legislation-review/2017-02-28-california-legislation-review/

Add README instructions to ODI projects on contributing

Add on click government organization field to the open data portal source URL

Score Maryland legislation

change data file to .yaml

Crash caused US and California legislation scores to be switched

It looks like the US legislation review may have been lost as well.

Government finance officer association give gofa award for good work

fold this into the incentives

New legislation as a last resort

We pursue a strategy of not enacting entirely new statutes if existing state laws pertaining to public records and utilization exist. Amend and improve if possible.

XBRL can be part of legislation standard

XBRL can be part of legislation standard for DataOhio board standards implementation. It should be neutral to include OKI frictionless financial data package standard.

Intersections between the federal, state, and city open data policies, laws, and implementation

We need to dig into current examples of open data operations that have been successful in this type of coordination. How do we reproduce their success? Follow up in the next Open Data Legislation project meeting. I will invite Frank Kohstall to deep dive on this.

include max score in indexes

there is no explanation what the score x out of y

Second pair of eyes on the Florida legislation scoring and review

Resource US Federal link to DATA act review is broken

Score ohio legislation

partially scored now. include hb40

Ohio review legislation score and provide feedback

Add GIS maps to legislation, transparency indexes

1. Rely on https://github.com/ayastreb/jekyll-maps/blob/master/README.md to start
2. other references http://jgardiner.co.uk/blog/a-basic-leaflet-map-in-jekyll and https://tinyheero.github.io/2015/12/06/rmd-to-jekyll-protect-eqn.html

Referencing core data requirement/characteristics provisions in key federal legislation

Christian suggested referencing core data requirement/characteristics provisions in key federal legislation (these items are written to not be too technically prescriptive). See the examples of Foundations for Evidence-Based Policymaking Act (See Title II, OPEN Government Data Act) (HR 4174, 115th) and Grant Reporting Efficiency and Agreements Transparency (GREAT) Act (HR 4887, 115th)

Create a workshop model for Government Financial Report hackathon

document workshops in the repo for states and cities to copy. Does Sunlight Foundation have something we can copy/use?

Establish the DataOhio board for open data leadership momentum

1. GA132-HB3 and HB40 are close to model legislation. Getting this group together will highlight getting the legislation passed and what amendments are needed.
2. The customer service and operations experience of the 2018 Ohio Treasury Office needs to be carried over to the next administration employees. This board can help carry the experience and knowledge over.

Making Ohio GA132-HR3 lines 86-88 more clear

With respect to Ohio HB3, Section 117.432(B) states the following:

"Within two years after the effective date of this section, the auditor of state shall establish, by rule adopted under Chapter 119. of the Revised Code, appropriate uniform accounting procedures and charts of accounts that may be used by all public offices. Public offices that maintain their financial
records in accordance with the rules established by the auditor of state under this section shall be declared by the auditor of state to have earned a "DataOhio Transparency Award—Uniformity of Accounting."

This provision could be readily modified to bring in machine readable standards and thus mandate XBRL or Frictionless Data formatted CAFRs. To conform with what Christian is doing on the federal level, I suggest the following revision (additions in bold):

"Within two years after the effective date of this section, the auditor of state shall establish, by rule adopted under Chapter 119. of the Revised Code, appropriate uniform accounting procedures and charts of accounts that may be used by all public offices. The chart of accounts shall be consistent with standards promulgated by the Governmental Accounting Standards Board. The auditor will also establish an electronic reporting standard for public offices that will render their accounting information fully searchable and machine readable, that will be non-proprietary and that will incorporate standards developed and maintained by voluntary consensus standards bodies. Public offices that maintain their financial records in accordance with the rules established by the auditor of state under this section shall be declared by the auditor of state to have earned a "DataOhio Transparency Award—Uniformity of Accounting."

Do you or others on this chain have thoughts about the proposed additions? If this is agreeable to everyone, how might this change be proposed to Representative Duffey?