Closed namurphy closed 1 year ago
@namurphy The coming decadal is a good point! I think it would be really good to have a way to cite PyHC in general.
We're getting a ROR ID instead of a DOI. It's a human-led process, not automated, so we're tracking the process here: https://github.com/ror-community/ror-updates/issues/1513
@sapols just announced on the mailing list that the ROR ID for PyHC is now: https://ror.org/012prn105
We still need to add it to the website, I think.
@namurphy 100% agree. I’m on holiday though so it’ll happen after the new year. 👍
@sapols can we go ahead and close this ticket?
According to the DOI FAQ, it's possible to assign a DOI to "any entity — physical, digital or abstract — that you wish to identify". We could perhaps assign a DOI to the Python in Heliophysics Community itself! That way, we'd be able to cite PyHC directly, instead of citing an article or a website as a proxy to PyHC. Were we to do that, we would then want to add the DOI to the website alongside citation instructions. This would be particularly useful to do in the next few weeks if we wanted to be able to cite PyHC directly in heliophysics decadal papers which are due in mid-August.
I'm not sure how to go about assigning a DOI to things, but we did include a few citations to funding agencies in PlasmaPy's CodeMeta file as examples.