From Alex's review on #936:
Comparison page also needs the same geo/scope/context header as single view
#946 turned the detail page's context ribbon into scope filters. The comparison page was left out: it has no scope concept at all — three independent side-by-side badge lists, and a plot geography selector built from the raw union of every column's timeseries tokens.
What it needs
- A sticky header with one shared sector axis and one shared geography axis, structurally matching
PathwayContextRibbon.
- The axes have to be reconciled across N pathways. Sector is an intersection. Geography cannot be: tokens are publication-specific and resolve to an ISO set only against their own publication's
regions mapping.
- URL-backed scope state (
?sector=, ?geography=), seeded from the reader's search selection at navigation time so a shared link reproduces what the sender saw.
Why geography is not an intersection
Measured across the seven loadable v2 pathways:
| Pair |
Shared sectors |
Shared geography tokens |
| ACE × ACE (any two of four) |
4 |
1 — South East Asia |
| ACE × IEA (any pair) |
3 |
0 |
| IEA-APS × IEA-STEPS |
12 |
15 |
| IEA-APS/STEPS × IEA-NZE |
12 |
1 — Global |
Any cross-publisher comparison has no geography in common by name, so an intersection-only vocabulary would have been empty for most real pairs. Every declared token is offered instead, labelled by publisher, and each column resolves the shared choice for itself.
Related: #842 (the charts should size to their column), #859 (scope/fallback badges, incl. "apply the same treatment in the comparison view").
From Alex's review on #936:
#946 turned the detail page's context ribbon into scope filters. The comparison page was left out: it has no scope concept at all — three independent side-by-side badge lists, and a plot geography selector built from the raw union of every column's timeseries tokens.
What it needs
PathwayContextRibbon.regionsmapping.?sector=,?geography=), seeded from the reader's search selection at navigation time so a shared link reproduces what the sender saw.Why geography is not an intersection
Measured across the seven loadable v2 pathways:
South East AsiaGlobalAny cross-publisher comparison has no geography in common by name, so an intersection-only vocabulary would have been empty for most real pairs. Every declared token is offered instead, labelled by publisher, and each column resolves the shared choice for itself.
Related: #842 (the charts should size to their column), #859 (scope/fallback badges, incl. "apply the same treatment in the comparison view").