Updated Code DOI best practices (markdown)
authorTimo Heister <timo.heister@gmail.com>
Fri, 7 Apr 2017 15:46:13 +0000 (11:46 -0400)
committerTimo Heister <timo.heister@gmail.com>
Fri, 7 Apr 2017 15:46:13 +0000 (11:46 -0400)
Code-DOI-best-practices.md

index c3f21d563c6ec5a1c2015f318f03fa5ab56a4117..ecb41203f480b168fe3ca665b5456df93d781d6f 100644 (file)
@@ -1,6 +1,6 @@
 This note tries to give best practices for DOIs for deal.II tutorial and code gallery contributions.
 
-1. Create a DOI at zenodo.org with title "The deal.II tutorial step-XY: The Title" or "The deal.II code gallery: The Title":
+1. Create a DOI at https://zenodo.org with title "The deal.II tutorial step-XY: The Title" or "The deal.II code gallery: The Title":
    - Include the .cc, CMakeLists.txt, and all necessary parameter files
    - You can include a README.md which will be prominently displayed in the citation (example: https://doi.org/10.5281/zenodo.484156). This allows you to link to the current version of the tutorial and provide instructions and additional citations, etc..
    - Select type "Software" and provide keywords, description, etc.

In the beginning the Universe was created. This has made a lot of people very angry and has been widely regarded as a bad move.

Douglas Adams


Typeset in Trocchi and Trocchi Bold Sans Serif.