QuantEcon / QuantEcon/QuantEcon.py
MAINT: Archive releases on Zenodo and point CITATION.cff at the concept DOI
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.4k
- Forks
- 2.3k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 3
Description
Problem
CITATION.cff gives 10.5281/zenodo.10345102 as the software DOI. DataCite records that DOI as the archive of v0.7.1, issued 2023-12-11, and it is the archive DOI that JOSS recorded for the paper. Its concept DOI, 10.5281/zenodo.10345101, has exactly one version under it, so Zenodo has archived nothing since v0.7.1. Nine releases have shipped since then (v0.8.0 through v0.11.4) and none of them has a citable DOI. The file also carries no version or date-released.
The preferred-citation block (the JOSS article, 10.21105/joss.05585) is correct and matches the README entry after #864. This issue is only about the software DOI and the release process behind it.
Proposed change
- Enable the GitHub–Zenodo integration for this repository so every GitHub release is archived automatically as a new version under concept
10.5281/zenodo.10345101. This is a one-time setting that needs an organisation admin with a Zenodo login. - Change the top-level
doiinCITATION.cffto the concept DOI, so it always resolves to the latest archived version rather than the December 2023 snapshot. - Add
versionanddate-releasedtoCITATION.cff, and add the step "updateversionanddate-releasedinCITATION.cff" to the release procedure indocs/source/contributing.rst, or automate it in the publish workflow. - Optionally add
repository-code,urlandlicense, which GitHub's "Cite this repository" panel uses.
Acceptance criteria
- A Zenodo version record exists for the next release, under concept
10.5281/zenodo.10345101 - The top-level
doiinCITATION.cffis the concept DOI, andversionanddate-releasedmatch the latest tag - The release procedure names the
CITATION.cffupdate step
Related: #885 covers the docs toolchain; this is a follow-up from the #903 audit and the #864 review.
Facts verified against the DataCite API on 2026-09-10.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing CITATION.cff and the release procedure in docs/source/contributing.rst, then check the repository’s GitHub–Zenodo integration and concept DOI settings. Update the citation metadata and release instructions so the next release is archived under the concept DOI and its version and date match the latest tag; verify the next Zenodo version record.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100