Deposit on Zenodo to obtain a citable DOI

[AlexisJanin]

Why

A Zenodo DOI makes ClinicalScope formally citable in academic work with a stable, versioned identifier. It is also the input that fills the doi: field in CITATION.cff and the BibTeX block in README.md.

Blocked by

• Choose and add a LICENSE file #38 — a LICENSE file is required before Zenodo will issue a DOI
• Tag and publish v1.0.0 public release #34 — should coincide with the v1.0.0 GitHub release (Zenodo snapshots a release automatically)

Steps

1. Go to zenodo.org and log in with your GitHub account
2. Under GitHub → find larib-data/clinical-scope and flip the toggle to On
3. Create the v1.0.0 GitHub release (see Tag and publish v1.0.0 public release #34) — Zenodo automatically archives it and mints a DOI
4. Copy the DOI (format: 10.5281/zenodo.XXXXXXX) and:
   • Uncomment and fill doi: in CITATION.cff
   • Uncomment and fill % doi in the README BibTeX block

Acceptance Criteria

• Zenodo integration enabled for this repo
• Zenodo record created and publicly visible
• CITATION.cff doi: field filled
• README BibTeX doi placeholder replaced with real value

[AlexisJanin]

Done — Zenodo DOI wired in

The repo is enabled in Zenodo's GitHub integration and a public record exists. Zenodo issues two DOIs; both are now documented here for the record:

DOI	Type	Behaviour	Where it's used
10.5281/zenodo.20830140	Concept / stable	Always resolves to the latest release	Badge + all citations
10.5281/zenodo.20830141	Version	Pins the current archived snapshot	(reproducibility only — not referenced in repo)

We deliberately reference the concept (stable) DOI everywhere, so it always points at the newest release and never needs editing per version.

Acceptance criteria

• Zenodo integration enabled for this repo
• Zenodo record created and publicly visible
• CITATION.cff doi: field filled → 10.5281/zenodo.20830140
• README BibTeX doi placeholder replaced → 10.5281/zenodo.20830140

Also done (beyond original scope)

• Added a DOI badge to the README header (Zenodo's repo-ID badge, which auto-tracks the latest release)
• Added DOI = "https://doi.org/10.5281/zenodo.20830140" to [project.urls] in pyproject.toml (surfaces on the PyPI sidebar from the next release)
• Documented the Zenodo flow in docs/RELEASING.md so future releases need no manual DOI work

Landed in commit 55939e3 (badge + citation + pyproject URL).

Note on the current record

The Zenodo record presently archives the 0.4.2 dry-run deposit. Publishing the v1.0.0 GitHub release (#34) will auto-mint a new version DOI under the same concept DOI — the badge and citations require no change. The version DOI in the table above will be superseded by the 1.0.0 one at that point; the concept DOI stays constant.

Ready to close.