A great example of a data integrity report!
A couple months back I discussed the importance of data integrity reports. One of my past clients and a longtime reader, David Churchill at Grantmakers in Health, offered up this idea, which I think is fantastic and should be added to any association's list of data integrity reports.
As he explains: "I found that there’s a lot of email address mistakes made during our online registration process. It's not always easy to spot simple typos like .cmo (.com), .ogr (.org) so I created a query that is titled “questionable top level domains” that shows any record with likely typos (or .ru which is largely spam)."
One reason I love this query is that it's designed to capture "common" errors with the knowledge that it won't catch every error. And it has the added bonus of looking at addresses that are likely spam.
But what a great idea! If a customer mistypes their email address, other than checking bounced emails in the future, how will anyone know there is an error? By proactively checking for errors, David is weeding the garden, which is critical to long-term data management success.
![]()
Wes's Wednesday Wisdom Archives
Don’t miss this year’s DAN Science Fair!
Don’t miss this year’s DAN Science Fair! I’m taking a break from my weekly tips […]
Just start. And it’s never done.
Just start. And it’s never done. Last week I had the opportunity to lead a […]
Don’t ask if you’re not going to answer!
Don’t ask if you’re not going to answer! In the past week, on three different […]
Seek forgiveness rather than permission
Seek forgiveness rather than permission “Seek forgiveness, not permission.” I can’t remember when I first […]
Is a 360 degree view necessary?
Is a 360 degree view necessary? “A 360 degree view of our members should NOT […]
Why data matters
Why data matters I write about data because managing our data effectively will help us […]
It’s about process
It’s about process I’m in the midst of adding an AI agent to my website […]
Data integrity reports
Data integrity reports I speak and write a lot about data integrity reports. So I […]
The most important training tip
The most important training tip I’ve been sitting in a lot of database training sessions […]
Be careful about getting tangled
Be careful about getting tangled “We had done a lot to tangle ourselves up.” – […]
