Comments for Liliendahl on Data Quality

Comment on 255 Reasons for Data Quality Diversity by Henrik Liliendahl Sørensen

Henrik Liliendahl Sørensen — Fri, 25 May 2012 15:16:42 +0000

Thanks QAS and thanks for the follow up outside the blog.

Comment on Do You Want Social MDM? by Henrik Liliendahl Sørensen

Henrik Liliendahl Sørensen — Thu, 24 May 2012 06:52:18 +0000

Thanks a lot for joining the discussion here Conrad.

I agree. Privacy is a huge somewhat unknown factor in social MDM.

About B2C and B2B I have a feeling that B2B actually will bring the most business cases. That is based on the way I work myself and I know many other people doing B2B do. We use LinkedIn (Xing, Viadeo…) as an integrated part of reaching out to and learning about business partners. Twitter too – I think I found you there. Sooner or later that will be “systemized”.

Comment on Do You Want Social MDM? by Conrad Chuang

Conrad Chuang — Thu, 24 May 2012 00:15:14 +0000

Apologies about the date, we misinterpreted ISO 8601

w/regards to social MDM, it may be interesting if you’re a consumer-focused (B2C) concern but for B2B? In addition to Chris’ example of tracking customer sales, social MDM could come in handy for segmentation after correcting for sampling bias. That said there a lot of unknowns in the regulatory realm. How will the revised EU Data Protection Directive will affect social networking, let alone use of social network data by 3rd parties? And will non-EU citizens begin to demand the same kinds of protections outlined in the directive? Is the US next? (You could argue that the USA FTC Do-Not-Track recommendations have antecedents in the EU ePrivacy Directive).

Some interesting conjecture and it is of course the role of a vendor to establish a vision in the market. But while “Social” may be good for marketing lines, I am with Prashant on the need for firms to get on board with some basic blocking and tackling with “plain simple MDM”.

Comment on Do You Want Social MDM? by Henrik Liliendahl Sørensen

Henrik Liliendahl Sørensen — Wed, 23 May 2012 07:07:09 +0000

Thanks Prash and Chris for commenting.

There is of course a difference about:
• What every single enterprise should do in MDM according to current maturity and way of doing business
• What a MDM tool vendor should explore according to market assessment, analyst input, current customer base and technology stack

Comment on Do You Want Social MDM? by Chris Boorman

Chris Boorman — Tue, 22 May 2012 22:51:32 +0000

As one of the vendors talking about social MDM, I think it's important to gives vision to the market while also delivering pragmatic solutions for today. Social MDM is going to be big as enterprises, starting with Retail, look at opening up new routes to market through social networks. It makes sense that MDM is at the core since MDM enables you to understand the single view of a customer - and their relationships both within and beyond the enterprise. So, I for one, like to hear of vendors with a vision for the future that shows where the industry is going. If you want to see the Informatica vision, then take a look at our CEO Sohaib Abbasi delivering the keynote at informatica world last week - social MDM is a big part of it! (www.informaticaworld.com).

Comment on Do You Want Social MDM? by Prashant C

Prashant C — Tue, 22 May 2012 22:17:28 +0000

I want it. But only after I get all these customers get on board with plain simple MDM first. I deal with so many of them on a day to day basis who probably will start thinking about social MDM (even lean MDM) and big data probably a decade from now.

Sorry, if this sounds like a rant. The reality is that there are tons of them who just are still in a stone age when it comes to data management.

Comment on Avoiding Contact Data Entry Flaws by johnowensblog

johnowensblog — Mon, 21 May 2012 19:46:47 +0000

With proper analysis and design input screens should be easily able to deal with this problem. Once you have selected a) the country and b) the language you wish to use, the address can be verified against a database for that country in that language.

The data structures to support this functionality are relatively simple.

The real challenge is loading the correct domain data a into the database or wiring the form into the cloud. This latter would be the preferred option as it would keep all data current.

Unique keys are simply that, unique keys. They do not identify anything and, consequently, cannot uniquely identify anything. Their misuse as unique identifiers is one of the greatest causes of duplication in databases.

Comment on 255 Reasons for Data Quality Diversity by Experian QAS

Experian QAS — Mon, 21 May 2012 17:29:14 +0000

Henrik and Daragh,
Thank you for highlighting this. We do focus on SEO internally as well as with an agency. However, this activity is certainly not in line with our social media marketing practices and is something we will be investigating immediately.

Comment on Avoiding Contact Data Entry Flaws by Henrik Liliendahl Sørensen

Henrik Liliendahl Sørensen — Mon, 21 May 2012 12:20:42 +0000

Thanks for joining Lynn. Just checked out the WDM Road 65.

Comment on Avoiding Contact Data Entry Flaws by lynnvanavermaet

lynnvanavermaet — Mon, 21 May 2012 11:09:19 +0000

Hi,
In Belgium we have the same problem. Even within one country, some addresses exist in French and in Dutch, other addresses exist in French and German. And as, moreover, the Belgian postal system is not very structured and logic, it can be quite dificult to create a single ‘address’ view as of the point of data entry of new client records. One solution can be to create a unique address key that identifies a street (or an another geographic element) in a unique way, independent from the language it is written in. One of the Belgian companies that has created this unique view on Belgian addresses, is WDM Belgium with it’s Road65 tool.