Open dataset collaboration / BAFU / UVEK
Make the dataset better.
Together.
Reproduce the import. Bring partner evidence and hackathon ideas into testable contributions. Build shared understanding, then return actionable recommendations to BAFU.
- 01Canonical import
- 02Partner contributions
- 03Application & testing
- 04Reviewed consensus
- 05Recommendations to BAFU
A shared place to work
Keep the evidence connected.
A finding about the source data, an importer defect and a new scenario need different evidence. Keep the original reproducible, apply contributions in separate candidates, and make every claim reviewable.
Start from a known baseline
Pin the release, source hashes, background and mappings. Understand what the import transforms before comparing results.
Import & use →Findings with a traceable source
Connect observations to dataset identities, release files and the discussion where contributors can reproduce them.
Explore the findings →Test the contribution's claim
Account for changed exchanges, check characterization, and compare equivalent scopes before seeking consensus.
Evidence & testing →Help improve BAFU / UVEK.
Bring a reproducible observation, a model or an application test. A proposal becomes consensus only after the evidence and reviewer decisions are recorded.
Work in progress
Contributions under review
C001 · Validate the hackathon copied-process layer before representation or forecasting recommendations
proposed2 / 5 required checks recorded as passed · 0 recorded approvals
Open the contribution record ↗C002 · Integrate the BAFU mapping work with Chris Mutel and reproduce method-specific results
proposed2 / 7 required checks recorded as passed · 0 recorded approvals
Open the contribution record ↗Importer fixes and application checks are tracked in issues and pull requests. Candidate method reproduction and community review remain open.