Aglet

Triage category and global search boundaries before changing scope

Category browsing and global search may share a field while making different promises. Triage the boundary from route to result. Capture breadcrumb, category path, phrase, filters, facets, and returned types so an expected exclusion is not mistaken for missing relevance.

Establish what is happening

  1. Capture the entry context

    Record route, breadcrumb, category path, query text, selected filters, sort, and result types before searching. Include a category page and global search path. Keep the same phrase where possible so scope differences remain visible.

  2. Compare scope promises

    Write what strict category scope, inclusive category filtering, and global search each imply. Compare returned products, subcategories, facets, and labels. Note whether the interface explains missing results or makes different scope rules appear identical.

  3. Set the route boundary

    State which path owns the scope, what a phrase means when empty, and how a person broadens the search. Preserve a control where expected results appear. Stop when another reviewer can explain each inclusion and exclusion from the route contract.

What to carry forward

The triage output is a scope contract linking route, breadcrumb, phrase, filter, and result type. Stop when category and global boundaries are reproducible. If the product has not decided whether a category is strict or inclusive, route that policy question before changing retrieval.

Technical background: Adobe developer documentation.

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