I have extolled the virtues of databases for years. (I'm certainly no pioneer in this field so I'm not looking for any kind of pat on the back or anything.) I love how they can take extremely complex data and distill it down into actually usable chunks. After all, what good is information if you can't make any conclusions based out of it?
I'm probably an even bigger fan of real time data. For example, why wait until tomorrow to read a newspaper to find out what is happening right now? This is why I love RSS feeds, Facebook, Twitter and their ilk.
I also really like maps. Not sure why. You'd have to ask my mom why she thinks I spent hours of my childhood looking at atlases. I think it is because they take real data - for example of where a road or country boundary is - and representatively put that information into my hand to allow me to carry it around. One of my favourite childhood memories is my parents letting me navigate the family from Ontario to Florida at the age of 11. I still remember in high school, trying to sit as close to the Social Studies teacher's desk as possible because he had an amazing collection of historical maps because that made the class discussions 'real'; but I digress.
Where things really get exciting to me is when you can put databases together with real time information and present this information visually on a map. Here's an example of the most used terms on Twitter during the 2009 Super Bowl and where those words were originating. (h/t @brownbaggingit) To me, this is amazing stuff!
Even Richard Florida has become map/data crazed. In his most recent book, Who's Your City?, he begins setting up his premise by using light data collected by a satellites, cross refrenced with census and industry reports to visually represent the places of the world who excel at things like innovation. The maps provide powerful argument to his thesis that where you live is important.
To me, there are some real possibilities this kind of technology offers us. And it's actually not that difficult or expensive to achieve either; making it even more likely we will start seeing this kind of visualization continue to be become part of our vocabulary and expectations.
I for one can't wait to see more of this kind of real time data being used by governments and corporations to make important decisions. It will allow for 'informed' decisions to be even more so.
Plus who doesn't love a good map?
UPDATE: Another fantastic example of data being presented visually that just came to my attention: newstimeline.googlelabs.com
Tuesday, April 21, 2009
Where database technology is taking us
Posted by
DJ Kelly
at
10:39 AM
3
comments
Labels: databases, Facebook, maps, Richard Florida, Super Bowl, Twitter
Friday, May 2, 2008
Babies should not be murdered by poorly maintained databases!
Also available on the Calgary Herald's Q.
Databases are important. As a marketer I often preach this to my clients. As a matter of fact, a couple years back I told one that I was working for that if the building caught on fire there was only one thing they had to rescue: their computer server. That computer contained 10 years worth of client data and was, as far as I’m concerned, irreplaceable. I only half-kiddingly said, ‘the company will continue with a new building, you can train new staff, you can do your work with new equipment, but you cannot do business without the information included in that database.’
This past week databases and death collided in real life.
You no doubt have heard the story of the NE Calgary family that lost their child when it took paramedics 30 minutes to respond after they first dialled 911. What happened? It turns out this family has an VOIP phone – also known as an internet phone. The problem is these phones have developed a reputation as being unreliable when calling 911 – deservingly so in this case. The first time the family called for an ambulance they got a support tech – and promptly got disconnected. The second time they called they did finally get connected to emergency services. However before they could give all their data to the dispatcher they were disconnected again. Thinking they passed on enough info they waited for an ambulance to arrive. It never did. (Until a neighbour called from a good old fashion land line.)
So what went wrong? And what does a database have to do with it? Well, it turns out an ambulance was dispatched. To the family’s old address in Ontario. It seems, while the family’s billing information and IP information was updated in the internet phone company’s database, nobody ever updated their emergency contact info. And now a child is dead and a family is grieving with the worst lost imaginable.
In the company’s process ensuring they have the correct address to send a bill to was more important than ensuring the emergency services address was right. Two databases instead of one. Why?
I will remember this example next time I run into a database situation that drives me nuts. Like having Telus tell me it will take 3 months to clear my account after cancelling my home phone line, because their internet and telephone services are on a different billing cycle and are different databases. I’ll take a deep breath, sigh, think about how such a similarly small thing led to the death of a baby in north-east Calgary and thank God no one will die because my ex-phone company can’t keep their customers happy.
Posted by
DJ Kelly
at
5:35 PM
0
comments

