[R-pkg-devel] DOI for archived package?

Jeff Newmiller jdnewm|| @end|ng |rom dcn@d@v|@@c@@u@
Fri Sep 11 03:14:39 CEST 2020

If your article is published with a DOI and read by anyone actually interested in it then it will be likely be accessed, so "never" seems rather pessimistic of you. You could simply not argue with your editor and acquiesce.

On September 10, 2020 9:14:12 AM PDT, "Kevin R. Coombes" <kevin.r.coombes using gmail.com> wrote:
>I am in the process of submitting a "workflow" article about an R 
>package (which is onCRAN) to F1000Research. The associate editor that I
>am dealing with wants a "DOI" for the source code of the package being 
>described in the manuscript.  I have already explained that CRAN 
>archives all versions of packages, and I sent him the URL to the
>page for the package, However, he still seems to believe that a DOI 
>needs to be assigned by some site like Zenodo.
>I haven't yet responded by pointing out that CRAN has been archiving
>versions of packages since at least the year 2000, it has mirrors all 
>over the world, and the URL/URI used here is likely to be far more 
>permanent than the DOI from Zenodo. Nor have I pointed out that there 
>are more than 15,000 packages at CRAN, nor that not a single R user 
>would ever think to go look on Zenodo for an R package.
>Does anyone have other suggestions for how to respond? (I know;  I
>just put the [expletive] thing into Zenodo and move on, but creating a 
>permanent identifier for something that will *never *be accessed just 
>seems stupid.)
>   Kevin
>	[[alternative HTML version deleted]]
>R-package-devel using r-project.org mailing list

Sent from my phone. Please excuse my brevity.

More information about the R-package-devel mailing list