Aglet

Investigate duplicate product results with identity evidence

An investigation should explain whether repeated rows are duplicate documents, legitimate variants, or presentation choices that look alike. Trace representative records through indexing and rendering, compare variant attributes, and replay queries under different sorts without assuming identical titles mean identical products.

Build a useful investigation brief

  1. Build the identity matrix

    List parent and variant identifiers, SKU, attributes, title, image, index source, category, sort, and destination for each row. Include one confirmed duplicate and one meaningful variant. Preserve source references instead of copying private catalog payloads.

  2. Trace the first merge

    Compare source records, index documents, grouping logic, result limit, and row template. Change one query or sort condition at a time. Record whether identity changes, a variant disappears, or only the visible label makes two distinct records appear alike.

  3. Write the grouping brief

    State the identity boundary, affected query contexts, preserved choice fields, and competing explanations. Recommend one identity experiment with an explicit preservation pass condition. Keep canonical-data, index, and rendering findings separate so each owner receives a tractable question.

What to carry forward

The investigation is complete when representative rows can be followed from canonical identity to visible choice, or the first unknown boundary is named. Stop with one grouping or rendering experiment. Do not collapse rows merely because a title or image is shared.

Technical background: Digital.gov guidance.

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