Skip to content

Latest commit

 

History

History
46 lines (40 loc) · 3.67 KB

scoring.md

File metadata and controls

46 lines (40 loc) · 3.67 KB
Raw
layout permalink title
default
/scoring
Scoring

{{ page.title }}

Transparency

Alpha (published July 2017)

We reviewed a subset of the states.

Calcuation: 0.80[100..0]+1.0[10..0]+1.0[10..0]

  1. Weight 80% [100..0] 2016 PIRG score
  2. Weight 100% [10 ..0] Accessibility: How easy was access to the data in a report format?
  3. Weight 100% [10 ..0] Downloadability: Was the data easily downloadable?
  4. Comments

Beta (To be published Spring 2017)

There may be some overlap with the metrics and 2016 PIRG

Calcuation: 0.80[10..0]+0.80[10..0]+0.80[10..0]+0.80[10..0]+0.80[10..0]+0.80[10..0]+0.80[10..0]+0.80[10..0]+0.80[10..0]+0.28[100..0]

  1. Weight 80% [10 ..0] Easy to use website: Is it intuitive or difficult to figure out?
  2. Weight 80% [10 ..0] Single pane of glass [10 ..0]: One panel or location to find all finance information
  3. Weight 80% [10 ..0] Common, easy to understand data export formatting: comma delimited (CSV) and text delimited (TXT) formats
  4. Weight 80% [10 ..0] Easy to use functionality for entire checkbook datasets: Is the data all similar in presentation and delivery?
  5. Weight 80% [10 ..0] Data schemes and techniques provided with datasets:. CSV column headers explain the data provided.
  6. Weight 80% [10 ..0] Published policy
  7. Weight 80% [10 ..0] Consistent publishing
  8. Weight 80% [10 ..0] pension liabilities (most portals exclude this critical data)
  9. Weight 80% [10 ..0] salary with explanation and comparison to similar roles in the same region private sector
  10. Weight 28% [100 ..0] 2016 PIRG features, Page 32, 100 points from 12 reviewed areas with checkbook features accounting for 40% of the score PIRG 2016 report

Legislation

Alpha (published February 2017)

Related legislation is reviewed as a whole and combines the scoring.

  1. Weight 100% [10 ..0] Public Default: Categories of records are public records by default
  2. Weight 100% [10 ..0] Technology standards: Recommend technology standards. These will be minimum requirements so extra work is not generated. Ability to export records in TXT format with recommended metadata headers. Open data system able to support exporting data through API using shared key. Commercial vendor product and open source project options with some high level recommendation of staffing requirements.
  3. Weight 100% [10 ..0] Accounting standards: Recommend accounting standards. Utilizing the state accounting system is recommended. Otherwise there must be a minimum set of common terms and fields that the state and municipalities can agree on. These accounting standards set the baseline for reporting and publishing.
  4. Weight 100% [10 ..0] Metadata standards: Recommend metadata standards. The metadata at a minimum define the field headers for the accounting standard fields. Collaboration and participation with open government open data organizations such as data.gov (Federal GSA), Open Data Initiative, What Works Cities (Sunlight Foundation), and Data Coalition. Encourage representatives to hold board seats, participate in strategy discussions, and help to keep on top of evolving new options.
  5. Weight 100% [10 ..0] Annual Report: Make annual recommendations with updates
  6. Weight 100% [10 ..0] Bi-annual meetings: Bi-annual public meetings with published agendas and meeting results. Following Robert's rules.
  7. Weight 100% [10 ..0] Incentives: Incentive programs, either grant annual funds for annual participation with state open data system or create a certification system that allows publishing for annual compliance.
  8. Weight 100% [10 ..0] Passed House
  9. Weight 100% [10 ..0] Passed Senate
  10. Weight 100% [10 ..0] Signed into law