Comments on: Breach Datasource Design Criteria

By: Lyger

Lyger — Thu, 28 Sep 2006 23:53:51 +0000

“This data entry is an embarrassingly parallelizable task, people! :^)”
/s/parallelizable/paralyzing
Sometimes literally. Where’s my chiropractor?

By: Chris

Chris — Thu, 28 Sep 2006 22:33:15 +0000

"backfilling into a dataset almost six years old can sometimes take hours a day." True dat. I want NY to make version 2.0 of their reporting document an NCS form. This data entry is an embarrassingly parallelizable task, people! :^)

By: Lyger

Lyger — Thu, 28 Sep 2006 22:15:31 +0000

Chris,
All excellent points, and I’m glad you posted your “quick” thoughts. A couple of mine:
Regarding point 2: While convenient, web interfaces shouldn’t be a standard. Yes, while point-and-click GUI goodness may be desirable, it’s the data itself that poses the biggest issue, not the file format or protocol in which it’s presented. Attrition considered a web interface at one point but decided that the security risks weren’t worth the hassle.
Regarding point 6: additional information would certainly be welcome. As you mentioned, this would be best done by a group who could dedicate a full-time effort. As you and I both know, gathering information, expanding catagories, and backfilling into a dataset almost six years old can sometimes take hours a day.
Regarding point last: Free. And sushi.
Would type more, but another breach probably just happened. AFK 60.. ;)
Lyger