docs(c-series): wire the Zenodo DOI through every citing record - #122
Merged
Conversation
10.5281/zenodo.22167996, deposit version c-series-v1, verified to resolve to
records/22167996 before being embedded.
The load-bearing one is `Encoding_Protocol_v0_2.md`'s Validation Record. It
cited `credenza/docs/donetest/...` paths that resolve for NOBODY outside this
project — the escalation the supplement was published to close, still open in
the protocol's own prose. It now points at `studies/c-series/` and the DOI, and
carries the `uofa verify` invocation inline so a reader can check a package
without leaving the page.
The ledger's §4.6 venue line replaces its placeholder ("a Zenodo deposit ... is
minted from these same bytes") with the minted DOI. The supplement README states
the split: cite the DOI in a manuscript, cite the directory to run the checks.
**Flagged, not fixed:** the Zenodo record's title reads "Unit of Assurance
(UoFA) Specification", inherited from CITATION.cff rather than the release
title, so the DOI reads in a bibliography as a citation of the spec rather than
of the data supplement. That is a record-metadata edit on Zenodo and a repo
identity question in CITATION.cff — both the author's, not this commit's.
…r cites The deposit minted two: 10.5281/zenodo.22167996 is the VERSION DOI (this release, these bytes) and 10.5281/zenodo.22167995 is the CONCEPT DOI (always the latest version). Only the first was wired in. The distinction is load-bearing for a results chapter. A version DOI cannot move under a reference; a concept DOI can, and would silently repoint a citation at different bytes the day a c-series-v2 is cut. The records now say which to cite and why, rather than leaving a reader to pick.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DOI: https://doi.org/10.5281/zenodo.22167996 — deposit version
c-series-v1, verified to resolve tozenodo.org/records/22167996before being embedded anywhere.Three records updated
docs/Encoding_Protocol_v0_2.mdcredenza/docs/donetest/...paths that resolve for nobody outside the project. Now points atstudies/c-series/and the DOI, with theuofa verifyinvocation inlinestudies/ch4_numbers/LEDGER.md§4.6studies/c-series/README.mdThe protocol's Validation Record is the one that mattered. The supplement was published specifically to close the escalation that outside readers couldn't resolve the C-series citations — and until this commit, the protocol's own prose still stranded them.
Flagged, not fixed
The Zenodo record's title reads "Unit of Assurance (UoFA) Specification", inherited from
CITATION.cffrather than the release title. In a bibliography that DOI will read as a citation of the specification rather than the data supplement.That's a record-metadata edit on Zenodo, plus a
CITATION.cffidentity question that will recur on every future deposit from this repo. Both are author decisions, so neither is in this commit.Verification
3421 passed, 14 skipped. Documentation-only.