- Downloading MongoChef - free #MongoDB GUI with full support for MongoDB 3.X 3t.io/mongochef via @MongoChef>> 1 month ago
- Migrating from Relational Databases to MongoDB lnkd.in/eNMWqbE>> 1 month ago
- Migrating from Relational Databases to MongoDB by @matkeep #migration #mongodb slideshare.net/matkeep/migrat… via @SlideShare>> 1 month ago
- cannot wait to mess with this! lnkd.in/ecimasm>> 1 month ago
- "is Chief Data Officer a Game Changer? " lnkd.in/ek-k6ry by @Rkreddy0228 on @LinkedIn>> 2 months ago
An event based log about a service offering
March 24, 2011Posted by on
As expected, customer data quality remains at the top of list with regard to having the most issues. Ironically, this domain has been at the forefront of the data quality industry since its inception.
One reason for the proliferation of concerns about customer data quality could be its direct link to revenue generation.
Whatever the reason, this poll seems to indicate that services built around the improvement of customer data quality will be well founded.
Once again there are no surprises when looking at what data improvements are desired. Data owners seem to be interested in a centralized, synchronized, single view of their data, most notably customer.
The good news that can be gathered from these polls is that as an industry, data quality is focused on the right data and the right functionality. Most data quality solutions are built around the various aspects of customer data quality and ways to improve it so there is a master managed, single version of a customer. The bad news is we’ve had that focus for quite some time and data owners are still concerned.
In my opinion, this is due to the nature of customer data. Customer data is at the core of every business. It is constantly changing both in definition and scope, it is continuously used in new and complex ways, and it is the most valuable asset that an organization manages.
One thing not openly reflected in these polls is that it is likely that the same issues and concerns that are present in the customer domain are also present in the employee and contact domains. However, they tend not to “bubble up” to the top of list due to lack of linkage to revenue and profit.
I’d encourage comments and feedback on this post. If we all weigh in on topics like this, we can all learn something valuable. Please let me know your thoughts on the poll results, my interpretation of the results and opinions.
February 2, 2011Posted by on
Recently a reader asked me if I had any posts on “data quality basics”. Turns out, I didn’t. So I’ve decided to put together a series of posts that covers what I feel are the basic essentials to a data quality program.
[tweetmeme source=”dqchronicle” only_single=false http://wp.me/prD2R-fe]
The many sides of data quality
It is generally accepted in the data quality world that there are seven categories by which data quality can be analyzed. These include the following:
- Conformity – Analyzing data for conformity measures adherence to the data definition standards. This can include determining if data is of the correct type and length
- Consistency – Analyzing data for consistency measures that data is uniformly represented across systems. This can involve comparing the same attribute across the various systems in the enterprise
- Completeness – Analyzing data for completeness measures whether or not required data is populated. This can involve one or more elements and is usually tightly coupled with required field validation rules
- Accuracy – Analyzing data for accuracy measures if data is nonstandard or out-of-date. This can involve comparing data against standards like USPS deliverability and ASCII code references
- Integrity – Analyzing data for integrity measures data references that link information like customers and their addresses. Using our example, this analysis would determine what addresses are not associated with customers
- Duplication – Analyzing data for duplication measures the pervasiveness of redundant records. This involves determining those pieces of information that uniquely define data and identifying the extent to which this is present
- Timeliness – Analyzing data for timeliness measures the availability of data. This involves analyzing the creation, update or deletion of data and its dependent business processes
January 9, 2011Posted by on
As a follow up to my previous post, I have compiled a checklist that can used to manage the effort of preparing for a data quality engagement.
- Form a data quality mission statement
- Define the systems and data in-scope
- Define the data quality environment
- Extract the data and land it to the data quality environment
[tweetmeme source=”dqchronicle” only_single=false http://wp.me/prD2R-et]