Allowing a package to be cited

Any thoughts here on what are currently the best options to allow people to cite a package that you have created?

I know of

Zenodo

Pros
Easy and also stores the code.

Cons
Is mostly ignored by Google Scholar.

Preprint repository such as arXiv

Pros
Reasonably easy

Cons
Need to write a LaTeX document LaTeX, HTML or PDF document.

Peer-reviewed publication

Pros
Looks nice

Cons
Takes long

Book

Obvious pro’s and con’s. I mention this because, for example, ggplot2 does this.

EDIT: Related article happened to be posted on Slack just now by Mathieu Besançon: Software Must be Recognised as an Important Output of Scholarly Research | International Journal of Digital Curation.

EDIT2: There is also https://f1000research.com/

5 Likes

Can’t you just cite the Github repo?

1 Like

In our department, people who are editors and reviewers don’t like that. A software package appears more legitimate if it has a “real” publication.

1 Like

Shouldn’t the original question be changed to “Where to publish a paper about a software package?” then?

I would say that a short open source journal paper is a pretty good choice for this topic.
Available on google scholar, writing markdown is enough, and takes relatively short.
David Sanders gave a talk to introduce the journal of open source software.

6 Likes

There is an interesting discussion on and around this topic here:
http://www.ijdc.net/article/view/745
“Software Must be Recognised as an Important Output of Scholarly Research”

1 Like

JOSS? https://joss.theoj.org/
The LaTeX document required can be fairly brief.

3 Likes

Journal of Open Source Software (JOSS) has some benefits including

  • Relatively short review times
  • An academic journal
  • Indexed by Google Scholar
  • Interactive review process
  • Developer friendly, on GitHub
  • Markdown with LaTeX features
3 Likes

ArXiv accepts but does not require LaTeX. You can submit pdf or even html.

1 Like