Aglet

Prioritize Duplicate Record Investigation

Prioritizing duplicates means choosing between preventing new repeats, correcting an inflated result, and clarifying whether similar records are truly distinct. Rank work by decision damage and recurrence, while giving identity ambiguity its own path. Use bounded counts and examples rather than treating every repeated row alike.

Decide where the work belongs

  1. Rank affected decisions

    List totals, balances, latest-state views, joins, exports, and operational workflows that change when suspected duplicates are grouped. Record the concrete difference and cohort. An exact repeat that inflates a key report may outrank a larger historical set that has no downstream effect.

  2. Assess recurrence and conflict

    Compare repeat frequency over time and across sources, then check whether copies disagree on status, amounts, ownership, or timestamps. Prioritize forward prevention when new conflicting records continue to arrive. Put ambiguous identity groups behind clarification before any irreversible consolidation.

  3. Choose a bounded action

    Select investigate, prevent future repeats, correct a named report, review a conflict cohort, or monitor. Include the grouping rule, comparison query, owner, and review trigger. Keep a separate queue for historical records whose identity evidence is too weak for automated handling.

What to carry forward

Return a ranked queue that separates exact repeats, conflicting copies, and legitimate repeated events. Each item should name the affected decision, recurrence evidence, identity confidence, owner, and bounded next action. Mark any priority as provisional when the logical identity contract is not yet agreed.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow