Stephan Janosch, May 8, 2017
This post will explain how you can assign a DOI to a piece of software within the Max Planck Society (MPG). I need to restrict the scope to the MPG, because the access to the DOI service of the Max Planck Digital Library is restricted. If you plan to release on Github, then the guide ‘Making Your Code Citable’ helps you along.
Next you head over to https://doi.mpdl.mpg.de/request-doi/ and fill out and submit the form.
The MPDL did choose an request confirmation via email. So will receive an email like that which you return to DOI helpdesk. Then you wait for the confirmation to take place.
your eMail address was used to request a DOI name via the Max Planck Digital Library (MPDL). To confirm that a DOI name should be registered on your behalf for the content item described below, please return the complete eMail to email@example.com.
In addition, you confirm that all information provided is correct and permit the MPDL to store the data locally. You also agree that the location URL and bibliographic metadata will be transfered to the German National Library of Science and Technology (TIB) in order to register the DOI name. The TIB receives the metadata under the conditions of the Creative Commons CC0 1.0 Universal Public Domain Dedication.
Best regards, your DOI helpdesk in the MPDL
After a while, you will receive the DOI with a nice hand-craftet mail. Done.
Lieber Herr Janosch,
vielen Dank fuer Ihre DOI-Anfrage. Fuer das Software-Paket wurde soeben die DOI 10.17617/1.46 vergeben und in wenigen Minuten sollte https://doi.org/10.17617/1.46 auf die gemeldete URL umleiten.
With a few clicks more you can link your freshly minted DOI to your ORCID record.
So open your ORCID profile and hit ‘Add Works’ -> ‘Search & Link’ -> ‘DataCite’
After you allowed the DataCite to connect to your ORCID profile, you can ‘Search’ for your works.
Two clicks more on ‘Add to ORCID record’ and ‘OK’ completes the process.
Software appears in different manifestations. You could refer to it as a specific release of your code (e.g. version 0.3 of the plugin) or as software engineering project. If you are interested in the citation count you want to have only one DOI for your software. Opposite to this, you want to have a DOI for each release of your code. This ensures that protocols or workflows cite the exact version used in order to prevent reproducibility issues.
The DataCite Metadata Schema (version 4 pdf) knows some very handy relation types like:
- IsNewVersionOf - IsPreviousVersionOf - IsPartOf - HasPart
It looks like, that Zenodo makes use of these, as this example shows. I will try to speak with Martin Fenner (DataCite), who is giving a talk with the topic ‘Workflows for assigning and tracking DOIs for scientific software’ this wednesday, to get a better idea about metadate for software.
According to the MPDL personell there is no interface right now for changing the landing page URL. Their advice was sending an email to the DOI helpdesk and submit your changes that way.
As you can see, assigning a DOI to a piece of software is not very hard. The easy interface provided by the MPDL helps a lot, but maybe an expert version of it is more appropriate for software? And it takes a bit patience because there is some waiting involved (explaination?). But the process in general is straight forward.
Feel free to discuss this topic at our communication channels (mailing list and/or slack). In case you have the desperate need to document the DOI assigning process for your own research organisation then head along and copy this post and push a pull request to our website repo. 😉