Solution Architecture

For this topic area post your best ideas on Data.gov and its capabilities, including data management, dissemination, search, semantic web, evolving core modules (shared services), data infrastructure and visualization tools and more.
(@niemann.brand)

Solution Architecture

Build Data Catalogs in the Cloud in Support of Data.gov & EPA's Strategic Data Action Plan

My Data Science Class Project (see http://federaldata.wik.is/Data_Science) is to re-architect Data.gov so that it responds to the IdeaScale Comments, is reusable, and is interoperable (searchable) with other data catalogs (international and sub-national). I am following an architectural pattern that starts with spreadsheets, uses a wiki for the metadata with well-defined URLs, provides analytics/visualizations, and lays ...more »

Voting

1 vote
Active
(@bobbygrant25)

Solution Architecture

HTML 5 compatability

This could be used as an alternative to Adobe Flash because of the inherent disadvantages of flash (lack of support on current phones/tablets excluding Android 2.2 devices, major stability and performance issues). This might also allow for specific apps to be made for the different mobile Operating Systems which as we have already seen with the expansion of the app stores breeds innovation and ideas that no one else ...more »

Voting

1 vote
Active
(@ekansa)

Solution Architecture

Faceted Search with Atom Based Web Services

Data.gov should have a faceted search interface that provides a comprehensive overview of Data.gov content (metadata and facet counts), and a way for users to progressively refine their search criteria. Faceted search provides a good way for outsiders to better understand a big collection described by complex metadata structure. The faceted metadata should also be shared as an Atom Feed, so that updates of new content ...more »

Voting

4 votes
Active
(@michael.daconta)

Solution Architecture

Remove and Guard Against (Validate) "Junk" Records

I tried to download a dataset that interested me called the "Occupational Outlook Handbook". The data.gov "record" says that it is a CSV dataset. However, when you click the csv link you go to a website that does not allow you to download the dataset! The data.gov link is: http://www.data.gov/details/336 This is a failure of the simplest validation possible - a link that is supposed to be to a dataset must be tested ...more »

Voting

7 votes
Active
(@michael.daconta)

Solution Architecture

Don't Inflate Counts! (aka let a Dataset contain multiple files)

When searching for interesting datasets it can be very frustrating to see identical datasets (except by year) cluttering the search results. To me, this seems like just an attempt to inflate the counts by treating separate years or geography as separate datasets. Here is my proposed simple rule: If the dataset metadata fields (i.e. like "Coverage Date") are the same, it is the SAME dataset. Just because the instance ...more »

Voting

10 votes
Active
(@davidsmith)

Solution Architecture

Link / Status Checker

Via a blog post, http://www.spatiallyadjusted.com/2010/02/07/data-gov-is-already-broken-just-like-everything-before-it/ - it would be good to integrate periodic link/service checking, ala Geospatial One Stop's Service Status Checker - http://registry.fgdc.gov/statuschecker/index.php. Any status changes/outages should be reported via notification, e.g. RSS feed / email, and directed to the stewards and registrars managing ...more »

Voting

6 votes
Active
(@afuller)

Solution Architecture

Make RSS Feeds Available

This entry is a consensus recommendation of seven organizations that work on government transparency of which OpenTheGovernment.org is one.

 

Consider making some of the datasets available as feeds that are constantly up to date, rather than as static datasets that are pulled down and then reposted on an occasional basis.

Voting

11 votes
Active
(@afuller)

Solution Architecture

Make Data easier to find using tagging or metadata

This entry is a consensus recommendation of seven organizations that work on government transparency of which OpenTheGovernment.org is one.

 

Use tagging or metadata to enable the public to bring together information on a topic. The thesaurus that USA.gov uses provides a useful example of the needed vocabulary.

Voting

19 votes
Active
(@afuller)

Solution Architecture

Make web-based interfaces available for public use

This entry is a consensus recommendation of seven organizations that work on government transparency of which OpenTheGovernment.org is one. Some of the currently posted files are quite large, ranging upward to several hundred megabytes. Their large size undermines their usefulness for most people or organizations. The large number of currently posted datasets also makes it difficult to find a particular database of ...more »

Voting

7 votes
Active
(@afuller)

Solution Architecture

Balance the format of data for developers and the public

This entry is a consensus recommendation of seven organizations that work on government transparency of which OpenTheGovernment.org is one. The format of the data plays a key role in its usability; many within the community of advocates who re-use and repackage government data would prefer data in CSV format, rather than the XML format in which many of the posted databases are provided. Accordingly, we recommend that ...more »

Voting

5 votes
Active
(@davidsmith)

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 »

Voting

23 votes
Active