The Origins of eGov Open Data: eGov Applications
summary
A Hawaii state portal runs as a self-funded portal hosting 98 online services and processing 63,000 transactions in seven days; typical projects take 90–120 man‑days. Forms move from paper to JSON open data rebuilt every 15 minutes; single sign‑on (Spring) and centralized PCI payment processing are standard. A DMV/ID workflow drops average service time from 110 to 12 minutes, license renewals hit 85% online, and an e‑bench warrants: 990,000 backlog → 12s retrieval overhaul proves scalable with code escrow and three‑year contracts.
AI-written summary · about
chapters (12)
- 0:00Start
- 7:29Overview
- 20:00Temptations
- 21:17Polymorphism
- 24:26Assumptions
- 24:52Questions
- 26:16Strategies
- 27:28Single Sign On
- 27:44Payment Processing
- 29:31Messaging
- 29:56Customer Support
- 37:23Harder to implement
related talks
27mWhy your API portal is so bad and what you can do about it
17mA case study: Ditching the paper for Drupal
28mWriting Docs Is a Chore
26mThe three things your developer portal can't live without
19mStreamlining API Documentation: Proven DocOps Strategies
29mThe experience choosing a framework for documenting APIs
38mAgile, Lean & Rugged - The Paper Edition
33mBreaking Down Paywalls for Online Health