Key Partnerships

Build and Leverage Existing Collaboration and Federation Models

Build upon approaches like EPA's Exchange Network toward federated architecture for data and assets, where standards-based approaches can be utilized to allow transparent discovery and access to data assets and catalogs where they reside.

Submitted by (@davidsmith)
4 comments

Voting

8 votes
Active

Agency Next Steps

Quality controls/checklist

The agency posting the data should assert that it has performed certain quality gates/checks on the datasets it is publishing. I just downloaded one dataset provided as a spreadsheet and one of the columns is: "Contructor" Either that is a weird term or it is an error and meant to say "Contractor". Looking at the data (which is a bunch of acronyms) it is probably the latter. Did whoever published the dataset check ...more »

Submitted by (@michael.daconta)
5 comments

Voting

14 votes
Active

Key Partnerships

Create a Data.gov Evangelist Position

Most of the big APIs like Twitter, Facebook, and now LinkedIn have a dedicated core team that spends a lot of time evangelizing the API and working with developers to get what they need. Data.gov needs a Data.gov evangelist who can be the community manager out on the road listening and talking and generally spreading the word on data.gov and its value. I think this is a separate role from leadership like Vivek Kundra ...more »

Submitted by (@sressler)
10 comments

Voting

46 votes
Active

Agency Next Steps

Publicly list the requests for data

You should list the types of data requested by the public and the number of votes for each type.

Submitted by (@georgevicbell)
7 comments

Voting

23 votes
Active

Agency Next Steps

Local Data

Should be able to filter by area of country, as well as include data (with appropriate notification) from cities, towns, and states.

 

There should be a standard way for cities, towns, states to incorporate their data into data.gov.

Submitted by (@georgevicbell)
Add your comment

Voting

20 votes
Active

Agency Next Steps

Reporting problems with data

The system should have a way to add "notes" about the data. This could include specific things that should be watched for (for example, the assumptions that the data was collected under, or the methology used to collect it)...it's not much use to use the dataset "tax data for 1999" in a mission critical application if the methology was to "ask 10 people what the tax rate was in 1999" Likewise, there should be ways ...more »

Submitted by (@georgevicbell)
8 comments

Voting

46 votes
Active

Key Partnerships

Public Health Laboratory Data

Many Public Health Laboratories and their users support implementation of an inter-operable and standards-based federal data network for laboratories so that data providers and data users can integrate their data submissions or requests among exchange networks to improve routine reporting and homeland security responsiveness. The data submission formats need to be flexible so they can be shared with multiple users, deliver ...more »

Submitted by (@krueger)
1 comment

Voting

4 votes
Active

Key Partnerships

Public Data.gov Roadmap

Many high-profile projects that rely on a community of supporters, like mozilla.org and open office, post a public roadmap that details major forthcoming plans and milestones. OMB/GSA should do the same for data.gov so that the public can see when planned innovations will occur and that they are actually influencing the evolution.

Submitted by (@michael.daconta)
Add your comment

Voting

29 votes
Active

Agency Next Steps

Transparency - Rules and Regulations

Federal Register notices currently provide full text narratives for proposed and final rule changes, mixing current and proposed (new) rules with historical text and information. My idea would be for the Federal Register to provide color text for each proposed and final rule impacting the CFR. By putting new or modified amendments in red text, for example, it would be much easier for the reader to distinquish between ...more »

Submitted by (@billthimmesch)
Add your comment

Voting

4 votes
Active

Agency Next Steps

Data Reference Model

With reference to the role of the agency CIOs as set forth in the draft CONOPS, it would be good if agencies published their segments of the Federal Enterprise Architecture (FEA) Data Reference Model (DRM) on their Web sites in XML format conforming to a finalized version of XML schema (XSD) for the DRM. http://xml.gov/draft/drm20060105.xsd Doing so would enable automated aggregation of the governmentwide DRM and faciliate ...more »

Submitted by (@owen.ambur)
1 comment

Voting

6 votes
Active

Key Partnerships

Data.gov is about data search: A strategy for Google, Bing & X

How do we leverage the power of Google/Bing and whatever is next to help people fin data? We need some new thinking! What is your idea? What solutions live between full text and fully structured metadata? We can and should improve Data.gov website search per the great suggestions here. We also need the API envisioned in the ConOps. But that is not enough. We need a way to better tag and expose data Agency data so that ...more »

Submitted by (@louissweeny)
5 comments

Voting

6 votes
Active

Key Partnerships

Expansion is Key

Link the data into 211 websites throughout the country. This allows 211 to expand the useage of their websites and accessibility to information. Look at NJ 211 as an example. All data information for them is now included for Non-profits to utilize when applying for grants. Create an application for Blackberry, Iphone and Android softwares. This allows people no matter where they are to look up information regarding ...more »

Submitted by (@helfer.shanee)
1 comment

Voting

7 votes
Active