Strategic Intent

Dataset Versioning

Perhaps it's there and I don't see it, but it would seem that some kind of automated versioning system needs to be in place. My concern, from a transparency standpoint, would be if there is the capability to overwrite an existing dataset. Even if it is well intentioned, if the original dataset is not preserved, questions could arise as to what has been changed/added/removed. This could also help with datasets that ...more »

Submitted by (@rowdydata)
3 comments

Voting

28 votes
Active

General

Relate Datasets

In browsing the current Data.gov holdings, one sees data which has in some instances been chunked (for example large datasets which would contain too many records as CSV) - perhaps these may be broken out by state, et cetera. Similarly, there are cases where there are datasets which are part of a time series (e.g. 2005->2006->2007 annual data releases) - it would be useful toward usability to have ways to relate these ...more »

Submitted by (@davidsmith)
4 comments

Voting

27 votes
Active

Strategic Intent

Create Scenerios Showcasing Data.gov Contributions for Key Issue

Many professional and social circles continue to focus on issues such as climate change, governmental fiscal imbalances, the demographic shift to older populations, depleting resources, health care, and increasing technological complexity. We are about to embark on a new decade and these unresolved issues will follow us. How will Data.gov contribute toward addressing the tough questions we face in the next decade? ...more »

Submitted by (@suzanne.acar)
6 comments

Voting

27 votes
Active

Developer's Corner

Developer Wiki

Though there is another idea regarding a wikipedia entry... I think it is important to have a separate wiki set up for developers as there are many developer topics where collaboration is key. Of course, there are tons of precedent for this whereby many major development efforts/sites have developer wikis.

Submitted by (@michael.daconta)
7 comments

Voting

26 votes
Active

Developer's Corner

Code Repository

In addition to posting datasets and web services, Agencies should also be posting code and documentation. As with a data policy of "By default, all data should be made available, unless there are compelling reasons why not, e.g. sensitivity" so to should be the case with GOTS code. A large number of parallel development efforts by contractors and agency staff alike are underway across many agencies, often replicating ...more »

Submitted by (@davidsmith)
9 comments

Voting

26 votes
Active

Solution Architecture

Use common digital formats for files

I feel like this is an obvious one but I just tried downloading some data set that has .dbf, .shp, and .shx files. I don't recognize any of these and could not open any on my computer.

 

Lets make this useful but allowing the data provided to be accessed.

Submitted by (@tegoulet)
6 comments

Voting

24 votes
Active

Solution Architecture

Improve Browsing of Data.gov

While there are quite a few discussions on this site about search; I would like to see improved browsing via a robust taxonomy/folksonomy of topic areas. In fact, I would recommend both a top-down/bottom-up approach where you begin with a top-down taxonomy but allow it to be extended via topic area suggestions and popular keywords. As a citizen, I don't always know what I want but want to browse and see what is available. ...more »

Submitted by (@michael.daconta)
5 comments

Voting

24 votes
Active

General

Clarify Data.gov Feedback Loop

I applaud the visionaries behind Data.gov for understanding the importance of feedback. It is great that there are feedback input mechanisms for datasets and also this feedback input site (ideascale) for feedback on the solution governance, architecture, and technologies. But in an ideal world feedback is an ongoing conversation, with comments or suggestions going into the system, responses and requests for use cases ...more »

Submitted by (@larrytalley)
1 comment

Voting

24 votes
Active

Solution Architecture

Super Crunching

Require agencies to submit datasets in standard format with common metadata fields, including short and long descriptions to improve user understanding of data-set. Create a user interface that enables users to easily graph multiple time-series data sets (simple trend graphs). This will let them visually compare different data sets on relative scales. By aggregating all government data into a standard format and enabling ...more »

Submitted by (@kohler.jim)
5 comments

Voting

23 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

Strategic Intent

Data Quality - Need process for assuring 'good data' on Data.gov

On Page 9 of the CONOP, the example of Forbes' use of Federal data to develop the list of "America's Safest Cities" brings to light a significant risk associated with providing 'raw data' for public consumption. As you are aware, much of the crime data used for that survey is drawn from the Uniformed Crime Reporting effort of the FBI. As self-reported on the "Crime in the United States" website, "Figures used in this ...more »

Submitted by (@chuckgeorgo)
5 comments

Voting

23 votes
Active

Solution Architecture

Facilitate Access to Agency Web Services via Aggregation

In addition to providing Agency metadata and facilitating informed discovery of datasets, there may be a good role for Data.Gov to serve in also serving as a clearinghouse for discovering and facilitating access to datacentric agency web services, e.g. Open Geospatial Consortium Web Map Service (WMS) and Web Feature Service (WFS). In many instances, these types of services may lie scattered across and within agencies, ...more »

Submitted by (@davidsmith)
Add your comment

Voting

23 votes
Active