In some future, if publishers would also take this serious, we will citation metrics for software like we have to research papers and increasingly for data (see also this brief idea). You can support this by assigning DOIs to software releases, e.g. using ZENODO. This list on our research group's webpage shows some of the software releases:
My advice for citation software thus goes a bit beyond what traditionally request for authors:
- cite the journal article(s) for the software that you use
- cite the specific software release version using ZENODO (or compatible) DOIs
This tweet gives some advice about citing software, triggering this blog post:
Citations inside softwareShould you cite software? Most probably yes! #collabw16 https://t.co/rol6KT0vhW pic.twitter.com/Xk4o8UwU51— dimazest (@dimazest) March 23, 2016
Daniel Katz takes a step further and asked how we should add citations inside software. After all, software reuses knowledge too, stands on algorithmic shoulders, and this can be a lot. This is something I can relate to a lot: if you write a cheminformatics software library, you use a ton of algorithms, all that are written up somewhere. Joerg Wegner did this too in his JOELib, and we adopted this idea for the Chemistry Development Kit.
So, the output looks something like:
(Yes, I spot the missing page information. But rather than missing information, it's more that this was an online only journal, and the renderer cannot handle it well. BTW, here you can find this paper; it was my first first author paper.)
However, at a Java source code level it looks quite different:
The build process is taking advantage of the JavaDoc taglet API and uses a BibTeXML file with the literature details. The taglet renders it to full HTML as we saw above.
> doi bridgedb
This will open the webpage of the cited article (which sometimes opens in Bioclipse, sometimes in an external browser, depending on how it is configured).
At a source code level, this looks like:
So, here are my few cents. Software citation is important!