Aglet

Verify duplicate product grouping across result contexts

Verification should show that grouping reduces repeated rows while retaining the differences needed to choose a product. Test confirmed duplicates and legitimate variants in the contexts where ordering changes. Inspect row labels and destinations so a compact result does not conceal a missing choice.

Check whether the outcome improved

  1. Check confirmed duplicates

    Run a query with repeated identity and confirm one useful representation remains, with count or variant context if promised. Compare destination and selection behavior. Record the query and sort so result-limit effects remain visible.

  2. Check meaningful variants

    Use products that differ in size, color, price, or availability. Confirm those choices remain understandable and selectable. Test category and search paths because a grouping rule that is safe in one view may hide context in another.

  3. Review the result contract

    Inspect labels, images, sort, pagination, narrow layout, and direct links. State tested identity types and omitted catalog cases. Leave a partial pass where canonical identity or variant availability was not directly verified.

What to carry forward

Verification passes when true duplicates are reduced, meaningful variants remain selectable, and labels and destinations preserve identity. If one catalog or sort context is untested, document it. A shorter list is not a pass if the choice a person needed has disappeared.

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