Blog: Dan E. Linstedt Subscribe to this blog's RSS feed!

Dan Linstedt

Bill Inmon has given me this wonderful opportunity to blog on his behalf. I like to cover everything from DW2.0 to integration to data modeling, including ETL/ELT, SOA, Master Data Management, Unstructured Data, DW and BI. Currently I am working on ways to create dynamic data warehouses, push-button architectures, and automated generation of common data models. You can find me at Denver University where I participate on an academic advisory board for Masters Students in I.T. I can't wait to hear from you in the comments of my blog entries. Thank-you, and all the best; Dan Linstedt http://www.COBICC.com, danL@danLinstedt.com

About the author >

Cofounder of Genesee Academy, RapidACE, and BetterDataModel.com, Daniel Linstedt is an internationally known expert in data warehousing, business intelligence, analytics, very large data warehousing (VLDW), OLTP and performance and tuning. He has been the lead technical architect on enterprise-wide data warehouse projects and refinements for many Fortune 500 companies. Linstedt is an instructor of The Data Warehousing Institute and a featured speaker at industry events. He is a Certified DW2.0 Architect. He has worked with companies including: IBM, Informatica, Ipedo, X-Aware, Netezza, Microsoft, Oracle, Silver Creek Systems, and Teradata.  He is trained in SEI / CMMi Level 5, and is the inventor of The Matrix Methodology, and the Data Vault Data modeling architecture. He has built expert training courses, and trained hundreds of industry professionals, and is the voice of Bill Inmons' Blog on http://www.b-eye-network.com/blogs/linstedt/.

June 2006 Archives

Reduce your development time, understand your data set and it's relationships in a visual format, accomplish all of this, and profile part of the data while your at it. You've heard of social networking on the web? If you've used Linked-In, or Plaxo, or another contact tool, you've seen some of the "social network diagrams" they produce. Well, now a company has gone and done something similar but with Source System data.

This particular product looks to have a lot of promise in the "understanding of data warehousing/data integration" space. It has an incredible visualization tool for data sets. Keep in mind it does not mine the data model (to my knowledge), but it is capable of extracting DATA RELATIONSHIPS based on patterns, that may be more business related than data model related. It brings the data set back to the business.

I'd love to hear what you think about Cogito, Inc.


Posted June 22, 2006 6:50 AM
Permalink | No Comments |

My oh my, we've thrown a lot of terms in to the mix. These days when you read magazine articles or you look through your local friendly blogger :) you find a slew of these terms used. Maybe it's time to refresh our memory on exactly what these terms mean. Why? Because they are pertinent to MDM and MMDM (master metadata data management). So read on...

These definitions have been pulled from http://www.websters.com

Taxonomy:
1. The classification of organisms in an ordered system that indicates natural relationships.
2. The science, laws, or principles of classification; systematics.
3. Division into ordered groups or categories: “Scholars have been laboring to develop a taxonomy of young killers” (Aric Press).

Classification:
1. The act, process, or result of classifying.
2. A category or class.
3. Biology. The systematic grouping of organisms into categories on the basis of evolutionary or structural relationships between them; taxonomy.

Ontology:
1. The branch of metaphysics that deals with the nature of being.

Registry:
1. The act of registering; registration.
2. The registered nationality of a ship.
3. A place for registering.
-- A book for official records.
-- The place where such records are kept.

Ok, what does this have to do with Master Data or Metadata or BI for that matter?
The industry is throwing the terms around too loosely. Registries are being used for Metadata, as such they should be - at the bottom level of a Taxonomy is a registry. The first step to successful enterprise Metadata Management or governance is getting a handle on the Taxonomy of the business and the metadata used within the business. This is critical to identifying and governing specific components of the MDM strategy.

Taxonomies should be utilized to manage, govern, and view (visualize) the metadata from an enterprise perspective. However, the act of building a metadata management solution, or a Master Data Management solution requires the implementation of a classification with a registry or set of registries underneath.

It is vital that we all speak the same language here and not get confused. Some of my blog entries I've discussed the possibilities of VISUALIZING data sets, well guess what? An EASY way to visualize huge metadata collections is to use a Tree classification as the implementation side of the taxonomy. The registries are at the leaves in the trees and provide further drill down, but have nothing to do with the visualization.

Wait a minute, I can see this for Metadata, but how does that help my MDM effort?
Well, as I've blogged before - Metadata or Master Metadata Management needs to be a part of EVERY MDM initiative out there. Why? Because it provides the CONTEXT to understanding our Master Data. How it's used, where it's used, when it should / should not be used, and what the elements mean at varying levels within the organization.

Master Metadata (at a very simplistic viewpoint) really is a data-driven taxonomy (representation) of the BUSINESS. Without tying our master data back to the business it will lose value quickly within the company, and eventually end up where all master systems end-up... in the sunset on the horizon...

Questions? Thoughts? Haiku's? Incantations? I'll take them all, let me know what you think...

Thanks,
Dan Linstedt
Daniel.Linstedt@MyersHolum.com


Posted June 21, 2006 2:45 PM
Permalink | No Comments |

I've blogged on this before, suggested that there be an equivalent "hidden signal" embedded in a data set, something that uniquely identifies each word, each paragraph, and each document (context). I wish there were a way (electronically) to construct and send unique keys to all data sets around the world; a single unified key structure (open, public but unique).

What's the business benefit? The business benefit would be the ability to key across B2B applications, the ability to recognize duplicate data, the ability to check remote web sites and b2b applications for unique data exchange. There are many more business benefits that I will elaborate on as we go forward.

Today, the only technology that can accomplish this is DNA computing within the Nanotech sector. DNA would give us the ability to uniquely "sign" data sets without destroying the data itself.

It's an interesting thought I think that bears more discussion and research; sort of an RFID for data if you will.


Posted June 3, 2006 5:59 AM
Permalink | 1 Comment |