Skip to content

docs: fix citation metadata and the broken weights-license link - #5

Merged
KalinNonchev merged 1 commit into
mainfrom
docs/citation-metadata-and-links
Aug 3, 2026
Merged

docs: fix citation metadata and the broken weights-license link#5
KalinNonchev merged 1 commit into
mainfrom
docs/citation-metadata-and-links

Conversation

@KalinNonchev

Copy link
Copy Markdown
Member

Why

CITATION.cff never validated against the CFF 1.2.0 schema, so anything that reads it — including GitHub's Cite this repository box — had nothing usable. Two violations, found with cffconvert:

  • year is not a valid top-level key; the schema expects date-released.
  • publisher must be an entity object, not a string — so "Cold Spring Harbor Laboratory Press" was invalid regardless of its content.

Separately, the README's weights-license link 404s, and neither citation file carried the preprint DOI.

What changed

CITATION.cff — fixes both schema violations, then adds the metadata citation and archival tooling expects: version, date-released (from the v1.0.0 tag), repository-code, the DOI under identifiers, keywords, abstract. license becomes PolyForm-Noncommercial-1.0.0 to match pyproject.toml; the previous CC-BY-NC-SA-4.0 is the weights license, a separate artifact, now noted in a comment.

README.md

  • [CC-BY-NC-SA-4.0](WEIGHTS_LICENSE)WEIGHTS_LICENSE.md. The old target does not exist, so the link 404s.
  • Three medrxiv.org/content/...v1 links → https://doi.org/10.64898/2026.06.19.26356060. The version-pinned URLs go stale at v2; the DOI always resolves to the current version.
  • BibTeX gains doi and url — it previously had no persistent identifier. Drops pages={2026--06}, a date fragment in a page field that renders as "pp. 2026–06". Publisher corrected to openRxiv; the 10.64898 prefix is openRxiv's, not CSHL's 10.1101. These oddities come from Google Scholar's stale medRxiv template.
  • RaetschR{\"a}tsch, matching CITATION.cff and Crossref.
  • PyPI added to Resources; it was previously reachable only via a badge.

Verification

  • CITATION.cff validates against cff-version 1.2.0 (cffconvert); APA and BibTeX render correctly.
  • All 8 relative links in the README resolve against the working tree.
  • Paper metadata cross-checked against Crossref: DOI 10.64898/2026.06.19.26356060, posted 2026-06-22, publisher openRxiv, author list matches.
  • Both changed external URLs return HTTP 200.

No code, packaging or CI changes.

🤖 Generated with Claude Code

CITATION.cff did not validate against the CFF 1.2.0 schema, so tools that
read it (including GitHub's "Cite this repository" box) had nothing usable:

- `year` is not a top-level key; `date-released` is.
- `publisher` must be an entity object, not a string.

Both are fixed and the file now validates with cffconvert. While there, add
the metadata that citation and archival tooling expects: version,
date-released (from the v1.0.0 tag), repository-code, the preprint DOI under
`identifiers`, keywords and an abstract. `license` becomes
PolyForm-Noncommercial-1.0.0 to match pyproject.toml -- the previous
CC-BY-NC-SA-4.0 is the *weights* license, which is a separate artifact.

README:

- `[CC-BY-NC-SA-4.0](WEIGHTS_LICENSE)` 404s; the file is WEIGHTS_LICENSE.md.
- The three medrxiv.org/...v1 links are version-pinned and go stale at v2.
  Point them at the DOI instead, which always resolves to the latest version.
- Add the DOI to the BibTeX entry, which had no persistent identifier at all.
  Drop `pages={2026--06}`, a date fragment in a page field that renders as
  "pp. 2026-06". Publisher is openRxiv, not Cold Spring Harbor Laboratory
  Press -- the 10.64898 prefix is openRxiv's. These oddities come from Google
  Scholar's stale medRxiv template.
- Escape the umlaut in Raetsch -> R{\"a}tsch, matching CITATION.cff and
  Crossref.
- Add PyPI to Resources; it was only reachable via a badge.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@KalinNonchev
KalinNonchev merged commit 8244769 into main Aug 3, 2026
7 checks passed
@KalinNonchev
KalinNonchev deleted the docs/citation-metadata-and-links branch August 3, 2026 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant