[Epic] Citable & reproducible dataset #237
Labels
No labels
area: build
area: ci
area: compare
area: data
area: engine
area: model
area: provenance
area: rite
area: validation
backport
blocked
breaking
confirmed
dependencies
duplicate
epic
github_actions
invalid
needs-info
needs-triage
php
priority: high
priority: low
priority: medium
regression
type: bug
type: chore
type: correction
type: docs
type: enhancement
type: feature
type: fix
type: perf
type: refactor
type: security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Directorium/Core#237
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Make the dataset something scholars and other engines can cite and verify. Hardens deterministic generation (#40) into an enforced gate and ships a versioned, checksummed, DOI-bearing artifact. Done when a tagged release produces a byte-reproducible, citable CC0 dataset.
Epic — child issues are tracked as sub-issues.
Epic complete — all three children merged in PR #473. The CC0 corpus is now a citable, verifiable product: an enforced integrity gate (verify.mjs: determinism + freshness + integrity), a versioned checksummed release artifact (deterministic tarball + SHA256SUMS covering the whole archive + release-metadata.json, attached on each release-please release), and DOI archival prep (.zenodo.json + CITATION.cff kept current + docs/citable-dataset.md). Zenodo enablement is the documented one-time maintainer step.