Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

NULL_OR_BLANK Match

Changes how Zingg handles null and blank values in a field.

What NULL_OR_BLANK does

By default, most Zingg match types treat a null or blank value as automatically matching anything.

NULL_OR_BLANK adds a separate feature flagging whether both values were actually present, so the model can learn to discount matches that were really just two missing values.

Exception: NUMERIC does not follow the "null matches anything" default - a null paired with any value scores as a non-match under NUMERIC, the opposite of every other match type covered here.

Use NULL_OR_BLANK combined with another match type, in the matchType string with a comma-separated combination.

What NULL_OR_BLANK matches and what it does not

Value A

Value B

NULL_OR_BLANK feature

Notes

null

John Smith

0.0

One side null

[empty string]

John Smith

0.0

Empty string treated exactly like null

null

null

0.0

No distinction between one-sided and both-sided nulls

null

[empty string]

0.0

Null and blank are interchangeable

John Smith

John Smith

1.0

Both values present

There is no distinction between "both null" and "one null, one populated" - all four null/blank rows above score identically.

When to use NULL_OR_BLANK

Fields that are frequently null across source systems

Middle name, maiden name, suffix, secondary address line, company name on a personal record, any field that is commonly absent in some source systems but present in others.

Without NULL_OR_BLANK, a null middle name in one record, any middle name in another record will match. This is often not what you want - a null middle name should not help two records match.

Add NULL_OR_BLANK alongside FUZZY on these fields so the model can learn to treat nulls appropriately from your labeled examples.

When data quality varies significantly across source systems

If one source system reliably populates a field and another consistently leaves it blank, NULL_OR_BLANK prevents the blank-vs-populated pattern from inflating match scores across source system pairs.

When not to use NULL_OR_BLANK

As a standalone match type

On its own, NULL_OR_BLANK only contributes a "both present?" signal, with no similarity information - which isn't useful for distinguishing matches. Nothing currently validates or blocks this configuration, but it won't do anything meaningful by itself.

Always pair it with another match type: FUZZY, NULL_OR_BLANK or EXACT, NULL_OR_BLANK or PINCODE, NULL_OR_BLANK.

On fields where null means the same thing across all records

If a field is universally null across all records with no non-null values to contrast against, NULL_OR_BLANK adds nothing. Use DONT_USE for those fields instead.

Last updated

Was this helpful?