|
|
capturing data
by gdanner on May 12, 2006 - 01:24 PM read 581 times Source: http://blog.industrial-science.com/2006/05/capturing-data... |
|
I have written about data in a previous post. This one is about capturing data. Usually, we are simply given data for the models we build. Well... it's never THAT simple, but we are rarely given the task of capturing "raw data". In fact, it's been a while since I have personally been involved with physical task of raw data collection that will be used in some analysis. Or at least, I think so... one never knows for sure with the ease at which data is captured.
But I digress. It's really too bad that I've been removed from the process of collecting data. But in recent weeks, I have been involved with two different activities where I am physically capturing data. One is for a client. I have made visits to several sites where, with pencil and clipboard in hand, I follow someone from entrance into the parking the lot through all the "stations". All the while, I am collecting time and process data, as well as making observations. You see, the client has provided us with all kinds of data; we are on the lookout for "important stuff that is not captured by the data capturing systm". Nothing beats an on-the-ground investigation for getting good intelligence. Now... what to do with the info is another matter.
The second activity is for Arbitron. My family has been selected to become a radio ratings survey for this week. We carry a log around and make hand-written entries to capture our radio-listening habits. What station? When? Where did we listen, etc. This is facinating to me, since I often get to see the aggregation of such data collection, but I rarely get to participate as a "citizen". Hopefully, writing about this on this blog doesn't disqualify me.
Both examples activities have made me think a bit more about what is actually reliable about any kind of data that's collected through distributed means. How do you set it up so you minimize the variations across the different data collectors? How do you deal with fatigue, learning, changing habits? Does the act of capturing data actually change behaviors?
Come to think of it, I am probably NOT a good candidate for a Nielson or Arbitron servey.
But I digress. It's really too bad that I've been removed from the process of collecting data. But in recent weeks, I have been involved with two different activities where I am physically capturing data. One is for a client. I have made visits to several sites where, with pencil and clipboard in hand, I follow someone from entrance into the parking the lot through all the "stations". All the while, I am collecting time and process data, as well as making observations. You see, the client has provided us with all kinds of data; we are on the lookout for "important stuff that is not captured by the data capturing systm". Nothing beats an on-the-ground investigation for getting good intelligence. Now... what to do with the info is another matter.
The second activity is for Arbitron. My family has been selected to become a radio ratings survey for this week. We carry a log around and make hand-written entries to capture our radio-listening habits. What station? When? Where did we listen, etc. This is facinating to me, since I often get to see the aggregation of such data collection, but I rarely get to participate as a "citizen". Hopefully, writing about this on this blog doesn't disqualify me.
Both examples activities have made me think a bit more about what is actually reliable about any kind of data that's collected through distributed means. How do you set it up so you minimize the variations across the different data collectors? How do you deal with fatigue, learning, changing habits? Does the act of capturing data actually change behaviors?
Come to think of it, I am probably NOT a good candidate for a Nielson or Arbitron servey.
Featured
Author Profile
Subscribe
Feed for nGenera Community:
Public
Secure
Why subscribe? What is RSS?