It has been over seven years since President Obama signed the executive order that launched the federal open data movement. Much progress has been made, and there is still more to do. Along with the United States, over 100 nations have started programs to provide open access to government data. From large metropolitan governments to small cities, governments are opening up their data to provide better transparency and better delivery of government services. Open government data is also adding $3 trillion a year to the global economy.
In this time, several different approaches to creating open data programs have evolved. A recent article in the Government Information Quarterly describes five approaches.
- Data-oriented: Governments create open data publication policies. This is the most fundamental approach.
- Program-oriented: Along with publication policies, the government establishes a governance structure with policies and strategies.
- User-oriented: In this approach, the open data policies are based on consumer requests.
- Scorecard and impact-oriented: This approach considers the greater societal impact of the open data program.
- Ecosystem: The most mature approach which is described in the next paragraph.
In the ecosystem approach, there are three major actors: open data providers, open data users and open data beneficiaries. The open data users are between the open data providers and the open data beneficiaries. The government agencies are the open data providers because they provide the open datasets and APIs* to the open data users. Open data users are transparency activists and app developers who craft the open datasets and APIs into open data products and applications. The open data beneficiaries are the eventual consumers of the open data products and applications. Throughout the ecosystem are robust feedback loops that help guide what government data is released and what open data products and applications are created.
You can see two examples of the ecosystem approach in the federal government. First, there are the hackathons and challenges that agencies periodically arrange to bring data users and data beneficiaries together to explore how particular open datasets and APIs can be used for the benefit of the American public. A great example is the National Aeronautics and Space Administration’s (NASA) 2016 Space Apps Challenge.
A second example is the Department of Health and Human Services’s (HHS) Demand-Driven Open Data (DDOD). As I wrote in a previous column, users create a “use case” when requesting data. A use case describes not only the data requested but also how the data will be used and who will benefit from the open data. The use cases are compiled into a library that is searched by other potential requestors. The goal is to create a community around released open datasets and APIs. Add the communities together and HHS has an ecosystem around all of its open data.
As more federal agencies adopt an ecosystem approach to open data, a larger federal ecosystem of ecosystems can be created. The benefits of a federal ecosystem is that it will be easier to share open data; open data products and applications; and open data development best practices. Also, I can see how easily Human-Centered Design (HCD) and Agile Development can be incorporated into the ecosystem approach. However, the most beneficial advantage to the ecosystem approach is that good customer service is built in through the robust feedback loops between the open data providers, the open data users, and open data beneficiaries._*API – Application Programming Interface. How software programs and databases share data and functions with each other. Check out APIs in Government for more information._ Each week, The Data Briefing showcases the latest federal data news and trends. Dr. William Brantley is the Training Administrator for the U.S. Patent and Trademark Office’s Global Intellectual Property Academy. You can find out more about his personal work in open data, analytics, and related topics at BillBrantley.com. All opinions are his own and do not reflect the opinions of the USPTO or GSA.
Have feedback or questions? Send us an email »