GitHub Release to Zenodo DOI

说明与用途

验证并确认 GitHub 发行版与 Zenodo 存档元数据的完整性和一致性，包括 DOI 版本、许可证以及 CITATION.cff 和 .zenodo.json 文件，以实现可靠引用和可重复性。

问题

Ensuring a GitHub release is accurately archived, cited, and reproducible via Zenodo DOI, while maintaining metadata consistency and license clarity.

结果

A reproducible receipt confirming that the GitHub release, archived ZIP, and DOI metadata are accurate and consistent, enabling reliable citation and future reproducibility.

工作流

• 1. Identify objects: GitHub release tag, commit SHA, Zenodo record ID, version DOI, concept DOI.
• 2. Download Zenodo ZIP and compute MD5; compare with archived checksum.
• 3. Extract and compare files (CITATION.cff, .zenodo.json, license, README) against Git commit byte‑by‑byte.
• 4. Validate JSON syntax and CFF schema; ensure fields match intended citation.
• 5. Confirm Zenodo record metadata (upload_type, access_right, license) aligns with repository files.
• 6. Record all identifiers and verification dates in a receipt.
• 7. Document any missing assets, private data, or license inconsistencies for future fixes.

证据

The public Zenodo record contained one ZIP file of 133,258 bytes. Its advertised MD5 checksum matched the downloaded archive.

来源

The four citation and license files inside that ZIP also matched their counterparts at the pinned Git commit byte for byte.

来源

Zenodo’s GitHub integration uses .zenodo.json and ignores CITATION.cff when both exist.

来源