Showing posts with label PII. Show all posts
Showing posts with label PII. Show all posts

Monday, September 16, 2013

#notsobigdata- an update, a new spreadsheet, and gym rats!

Sometimes I feel like a nanobot in the data universe. A pretty diligent, hard-working nanobot, to be sure. But in terms of the data I typically handle, still very much a nanobot... and in the For What It's Worth Department, nano == 10-9.

I didn't get many cards for my birthday this year: actually, I only got one, and it was from an insurance agent in Utah. I live in Illinois; I guess I won't get any when their #notsobigdata specialists clean up his mail list. In the bigger scheme of things, I guess the ~seventy-five cents this agent probably spent on this card isn't any big deal. However, when one considers the cost of bad data (and in this instance, my name is bad data) on a larger scale, its easily into the millions of dollars when one considers how many (postal) mail lists exist. In my current role, I have the opportunity to look at all sorts of mailing list data. Just last Saturday I was doing a quality check on a segment of a job, and I ran across some bad data. In this particular instance, the program looked for the addressee's (member's) first name (fname) and last name (lname). This particular customer has a couple of places where the lname is used and the fname is not. The customer wants verbiage like "To the lname home", in some places and "To the head of the lname family" in others. Its really a nice, personalized rewards mailpiece, but it breaks down when the data are incorrect. As in, when the member puts their lname in the fname field, and vice versa.

Lets face it, you and I fill out lots of forms. For our favorite stores, there may be some sort of loyalty or rewards program: we agree to give the store certain information, and in return, they pass along some savings. Jennifer and I (and Daniel) are members of a number of these, and for the most part, the paltry amount of personally identifiable information (PII) that we surrender is a fairly small price to pay in return for the savings on merchandise that we realize. There are other programs that we participate in, though, where we have some options as to our input, and in these we further limit our exposure. Yes, we reap some benefits of the programs, but we do not share all of the data they request.  

In other data news, Jennifer and I have been going to the gym recently, and now that we've been going for a few weeks, its time for a report. 

It only took us about a week to recognize many of the "regulars" at our local Parks and Recreation Department Fitness Center (a.k.a. the gym). There is what I suppose is the usual assortment of 40- and 50-something folks wanting to get (back) into shape, some 20- and 30-something women.... mostly women who hit the cardio equipment hard, and then there are the runners, lifters and other sundry amateur athletes.

Among the lifters, I'm the only one who keeps a log book. At least, I've never seen anyone else there with a logbook. My logbook goes back about two years, and documents my previous intermittent attempts to become a more physically fit human specimen. Now that Jennifer and I are working together, the plan is finally starting to come together. My logbook has blood pressure, weight, and exercise activity. It is going to get transferred to a spreadsheet pretty soon- and that's the #notsobigdata.  #notsobigdata really is important, especially if it pertains to you or to someone you love. Don't be a victim of big data. Use #notsobigdata to make a positive impact on your life!

As always, I am hochspeyer, blogging data analysis and management so you don't have to.

**I almost forgot: time to post links to some *ahem* golden oldies!


Wednesday, August 21, 2013

What's in a name? Or, for Bowie fans, Changes.

As I progress through a deeper experience (and hopefully a greater understanding) of not-so-big-data, I've come to realize that Ye Olde Blogge needs a bit of a tech refresh. Nothing really out of my comfort zone, but a few changes to make that old, familiar sweater feel more comfortable in 2013. Therefore, I've made a few minor changes to the look, and updated the title- which now more closely aligns with my philosophy on data.

I'd like to take a few steps back and try to explain why #notsobigdata is vitally important, possibly even more than Big Data or Megatrends. By the way, I did not read John Naisbitt's Megatrends, but I do remember seeing it in bookstores (does anyone remember bookstores?)

#notsobigdata, though, is both important and timely. It does not necessarily appeal to larger corporate consumers, but rather to ordinary folks, SOHOs and SMBs... a whole lotta acronyms that identify data producers and consumers... folks that, if they knew how to gather or interpret data, could possibly compete more successfully with the big players in their respective industries, or budget money better.

My #notsobigdata is focused on insurance and entertainment at this particular moment. Insurance and entertainment may seem like strange bedfellows to the casual observer, but have you ever considered how much media you have purchased in the past year? Have you ever considered how you would replace it should something catastrophic happen? In other words, if you have a collection of media that is stolen or destroyed, how would you recoup that loss?

The "cloud" is a consideration, I suppose. You could store all of the data about your collection(s) there. The problem I have with the cloud is that its hardly private- and this is true of all of your web-based email as well. I've never been really comfortable with posting all sorts of photos on the internet, which is the primary reason I don't post many pictures- and the ones that I do post are generally not of persons. I also take steps to control PII (personally identifiable information)- which is why nicknames are often used in this blog.

Not to belabor the point, as I've mentioned this at least a few times- the biggest problem I have with data is actually entering it into the tables or worksheets (I'm currently using both Excel and Access for this project). It's not that I mind doing it, it's just that I'm not particularly quick (~30 wpm). And, I don't have enough data in some of the tables yet to justify making some nice-looking front-end which could speed the data entry process. I do see a future for dashboards, though, and possibly some sort of map-like application. Alas, those things are the toys which may be in the database of my future- but for now, I have to be content with building my as yet to be glorious database one cell at a time.

As always, I am hochspeyer, blogging data analysis and management so you don't have to.