Generate DOI numbers for each release
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 21
- Forks
- 11
- Avg merge
- 12h 5m
- Merged PRs (30d)
- 24
Description
The Zenodo project makes it easy to generate DOI numbers for each GitHub release, and DOI numbers make it easy for researchers to cite a specific version of MiCall.
- configure Zenodo to generate the DOI numbers
- add current DOI number to BaseSpace description
- add some DOI information to small print on resistance reports (may have problems updating the DOI before tagging the release, but look at the feature for reserving a DOI)
- add current DOI number to project README
- update release instructions to include DOI updates to the items listed above
Contributor guide
No contributing guide indexed for this repository
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 with the unchecked checklist items: the BaseSpace description, resistance reports, project README, and release instructions. Review how DOI information is currently handled and the release process, then update each listed location and document the DOI update steps so all checklist items are complete.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100