Hello maintainers,
Would this open guide be in scope for the Build Workflows section?
How to Publish a Source-Backed Historical CSV Archive
https://remo65588-boop.github.io/lottolens-ph-public-data/guides/publish-source-backed-csv-archive.html
It presents a reusable workflow for preserving and publishing dated tabular records with row-level provenance, field dictionaries, declared keys, reproducible duplicate/null/source/checksum checks, immutable versioned releases, coverage and missingness notes, licensing boundaries, correction paths, and logged-out public-release verification. The worked example is a Philippines public-draw archive, but the checklist is domain-independent and applies to historical event datasets.
I searched the current README and previous suggestions and did not find a close CSV provenance/checksum workflow duplicate. If it is in scope, I can submit one entry at the bottom of Build Workflows in the repository format; if not, no PR is needed.
Disclosure: this suggestion was drafted with AI assistance and manually checked against the current contribution guide and live resource.
Hello maintainers,
Would this open guide be in scope for the Build Workflows section?
How to Publish a Source-Backed Historical CSV Archive
https://remo65588-boop.github.io/lottolens-ph-public-data/guides/publish-source-backed-csv-archive.html
It presents a reusable workflow for preserving and publishing dated tabular records with row-level provenance, field dictionaries, declared keys, reproducible duplicate/null/source/checksum checks, immutable versioned releases, coverage and missingness notes, licensing boundaries, correction paths, and logged-out public-release verification. The worked example is a Philippines public-draw archive, but the checklist is domain-independent and applies to historical event datasets.
I searched the current README and previous suggestions and did not find a close CSV provenance/checksum workflow duplicate. If it is in scope, I can submit one entry at the bottom of Build Workflows in the repository format; if not, no PR is needed.
Disclosure: this suggestion was drafted with AI assistance and manually checked against the current contribution guide and live resource.