The document discusses establishing software as a recognized scientific achievement by creating missing links between software, data, and papers. It proposes making software a contribution to scientific journals, adopting common understanding and defined processes for software as a scientific achievement. It also suggests leveraging open access and open science platforms to share runnable code, documentation and reviews. Further, it addresses establishing software engineering best practices and processes in science to improve code quality and safeguard traceability.

1. Publication and citation of scientific software
with persistent identifiers
EGU General Assembly 2014, OSGeo Townhall Meeting, April 29, Vienna, Austria
Martin Hammitzsch, Helmholtz Centre Potsdam, GFZ German Research Centre for Geosciences
Peter Löwe, German National Library of Science and Technology / University Library Hannover (TIB/UB)
Jens Klump, Commonwealth Scientific and Industrial Research Organisation (CSIRO)
Dominik Reusser, Potsdam Institute for Climate Impact Research (PIK)
Bernadette Fritzsch, Alfred Wegener Institute, Helmholtz Centre for Polar and Marine Research (AWI)
Björn Brembs & Gernot Deinzer, University Regensburg
Roland Bertelmann, Helmholtz Centre Potsdam, GFZ German Research Centre for Geosciences, Library and Information Services
Heinz Pampel, Helmholtz Association, Helmholtz Open Access Coordination
Martin Fenner, Public Library of Science (PLoS)
Joachim Wächter, Helmholtz Centre Potsdam, GFZ German Research Centre for Geosciences
Image: http://www.slashgear.com/google-data-center-hd-photos-hit-where-the-internet-lives-gallery-17252451/

2. Establish the missing link
between software, data and papers.
papers
data
software
findings
Image: youtu.be/eYDjV7ajuMo, 1:52
crucialroleinscientificwork
rarelyseenpublishable
solutionslackresearchers’needs
inconflictwithprincipleof reproducibility alreadyprofessionallypublished
notstandardpractice
basedonrawdata&datafromanalysesandthusonsoftware

3. Make software recognised
as scientific achievement.
Image: http://justhappeneduponthis.wordpress.com/2012/08/25/megaphone-mercy/
contribution
journals
achievement
gap
partof solutionforquestionorproblem& independent
commonunderstanding
definedprocesses
acceptedmetrics
adoption
poorlyperceived&hardlymeasurable
notassessed&notvalued
…areoftenworkarounds
publicationsindesiredjournals…
directreleasenotpossibleasscientificpublication

4. Images:
http://juretriglav.si/3-simple-things-github-can-do-for-science/
https://osf.io/tvyxz/wiki/view/
http://figshare.com/blog/Working_with_Github_and_Mozilla_to_enable_Code_as_a_Research_Output_/117
Leverage open access
and open science.
code · re-use · repositories · scientific tradition
notwrittenforothers ·nointendedre-use·keptprivately&internally
happensinformally&anonymously·heavilypracticedinsciences·fewcontributeback
numberof platforms·scientificneedspartlyaddressed·unclearuse
runnablecode·sufficientdocumentation,sampledata,tests,comments·adequate&qualifiedreviews·learntowrite&releasecodeandsoftware

5. Establish software engineering
rules, best practices and processes in science.
Image: http://news.onlinenigeria.com/index.php?news=5748
scientific performance
additional work
software engineering
includessoftwareengineering
habitsarerarelypracticed
skillsseldompassedontofollowers
codedesign,versioncontrol,documentation,testing…
safeguardtraceability&re-use
adoptionof softwaredevelopmentlifecycleandrelatedprocesses
notcoveredinprimaryresearchtask
noincentivestoimprove&publishcode
softwareandcodequalityinfluenceresults
bettersoftware,betterresearch

6. Make software recognised as scientific achievement.
Leverage open access and open science.
Establish software engineering
Establish the missing link
between software,
rules, best practices and processes in science.
data and
papers.
Image: http://www.desk7.net/wallpapers.aspx?typeid=6374