Open Data for an Open Society
September 2016
Pia Waugh
@piawaugh | [email protected]
Help the public sector help you
- Powerful citizens, responsible geeks
- Dsitributed power
- Paradign shifts and struggles
What data?
What data?
●
●
●
●
●
●
●
●
●
●
Specialist data
●
Administrative data
●
Reports
●
Tables
●
Maps
●
Analysis
Key indicators
●
Official Information Act requests
Lists (places, contracts, services)
Services analytics
Regular requests
Compliance information
Public reporting data
Budget
Policy & programme
monitoring
...
Questions
●
●
●
●
●
●
What is the government data vision and strategy? A holistic
approach would yield greater benefits to everyone.
What barriers exist for agencies to better use, manage,
share and publish data?
What is needed by data publishers and users to make data
sharing and publishing part of BAU?
How can we bring the different NZ data agendas together?
What are the benefits of open data? Is it beneficial to
agencies individually and better government as a whole?
What role should data.govt.nz play?
Previous feedback, landscape/gaps, dev empathy
Public sector open data motivators
●
●
●
●
●
●
●
●
Efficiencies from proactively publishing common requests
Cheaper and more modular services delivery
Reduced regulatory burden through machine readable
data supporting compliance and automated reporting
Better policy outcomes by leveraging cross-agency data
More consistency & less duplication across government
Improved opportunities to leverage innovation and
collaboration (citizens, industry, other depts)
Opportunities to improve data quality through
verifiable public contributions
Access to data from other agencies
NZ Data Landscape
Reuse projects
No
catalogue
for
sensitive
data
Catalogs
Publishing
Sharing &
Integration
Data
Figure
NZ
Catalyst
projects
Stats
IDI
Aggregate
SIU
Statistics
(statistical
data)
Data.govt.nz
(ostensibly
AoG
catalogue)
Specialist
catalogues
LINZ
ODP
advocacy
GovHack
Geopor
tal
Council
catalog
ues
AoG Publishing?
Internal
Analytics
Sensitive
Agency data
(internal)
LINZ
(spatial and
spatially
enabled
data)
Agency
LDS
Agency
LDS
AoG
Services
Analytics
Agency
LDS
Non-sensitive
Agency data
(internal,
on websites)
Council
data
How Do Agencies Publish?
●
●
●
●
●
Some agencies have specialised data expertise and
publishing capabilities.
Some are developing
capacity to publish.
Most, if they publish
data at all, publish
data un-usefully.
AoG data platform
required for this barrier. DIA
St
Skills, guidance and
ats
LI
encouragement help.
?
NZ
Customer Pain Points
●
●
Most Agencies have little motivation, resources or expertise to
publish data. In most cases do not have a broader data strategy.
If agencies consumed more data (internally & across govt) it
would naturally lead to more data sharing and public availability.
Data users find it hard to discover data and usually if it is
findable, it isn't usable or machine readable. Often user logins
are required. This creates a lack of experimentation of and
confidence in government data resulting in a lack of reuse and
lack of outcomes realised.
Every individual barrier to using or publishing data dramatically
reduces activity and the possibility of benefits realisation!
●
User Needs for data.govt.nz
Data Users
(Public, Business,
Journalists, Media,
Agencies)
Data Publishers
(Agencies)
Discovery
Usage
Rights
Usable
Data
(MR, APIs)
Support,
Requests
Internal
Data Strategy
Easy
Management
Of Catalog
Easy Data
Publishing
Access to
Expertise, Docs
& Training
Access to
Data from
Across Govt
Value from
Open Data
Analytics &
Reporting
Case Studies
& Business
Case for OD
We need to educate on benefits and reduce barriers to
using and publishing data so people can get on with it.
Parts of a data strategy
Data reuse
Strategy
Implementation
Business
Reuse
(Products,
services)
Govt
Investment
(Catalyst
projects)
Analysis,
Presentation
(eg, datavis,
FigureNZ)
Governance,
leadership
Advocacy
Infrastructure
(Specialist &
General)
Skills,
Resources,
Training
Better
Govt Policy,
Decisions,
Efficiencies
Public
Innovation
(eg,
Govhack)
Incentives,
Performance
Data
Policy
Full
Discovery
Standards
Critical aspects for data.gov.au
(for comparison)
●
●
●
●
●
●
●
Harvesting metadata from existing catalogues with
common metadata mapping
Free data hosting (with automatic APIs) to serve the
majority of agencies that can't easily publish data
Education of the business case for agencies
A committed central technical team – agency support,
platform functional improvements, docs
A distributed publishing model where agencies manage
their own data linked or hosted on data.gov.au.
Constant public success and communication
Modular, iterated technical design, scalable on the cloud
Future data.govt.nz options
Simple
catalogue only
Currently live
Beta
Future
Options
Consistent
catalogue
Tabular
data hosting
Automated
APIs
Basic Stats
Basic Charts
& Mapping
Consistent
catalogue
Tabular
data hosting
Automated
APIs
Analytics &
Reporting
Basic Charts
& Mapping
Metadata
Mapping
Data
Services
Distributed
Publishing
Quality
Frameworks
Collaborative
Strategy
AoG Data
Vision
Data Models
Sharing
Part of
Services
Delivery
Additional
Data Hosting
As Required
High Volume
Charging
Framework
Artifacts
Sharing
Hub
Guidance
And Shared
Resources
Scalable
Cloud
AoG Data
Practitioner
Community
Of Practice
Cross
Agency
Hackfests
Practitioner
Governance
Group
Exemplar
Agency
Projects
Business
Benefits
Case Studies
Sustainable
Reuse
Projects
Parallel Initiatives Needed To Drive Change
Data reuse projects to demonstrate value and drive appetite
Eg - Catalyst projects, FigureNZ
Development of data driven culture across govt
Eg - growing demand from policy teams, investment, services delivery
AoG holistic data publishing, sharing, skills and capability improvements
Eg – data.govt.nz, LINZ, Statistics
Specialist data programs and integration initiatives for specialised outcomes
Eg – SIU, DFP, LINZ, Statistics, IDI