News:Bioconductor packages now each have a DOI.
0
8
Entering edit mode
@sean-davis-490
Last seen 6 weeks ago
United States

DOIs are available for Bioconductor packages, one per package (no versions). All are of the form:

doi:10.18129/B9.bioc.PACKAGENAME

These DOIs resolve to the package landing page on Bioconductor.

https://doi.org/10.18129/B9.bioc.Biobase

The package names are case-insensitive. Feedback, ideas for how best to leverage them, and comments are welcome. 

doi citation News • 1.6k views
ADD COMMENT
3
Entering edit mode

The DOI have been added to the top of the package landing pages if the DOI has been created. 

ADD REPLY
1
Entering edit mode

Does the DOI resolve to package short URL in the form http://bioconductor.org/packages/Biobase such that it can be used with packages which have been newly added to devel but haven't made it to release yet?

ADD REPLY
1
Entering edit mode

Yes, it resolves to https://bioconductor.org/packages/PACKAGENAME. Note the http(s), also.

ADD REPLY
0
Entering edit mode

Another one: when are the DOIs assigned, are they available as soon as the package gets accepted and its landing page is created?

ADD REPLY
0
Entering edit mode

I think that'll be the plan, but currently the process is manual (I believe?) and we're still working through the git transition.

ADD REPLY
1
Entering edit mode

Yes, the process is currently kicked off manually. In addition, new DOIs and changes to existing ones can take some time to propagate to resolvers. 

ADD REPLY
0
Entering edit mode

Great, I think it would be useful that the DOI is shown in the package landing page, ideally by fetching it from the package DESCRIPTION file, if such a field would be allowed.

ADD REPLY
0
Entering edit mode

The DOI doesn't need to be added to the vignette; they all share the base identifier, plus package name, so the DOI can be inferred from DESCRIPTION Title:

ADD REPLY

Login before adding your answer.

Traffic: 487 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6