Publication and citation of scientific softwarewith persistent identifiers

EGU General Assembly 2014, OSGeo Townhall Meeting, April 29, Vienna, AustriaMartin 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 RegensburgRoland Bertelmann, Helmholtz Centre Potsdam, GFZ German Research Centre for Geosciences, Library and Information Services

Heinz Pampel, Helmholtz Association, Helmholtz Open Access CoordinationMartin 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/

Establish the missing link

between software, data and papers.

papers

data

software

findings

Image: youtu.be/eYDjV7ajuMo, 1:52

crucial role in scientific work

rarely seen publishable

solutions lack researchers’ needs

in conflict with principle of reproducibility already professionally published

not standard practice

based on raw data & data from analyses and thus on software

Make software recognised

as scientific achievement.

Image: http://justhappeneduponthis.wordpress.com/2012/08/25/megaphone-mercy/

contribution

journals

achievement

gap

part of solution for question or problem & independent

common understanding

defined processes

accepted metrics

adoption

poorly perceived & hardly measurable

not assessed & not valued

… are often workarounds

publications in desired journals …

direct release not possible as scientific publication

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 traditionnot written for others · no intended re-use· kept privately & internally

happens informally & anonymously· heavily practiced in sciences· few contribute back

number of platforms· scientific needs partly addressed· unclear use

runnable code· sufficient documentation, sample data, tests, comments· adequate & qualified reviews· learn to write & release code and software

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

includes software engineering

habits are rarely practiced

skills seldom passed onto followers

code design, version control, documentation, testing …

safeguard traceability & re-use

adoption of software development life cycle and related processes

not covered in primary research task

no incentives to improve & publish code

software and code quality influence results

better software, better research

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