You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
26 pathways are still on metadata v1 and don't appear on the site #978
Found while migrating the timeseries to v2 (#974).
The problem
The app loads only v2 metadata (src/data/pathwayMetadata.ts). A file still on pathwayMetadata.v1.json is skipped silently; the dev server only logs a count. 26 pathways are in that state, so they're missing from search, cards and comparison:
TransitionZero and UTS-ISF also have timeseries, which #974 moved to v2, so their benchmark data is ready but their pathways don't appear.
Options
Codemod:scripts/codemod-v1-to-v2.ts (from v2 schema + data codemod #858). It is mechanical, but it scaffolds coreDrivers as null and scopes every key feature at the widest level, so the result needs review.
Workbook import: add the pathways to pathway_data_prepared.xlsx and import them with scripts/import-pathway-data.ts, like the 24 already imported. This gives authored v2 content (scoped key features, core drivers, dependencies, data availability) but is authoring work.
A codemod first, with the workbook replacing it later, would make the pathways visible again quickly. That's the same approach #974 took for timeseries. Either way, npm run schema:check will catch problems: scoped geography must be declared, and NGFS still has the empty region memberships tracked in #801.
Found while migrating the timeseries to v2 (#974).
The problem
The app loads only v2 metadata (
src/data/pathwayMetadata.ts). A file still onpathwayMetadata.v1.jsonis skipped silently; the dev server only logs a count. 26 pathways are in that state, so they're missing from search, cards and comparison:TransitionZero and UTS-ISF also have timeseries, which #974 moved to v2, so their benchmark data is ready but their pathways don't appear.
Options
scripts/codemod-v1-to-v2.ts(from v2 schema + data codemod #858). It is mechanical, but it scaffoldscoreDriversas null and scopes every key feature at the widest level, so the result needs review.pathway_data_prepared.xlsxand import them withscripts/import-pathway-data.ts, like the 24 already imported. This gives authored v2 content (scoped key features, core drivers, dependencies, data availability) but is authoring work.A codemod first, with the workbook replacing it later, would make the pathways visible again quickly. That's the same approach #974 took for timeseries. Either way,
npm run schema:checkwill catch problems: scoped geography must be declared, and NGFS still has the empty region memberships tracked in #801.Related: #858, #860, #915.