17. Why Open-Source Matters...
• No vendor lock-In / choice of consultants / ability to build inhouse capacity
• Collaborate w/ our peers (White House)
• Security transparency (US DoD is a major consumer for this
reason)
• Open-Source platforms often pay more heed to open formats
and standards (e.g.: DCAT, RDFa, OData, JSON vs Shapefiles, PDF,
etc.)
• Innovation: healthy open-source projects can aggregate more
engineering effort than proprietary alternatives, propagate great
new extensions faster
• Freedom of Hosting Options: consume as a cloud-hosted
service today, change our mind and host in-house tomorrow, etc.
18. But
Data.gov.uk,
Data.gov,
HealthData.gov,
OpenGovPlaKorm,
etc.
all
added
Drupal
to
CKAN
http://flickr.com/photos/rocketqueen/1573565705/
20. With
DKAN
Distro,
Drupal
Itself
Now
Also
Becoming
a
Public
Sector
Data
Management
System
(“DMS”)
21. Why DKAN Instead of Drupal+CKAN?
• Manage content, data, permissions through same platform
• Single software stack to maintain
• Single site to design & theme
• Easy to extend with social features
• Transparent, well-governed upgrade path of Drupal
• Extensive Drupal ecosystem of civil service talent,
consultants, hosting, support
22. Why Drupal?
•
MATURE:
>1
million
sites
(2%
of
all
sites),
3,718
Code
commits/wk,
6,388
issue
comments/wk
•
IN-‐HOUSE
SKILLS:
24%
of
.gov
sites
•
EXTENSIBLE:
18,489
Modules,
1,512
Themes,
21,009
Contributors
•
FISMA-‐Cer&fied
Cloud
Hos&ng
Op&ons
•
INTEGRATES
easily
w/
public
websites
lots
of
de
facto
data
is
already
published
as
content
34. Open Data is Just “Sharing Your Files”
• Datasets
are
collec&ons
of
resources,
with
some
descrip&ve
metadata
• Resources
are
just
files.
They
can
be
any
kind
of
file,
but
ohen
they
are
CSV
files,
spreadsheets
or
some
other
kind
of
tabular
data
file.
• Organiza&ons
create
datasets
and
upload
resources.
• Data
consumers
can
browse
datasets
and
some&mes
see
visualiza0ons
of
resources.
34
35. DKAN
•
Fully functional data portal housing datasets, Solr search, accessible
via JSON and RDF; csv or xml files uploaded through Drupal, stored in
*SQL, visualized through Recline.js
• Seeks to replicate CKAN 2.0 functionality, design, standards, & API
• Reuses CKAN components wherever possible (e.g.: Recline.js)
• Built with support and input from the Open Knowledge Foundation
• Fully open project, with code on Drupal.org/project/DKAN
49. Ongoing Development
•
Adding
feedback
on
datasets,
other
social
features
•
Support
for
addi&onal
file
types
•
Adding
DKAN_DataSet
&
DKAN_DataStore
modules
to
other
Distros
like
OpenCivic
•Offering
enterprise
support
&
hosted
OpenSaaS
DKAN
50. “NuData DKAN” OpenSaaS Offering
•
NuData
=
our
DKAN
as
a
turnkey
hosted
24/7
supported
sohware-‐as-‐a-‐service
•
Governments
like
SaaS
like
Socrata
because
it’s
quick,
affordable,
and
no
technology
burden
on
exis&ng
staff
•
Governments
like
open-‐source
(e.g.:
CKAN)
because
they’re
in
control-‐-‐
no
vendor
lock-‐in,
ability
to
customize,
innovate
•
OpenSaaS
=
the
best
of
both
worlds;
SaaS
but
truly
open-‐-‐
you
can
take
your
app
and
your
data
with
you
with
minimal
switching
cost
•
Drupal
is
excep&onally
well
posi&oned
to
enable
OpenSaaS
businesses
51. Drupal Open Data Policy Compliance Recipes
add /data.html &
/data.json pages
to existing Drupal
site with new Open
Data Module?
(sandbox project)
add data management
&
publishing features
to a Drupal site with
DKAN Data Set &
DKAN Data Store
Modules
deploy new Open
Data Catalog / Portal
with the DKAN
Distribution, on your
own, or as SaaS