Prioritizing Open Data Sets


Published on

Prioritizing Open Data Sets by David Eaves

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Prioritizing Open Data Sets

  1. 1. Prioritizing Open Data Sets<br />3 simple rules<br />
  2. 2. Rule 1: Look Backward, Look Sideways<br />Look Backwards:<br />Most governments know what data and information has been heavily requested by the public in the past<br />Past requests reveal both latent demand and potential community<br />This is a good place to start<br />Look Sideways:<br />Look at requests other governments make public, there are trends<br />Examples of data sets that regularly top the list: procurement, budget, crime, transit and transportation data<br />
  3. 3. Rule 2: Target Policy Objectives<br />Release data that will advance specific policy goals<br />Health<br />Accountability/anti-corruption<br />Education<br />Transport<br />Environment<br />
  4. 4. No one visits your website<br />This is Vancouver Coastal Health’s Restaurant Inspection site.<br />No one visits it.<br />
  5. 5. Repeat, no one visits your website<br />The only time anyone searches for restaurant inspection data...<br /> after they’ve been food poisoned<br />
  6. 6. e.g. Health Objectives<br />When citizens see restaurant inspection data<br />Consumer behavior drives compliance:<br />Well rated restaurants experience more business<br />Badly rated restaurants experience less business<br />Consumer behavior and compliance create savings:<br />In Los Angeles County, Emergency Room Visits due to food born related illnesses declined by 16% in year one, 6% in year two, 3% in year three<br />Focused transparency can improve health outcomes and lower costs<br />
  7. 7. Put the data where the citizen is<br />
  8. 8. Rule 2: This is your goal<br />
  9. 9. Rule 3: Partner when you must, Follow when you can<br />Open data in structures that are common across multiple jurisdictions is much, much more powerful<br />The power of a common structure: the General Transit Feed Specification allows access to transit schedules in 160+ cities in dozens of languages in Google Maps<br />Copy others structure whenever you can<br />
  10. 10. Rule 3: Partner when you must, Follow when you can<br />Rule 3a:<br />Help foster cross jurisdictional standards by copying other people’s data structures<br />Rule 3b:<br />When there is no standard, find private sector or community actors who want to consume your data, and get them to help you create the data structure<br />Tell the world about your structure!<br />
  11. 11. Partnering<br />Creating a new standard requires scale, access to a large user base, and an ability to compromise. E.g. For Transit, Portland engaged Google<br />4 Do’s and Don’ts<br />DON’T start by forming a standards committee, we don’t have 10 years to spend coming to agreement<br />DO find a partner with scale and market penetration<br />DON’T promise exclusivity to that partner<br />DO create a governance model after the standard succeeds<br />
  12. 12.
  13. 13.
  14. 14.
  15. 15.
  16. 16.
  17. 17.
  18. 18. David Eaves<br /><br /><br />@daeaves<br />