What Is Data Quality?
A vague definition of data quality is easy: "good data." A useful one names the specific, checkable problems it actually covers.
A checkable list, not a feeling
A concrete data-quality check covers a specific list of patterns: missing values, exact duplicate rows, low-cardinality or constant columns, numeric outliers, and inconsistent formatting in email, URL, date and categorical columns. Each of these is something a program can actually detect from the data — “is this data good?” is not.
Every finding needs four things
A useful finding states its severity, the affected column, a count and percentage, a plain explanation of what was detected, and a suggested action. “23 rows (4.6%) in the email column don't match a typical email format” is checkable and specific. “Email column has issues” is not.
“Potential issue”, never “wrong”
A checker can flag that a value doesn't match a common pattern; it cannot know whether that value is actually incorrect for your use case. A phone-number-shaped column that's really a free-text notes field will trip a “possible identifier duplication” or format check without being wrong in any real sense. That's why a genuine data-quality tool says “potential issue detected”, not “invalid” — the language reflects a real limitation, not excessive caution.
Format checks should be majority-vote, not name-based
Deciding a column is “email-like” by its header name (anything containing “email”) is fragile: a column named contact might hold emails, and a column named email_verified holds a boolean. A sturdier approach looks at the actual values — once most of a column's values already look like an email, the minority that doesn't becomes the finding. No network request is made to verify an email or URL actually resolves; that would send your data to a third party for no real benefit.
No score, on purpose
A single “data quality score” out of 100 flattens ten unrelated findings — of very different severity and relevance to your actual use — into one number that hides more than it reveals. A list of specific, explained findings is more useful and more honest than a score that implies a precision the underlying checks don't have.
Where to start
Run a CSV Data Quality Analyzer against a real file: every check runs and is reported, including the ones that found nothing, so “checked, found nothing” is never confused with “not checked at all.”
Try it: CSV Data Quality Analyzer
Detect potential data problems in a CSV, each with severity, count, explanation and a suggested action.
Related reading
- What Is Data Profiling?What profiling actually computes, and how it differs from a data-quality check.
- How to Find Duplicate Rows in a CSV FileWhy sorting doesn't find duplicates, and where duplicate detection stops working at scale.
- How to Find Missing Values in a CSV FileNULL, an empty string and a whitespace-only value are three different things. Here's why it matters.