Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mint DOIs for pyspedas (all versions) and each individual release #1037

Open
jameswilburlewis opened this issue Oct 10, 2024 · 0 comments
Open
Labels
Admin General PySPEDAS administrative tasks or issues Documentation Examples, notebooks, installation guides, webinars, etc

Comments

@jameswilburlewis
Copy link
Contributor

TBD: Find some guidance on best practices for minting DOIs for software. Also, how would we include the DOI for a specific release inside that release itself (e.g. in an "about" or "version" routine)? Since I think you don't get the DOI after uploading the files, and it's probably not good practice to modify the release after the DOI is minted....

@jameswilburlewis jameswilburlewis added Admin General PySPEDAS administrative tasks or issues Documentation Examples, notebooks, installation guides, webinars, etc labels Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Admin General PySPEDAS administrative tasks or issues Documentation Examples, notebooks, installation guides, webinars, etc
Projects
None yet
Development

No branches or pull requests

1 participant