|Browse Use Cases|
Welcome to Demand-Driven Open Data (DDOD)
This wiki is a knowledge base containing detailed descriptions and specifications of use cases for open datasets from many organizations under the U.S. Department of Health and Human Services. Each starts of with a specific business or research problem the use case is trying to address. Ultimately, solutions -- both short-term workarounds and long-term implementations -- get entered here as a public resources.
To get started browse the library of Use Cases or run a search for your topic of interest.
If your business or research problem is not addressed by any of the existing use cases, you can create a new one. Go to DDOD Github Issues and click "New Issue". Github issues are used for entering new requests and hosting discussion between data owners and users that's visible to the public. These "issues" go through all of the predefined stages of the DDOD process. They are linked to related wiki entries, which have specifications and solutions.
|Enter a new Use Case|
Demand-Driven Open Data (DDOD) guides Open Data initiatives by giving external users a way to ask for the data they need
Demand-Driven Open Data (DDOD) is a framework of tools and methodologies to provide a systematic, ongoing and transparent mechanism for you to tell public data owners what's most valuable.
All work is entered, prioritized, implemented, and validated in the form of "use cases". This approach allows for all projects to have a known value even before work begins. It is the Lean Startup approach to open data initiatives.
How DDOD Works
Ready to get started? This document is an introduction to DDOD intended for Data Users. That could include anyone in industry, academia, nonprofits or even other government orgs who could benefit from DDOD.
Combined Workflow and MilestonesHere's how the pieces come together.
Progress on Use Cases
The "Value Delivered" is a category assigned to a use case that describes the type of artifacts and solutions that have been delivered to benefit the user community. A use case typically has multiple value categories associated with it, since it benefits users in different ways. Even the documentation of the use case itself has benefit, as it describes a specific situation for which requested datasets can be used.
Here's the tally of the value delivered so far in DDOD's portfolio of use cases