OGD - Jeff Walpole

Developing /open Agency Sites Using Open Source Drupal for the Open Government Directive Prepared & Presented by Jeff Walpole, CEO

Why Use Open Source for OGD? About Phase2 Technology
Open Data + Open Source ≠ Open Government, but…
Open Data + Open Source ≠ Open Government, but…
Open Data + Open Source = a great starting point
Consider:
Cost
Openess
Time to Deliver
Community

Tech Requirements of OGD About Phase2 Technology
Every government agency will be required to create a presence at www.agency.gov/open that includes many things, but the big things that matter now are:
Use of “modern technology” / best practices
Open data sets (at least 3 meaningful data sets to start)
Published Open Government Plan
FOIA Plan and Information
Mechanisms for public feedback and input
Downloadable/machine readable copies of virtually everything you can (make your point loud and clear)

OGD = opportunity ≠ burden 8 Elements of Open Data
/open is a place to serve the public not the agency.
/open is a place to demonstrate government can follow good practices for web 2.0 collaboration and sharing
/open is an aggregation point for citizens to look for certain information - some of it can exist elsewhere (e.g. FOIA site/section or Data.gov) – that is okay!
/open pages should be pro-active. If they dont make you share it yet, they will so set the stage early.
/open should be preparing your agency to be "scored" - lots of people, not least the administration will do this.
/open should be preparing your agency to serve data in more forward looking ways (APIs, Fed dashboard integration, etc.)

Open Government Data Principles 8 Elements of Open Data 5. Machine processable : Data is reasonably structured to allow automated processing. 6. Non-discriminatory : Data is available to anyone, with no requirement of registration. 7. Non-proprietary : Data is available in a format over which no entity has exclusive control. 8. License-free : Data is not subject to any copyright, patent, trademark or trade secret regulation. Reasonable privacy, security and privilege restrictions may be allowed. Compliance must be reviewable. 1. Complete : All public data is made available. Public data is data that is not subject to valid privacy, security or privilege limitations. 2. Primary : Data is as collected at the source, with the highest possible level of granularity, not in aggregate or modified forms. 3. Timely : Data is made available as quickly as necessary to preserve the value of the data. 4. Accessible : Data is available to the widest range of users for the widest range of purposes. Source: Open Government Working Group Meeting in Sebastopol, CA, October 22, 2007

Straightforward Steps to Publish Government Data
Step 1: Publish well structured raw data
Step 2: Create an online catalog of the raw data (complete with documentation) so people can discover what has been posted.
Step 3: Make the data both human- and machine-readable
8 Elements of Open Data Source: Publishing Open Government Data W3C Working Draft 8 September 2009

/Open: behind the scenes 8 Elements of Open Data
Government agencies have unique specific challenges that must be carefully managed and addressed before data can get onto the web including :
Security
Privacy
FOIA
Records management
Accessibility (Section 508)
Accuracy
Various Regulations (PRA, etc.)

OGD & FOIA 8 Elements of Open Data
They want:
Your process
Your plan
Your contacts
Your stats (extra credit)
They do not ask for another site, existing resources can be pulled under the /open umbrella
The Directive also asks for similar information about how your comply with congressional requests

Open Government Data Stack 8 Elements of Open Data

So How Do You Get Started? 8 Elements of Open Data

/Open Concept Site 8 Elements of Open Data
/open is an open source technology concept we designed to prepare a simple approach to open government data and communications through a templated installation of Drupal.
How it is being developed? From our work with related open government efforts, we’ve developed a framework and process for implementing sites that are compliant and forward-thinking about OGD.
Why? Because open technology can only be used to accomplish OGD goals if it’s done correctly, responsibly, and with minimal burden on agencies.
Who will use it? Government agency technology reps required to comply with the OGD.
To accomplish what? Immediate help with compliance, but also proactive commitment to open government shared through open technology

Why Our /open Concept Helps The Big Picture – What We Use
Using proprietary, closed software in your efforts to show how "open" your government agency is just doesn't make sense. Now, we need a solution that is…
Ready to go to get you compliant on time with a templated approach to not missing key elements of the OGD
Implements site requirements using best practices, not quick fixes
Sets the right path to promote open government for future work, updates, data sets, collaboration
Makes it easy to update, change, publish, follow (RSS)
Provides a collaborative environment for citizen participation
Built/managed on a sensible infrastructure

What does /open look like? wireframes

Contact Information Web: phase2technology.com Blog: agileapproach.com LinkedIn: Jeff.Walpole Twitter: rockstarin86 [email_address]

http://wistowns.com	207
http://acquia.com	26
http://wisd.wistowns.com	4
http://cruiskeenconsulting.com	2
http://www.wistowns.com	1
http://www.cruiskeenconsulting.com	1
http://cityofdunn.wistowns.com	1

OGD - Jeff Walpole

by Acquia on Jan 20, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

7 Embeds 242

Statistics

OGD - Jeff Walpole — Presentation Transcript