Repository navigation

Store the metadata v3 reads in the v2 catalog from PolicyEngine.py's public records (catalog format 2) - #4023

Draft

anth-volk wants to merge 8 commits into

v2plan/1f-123-region-reference-filesfrom

v2plan/1f-115-catalog-metadata-fields

Draft

Store the metadata v3 reads in the v2 catalog from PolicyEngine.py's public records (catalog format 2)#4023
anth-volk wants to merge 8 commits into
v2plan/1f-123-region-reference-filesfrom
v2plan/1f-115-catalog-metadata-fields

Commits on Oct 22, 2026
- Add nullable catalog format 2 columns for v3's metadata
  
  anth-volk
  and
  claude
  committed
  c1608c0
- Extract v3's metadata from PolicyEngine.py's public records as catalog format 2
  
  anth-volk
  and
  claude
  committed
  98ce648
- Store catalog format 2 fields when a catalog version is published
  
  anth-volk
  and
  claude
  committed
  41cead6
- Scope UK constituencies and local authorities by what the certified release provides
  
  anth-volk
  and
  claude
  committed
  739bbc1
- Name the missing catalog format 2 fields when PolicyEngine.py lacks them
  
  anth-volk
  and
  claude
  committed
  7e03529
- Compare enum label types in the metadata parity test
  
  anth-volk
  and
  claude
  committed
  0340aaf
- Test that enum labels and parameter paths round-trip through publication
  
  anth-volk
  and
  claude
  committed
  d20f743
- Type the catalog's entity and enum-value columns
  
  anth-volk
  and
  claude
  committed
  18d014a