PolicyEngine / PolicyEngine/chronicle

Add native Opgroeien Groeipakket caseload and expenditure facts

Open
#217 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
0
Forks
1
Avg merge
11h 48m
Merged PRs (30d)
45

Description

Refs #69.

Source gap

The current opgroeien-groeipakket-caseload-2025 package is a curated extract
of heterogeneous headline figures. It does not pin a native publisher export,
does not include expenditure, and labels the whole administrative scope as
NUTS BE2 without publisher-byte evidence that every row has that geography.

Opgroeien's official Cijfers op maat page embeds separate Power BI reports
for Groeipakket caseload and budget/expenditure. The current execution
environment cannot retrieve their native data exports. Rendered dashboard
cards, screenshots, accessibility text, and manual transcription are not
acceptable Chronicle artifacts.

Deterministic handoff

Use the two Opgroeien entries in
FETCH-MANIFEST-BELGIUM-PUBLIC-FACTS.json:

  • official landing page:
    https://www.opgroeien.be/kennis/cijfers-en-onderzoek/groeipakket/cijfers-op-maat
  • caseload report ID and exact native-export procedure recorded in the handoff;
  • expenditure report ID and exact native-export procedure recorded in the
    handoff.

Acceptance criteria

  • Pin unchanged native publisher export bytes with URL, SHA-256, size, report
    vintage/update timestamp, visual name, active filters, headers, and
    content-addressed raw-storage pointer.
  • Preserve each publisher reference period, recipient unit, component,
    currency/scale, and administrative/geographic scope exactly.
  • Add post-2019 caseload and expenditure facts only for cells that resolve from
    the pinned export. Do not force administrative coverage to BE2 without
    evidence in the export.
  • Do not calculate annual totals, per-recipient amounts, reconciliations,
    imputed periods, take-up, or model bindings.
  • Run validate-package, source-cell preservation, fact-load,
    consumer-artifact, raw-facts-boundary, ruff, and git diff --check checks.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the two Opgroeien entries in FETCH-MANIFEST-BELGIUM-PUBLIC-FACTS.json and follow their recorded native-export procedures, starting from the official Cijfers op maat page. Done means pinned export bytes and preserved source cells are added only where resolved, with the listed validation, fact-load, consumer-artifact, raw-facts-boundary, ruff, and git diff --check checks passing.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.