Search — Domain-Control Data-Gap Analysis
Scoping of the global Search screen. Documentation only; no presentation work.
Search (4951:11891)
Headline — client-side, no backend gap. A search input (
Master Form Field) + a
typeahead result list (rows of Master Form Field). No dedicated global-search endpoint or VM exists in
the codebase, so search runs client-side over already-loaded data (documents, menu/nav, airlines,
content). Work is presentation only. Confirm: the searched corpus, and whether a server search is
needed if that corpus outgrows what's loaded on device.
1 · Screen & controls
- Search input (
Master Form Fieldwith search icon + clear) over the keyboard. - Typeahead results — up to ~10
Master Form Fieldrows; mixed entities (e.g. tools like "DART", airlines like "Air Inuit", content terms).
2 · Data-source mapping
| Element | Data | Source | Status |
|---|---|---|---|
| Query | typed text | client form state | client |
| Results | matching entities (documents · nav · airlines · content) | client-side filter over loaded data (DocumentItem list, MenuItem, KCM airlines, …) | client |
| Result → navigation | route / document / detail | existing per-entity navigation | mapped |
3 · Confirm items
| # | Item | Question |
|---|---|---|
| 1 | Search corpus | Which data sets does global search span (documents, nav, airlines, KCM, content)? Defines the client index to build. |
| 2 | Server vs client | Client-side is fine for the bounded reference data loaded today. If the corpus grows (full content/document body), confirm whether a server search endpoint is wanted. |
4 · Summary
- Backend data gaps: none — search is client-side over loaded data; results reuse existing per-entity navigation.
- Confirm: search corpus/scope · server-search need at scale.
- Presentation backlog: search input + result rows (
Master Form Fieldvariants).