-
Notifications
You must be signed in to change notification settings - Fork 229
How to cite PyGMT #653
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
Comments
This was mentioned before by @liamtoney on Apr 2020 at https://forum.generic-mapping-tools.org/t/how-to-cite-pygmt/382, but that predates v0.1.0 (and hence no Zenodo DOI was available). I still think the GMT 6 paper needs to be cited regardless since that's the real engine, and people should refer to https://www.generic-mapping-tools.org/cite/ for that. That said, we could have a Bibtex entry on our main README.md page for this. For PyGMT v0.2.0, this is what I got from my Zotero's "Export to BibLaTeX" function:
Or if we use Zenodo's "Export to Bibtex" page at https://zenodo.org/record/4025418/export/hx:
Obviously, this would change for every version release, and also as new contributors from https://github.com/GenericMappingTools/pygmt/blob/master/AUTHORS.md are added. In the long term (i.e. for v1.0.0), we should look at making a JOSS paper or similar to make a stable citation. |
We could point people to the overall Zenodo DOI and instruct them on how to get the BibTeX and citation info from that. Otherwise we would have to remember to update the citation every time we make a release. I agree that we should think about a paper as we get closer to something "complete". We could go for JOSS (which is very little work but relatively unknown in geophysics) or a more popular journal in geoscience (G³ or the like). We have grant money that could pay for open-access fees so it shouldn't be a huge problem. But that would require a lot more effort for the paper and reviewers generally don't even look at the code... I opened #677 to discuss what we need for a first paper. |
Yes, we should point to the Zenodo DOI, but I think it's worth the effort to update a BibTeX citation on the main README page every release just to make it easy for users wanting to cite PyGMT. I just spent/wasted a whole day fixing 30+ citations for a paper and the last thing I want is to jump through a bunch of links just to get at the BibTeX/RIS metadata!! That said, I'll open up a Pull Request for this (unless anyone else wants to give this a go). |
Looks good to me. We just need to add it to the release checklist. |
I’m OK with that as well 👍🏽 |
Description of the problem
Searching for "PyGMT" in Google Scholar shows that there are already some papers citing/mentioning/acknowledging PyGMT. Here are the searching results: https://scholar.google.com/scholar?q=PyGMT&hl=en&as_sdt=0%2C23&as_ylo=2017&as_yhi=
From the searching results, you'll see that people are citing PyGMT in various ways:
PyGMT should document the correct/recommended way for citation.
The text was updated successfully, but these errors were encountered: