Slashdot Mirror


Serious Design Failure At USAspending.gov?

theodp writes "Over at Intelligent Enterprise, Seth Grimes declares the Federal Government's USAspending.gov website a travesty, calling it 'almost a parody of a government-transparency site.' Among the faults cited by Grimes is a botched 'Federal Spending FY 2009 YTD' pie chart that graced USAspending.gov's home page. Not only were the sizes of pie segments not in proportion to the percentage labels (due to a Google Chart API error), the colors in the pie chart didn't even match the colors and values in the table immediately below the chart. Lucky for the Feds, Grimes didn't get a chance to look behind the curtain at the Federal IT Dashboard, where they forgot to remove a (commented) reference to a Google spreadsheet that states 'These totals are pretty poor numbers' (Google workbook). Oops!"

7 of 207 comments (clear)

  1. oookay by nomadic · · Score: 4, Informative

    Read the blog article, and I think that a better title for this slashdot article would be "minor design failure."

  2. Re:Criticize the Numbers Not the Presentation by synthparadox · · Score: 3, Informative

    I agree. When I first read the title, "Serious" jumped out at me (possibly with the assistance of being the first word), and luckily for me I actually RTFA'd. Speaking for myself and more than likely any one who's done any web programming, a minor mistake of data passing being in the incorrect format for the Google APIs to digest is much much less than a "serious" design failure. In fact, its not a design failure at all. Its a code error, and luckily (or possibly unluckily) for the guys at USAspending.gov, Google's APIs don't just segfault out and crash the page, instead they try to parse it in a "is this what you wanted?" sort of way.

    TL:DR - its not serious, its not a design failure, its a coding bug, and as TFA says its a 2-3 line fix. Not newsworthy if you ask me.

  3. Can't write HTML.... by aitala · · Score: 5, Informative

    The site's pages don't even have a proper BODY or HTML close tags..

    Jeez.

    Eric

    --
    Eric Aitala
    www.f1m.com
    1. Re:Can't write HTML.... by themacks · · Score: 4, Informative

      Not to mention the 253 errors from the W3C Validation site.

      --
      i read about it in a blog once
  4. Re:Bugzilla? by kevinNCSU · · Score: 4, Informative

    You mean something like this?

    Microsoft Contracts

    I mean come on, the search by contractors was only one click from the main page ;)

  5. Re:They are merely tallying points by M.+Baranczak · · Score: 3, Informative

    a system to systematically scrape all non-hidden data on popular sites like facebook and myspace

    Did you even read that link? The job it describes consists of archiving all the web content produced by the EOP (Executive Office of the President). Where does it say anything about facebook or myspace? Is it after the secret paragraphs that talk about the death panels and hiding the President's birth certificate?

  6. newness is not an excuse in this case by sbma44 · · Score: 5, Informative

    I work at the Sunlight Foundation, where we're pretty familiar with the people and data systems powering USASpending.gov. I've seen a lot of comments here saying that the important thing is that the government is publishing something, and that it's understandable that their first pass might not be perfect.

    But this isn't their first pass. The underlying data systems -- FAADS and FPDS -- have existed since the 90s, and have been riddled with errors throughout their existence. Instead of fixing the problems, OMB continues to slap new coats of paint on the same lousy data.

    It's nice that we've got a new USASpending.gov, and I agree that it would be a mistake to put too much emphasis on a buggy visualization. But the underlying data is terrible, and so far no one is showing the will to fix it. Just look at USASpending's "data quality" tab -- it talks about the completeness of each row. Well, that's great, but it tells you nothing about the thousands upon thousands of missing rows, nor about the rows that massively under- or over-report their dollar amounts.

    At Subsidyscope, the project on which I work, we've delved into these problems in more depth. Those who'd like to learn more about the shortcomings of the data systems powering USASpending can find a discussion of the relevant issues here.