"Anyone Can be a #CivicTech Hero"

on YouTube ↗26m

" summary

A developer identifies a concrete problem with regulations.gov, finds the regulations.gov API on api.data.gov 1,000/hour limit, and builds an MVP site (fedgovregs.org) that fetches dockets, churns through up to ~200,000 comments, caches results by docket, and offers CSV exports and attachment filters. The solution uses the US Web Design System, requires each user’s API key to avoid global rate limits, and demonstrably reduces the manual paging the old site forced.

AI-written summary · about

" chapters (12)

1. 0:00Introduction
2. 1:06Speaker background
3. 2:10Three steps to build Civic tech
4. 3:35Regulations.gov problem
5. 7:06Finding open government data
6. 9:12Accessing government APIs
7. 12:23API limitations with caching
8. 15:31Open-source UI frameworks
9. 17:13Live demo
10. 22:27Become a Civic Tech Hero
11. 24:31Contribute to Civic Tech
12. 25:36Q&A

" related talks

• 38mA Conversation with Beth NoveckBeth Noveck, Tim O'Reilly · Web 2.0 Expo New York 2009
• 09mGovernment Data and the Invisible HandHarlan Yu · Gov 2.0 Summit 2010
• 28mGovernment.js - Building the JavaScript PartyMax Ogden · JSConf EU 2012
• 06mOne Step, Many Feet: How Technology...Stacy Donohue · Gov 2.0 Summit 2010
• 11mOpen Government, Idea Generation, ...John Porcari · Gov 2.0 Summit 2010
• 06mHow Open Data is Making ...David Eaves · Gov 2.0 Summit 2010
• 06minterviewed at Gov 2.0 – Carl MalamudCarl Malamud · Gov 2.0 Expo 2010
• 53mIf Government can do it...Gareth Rushgrove · GOTO Aarhus 2013