What are the duplicate status?

Understand what each status means for duplicate pairs in Delpha. Learn how Delpha handles auto merges, rejections, and steward validations.

Understanding Duplicate Pair Statuses in the Delpha Data Steward View

In the Duplicate Data Steward View, each duplicate pair has a score, status, and optionally a comment. These fields help you track the current state of the pair throughout the detection, review, and merge process.

This article explains what each status means, how it’s assigned, and how it affects the pair's lifecycle in Delpha.

Key Concepts

• Score: A confidence score (0–100) showing how similar the two records are.

• Status: Indicates the current action or required action for the duplicate pair.

• Comment: Additional context, often used when a filtering rule or error applies.

• Processed: A Boolean field (True/False) indicating whether the pair has been finalized.

Unprocessed Duplicate Pairs (Processed = False)

These pairs are still under review and may change if monitored fields are updated.

Status	Meaning
Potential	Default state. The pair can be reviewed via the Data Steward view or Delpha bot.
Auto No	Excluded by a Filtering Rule with Discard: true. Can only be reviewed in the Data Steward view.
Auto Yes	Score exceeds the Auto Merge Threshold. Will be auto-merged during the next scheduled merge job.
Steward Yes	Validated as a true duplicate by a Data Steward. Will be merged during the next merge batch (also available in the bot).
Failed	Merge attempt failed. Check the Comment field for the root cause.

---

Processed Duplicate Pairs (Processed = True)

These pairs have been finalized. The status will not update even if fields change.

Status	Meaning
User Yes	Merged manually via the Score Meter Duplicate Editor.
User No	Rejected via the Score Meter Duplicate Editor. This pair will never be proposed again.
Auto Yes	Merged automatically by Delpha based on the score threshold.
Steward Yes	Merged via the Data Steward view.
Auto No	The pair is automatically rejected because one member no longer exists. For example, consider pairs A–B, B–C, and A–C. If B–C is merged with B as the master, C is deleted. The A–C pair then becomes Auto No.
Steward No	Rejected via the Data Steward view. This pair will never be proposed again.

Important Notes

• Updates to monitored fields can change a pair’s status and score until processing occurs.

• When Processed is True, the pair is final. It is either merged or rejected.

---

Summary Table

Field	Description
Score	Match confidence (0–100)
Status	State of the duplicate pair (see tables above)
Comment	Filtering or merge failure info
Processed	True = final, False = under review