some technical hurdles towards open science

30
Open Source, Open Data, Open Science: three easy words, many obstacles Björn Brembs Universität Regensburg http://brembs.net

Upload: bjoern-brembs

Post on 06-May-2015

1.234 views

Category:

Education


2 download

DESCRIPTION

My presentation at the DataCite workshop in Cologne, December 12, 2012.

TRANSCRIPT

Page 1: Some technical hurdles towards open science

Open Source, Open Data, Open Science:three easy words, many obstacles

Björn BrembsUniversität Regensburg

http://brembs.net

Page 2: Some technical hurdles towards open science

SCHOLARSHIP

Institutions produce publications, data and software

Page 3: Some technical hurdles towards open science

CRISIS I

Dysfunctional scholarly literature

Page 4: Some technical hurdles towards open science

Literature

• Limited access• No global search• No functional hyperlinks• No flexible data

visualization• No submission

standards• (Almost) no statistics• No text/data-mining• No effective way to sort,

filter and discover• No scientific impact

analysis• No networking feature• etc.

…it’s like the web in 1995!

Page 5: Some technical hurdles towards open science

CRISIS II

Scientific data in peril

Page 6: Some technical hurdles towards open science
Page 7: Some technical hurdles towards open science
Page 8: Some technical hurdles towards open science

CRISIS III

Non-existent software archives

Page 9: Some technical hurdles towards open science
Page 10: Some technical hurdles towards open science
Page 11: Some technical hurdles towards open science

My Digital Utopia:

• No more corporate publishers – libraries archive everything and make it publicly accessible according to a world-wide standard

• Single semantic, decentralized database of literature, data and software

Technically feasible today (almost)

Page 12: Some technical hurdles towards open science

Today‘s Digital Dystopia

• Institutional email• Institutional

webspace• Institutional blog• Library access card• Open access

repository

• No archiving of publications

• No archiving of software

• No archiving of data

Page 13: Some technical hurdles towards open science
Page 14: Some technical hurdles towards open science

Software to control the experiment and save the data

Page 15: Some technical hurdles towards open science

Software to analyze and visualize the data

Page 16: Some technical hurdles towards open science
Page 17: Some technical hurdles towards open science

buridan.sourceforge.net

Page 18: Some technical hurdles towards open science
Page 19: Some technical hurdles towards open science
Page 20: Some technical hurdles towards open science
Page 21: Some technical hurdles towards open science

However, a version is already available

Page 22: Some technical hurdles towards open science

Get your API keys.Insert them in your R code

Page 23: Some technical hurdles towards open science

Add the variables to your code

Page 24: Some technical hurdles towards open science

What to publish on figshare

For instance, produce an image than can be previewed (instead of a multiple page pdf)

Page 25: Some technical hurdles towards open science

Add new, or update an existing article

Page 26: Some technical hurdles towards open science

Run your script and...

Same type of experiments → same scriptDefault: → same categories

→ same tags→ same authors→ same links→ same description

→ One complete article, in one click.

Update the figure: Higher sample size directly published while analysed, your boss may see the results before you do! (or you may see the results of your student before they do)

Possibility to make it public and citable in one click or directly in the R code.

Page 27: Some technical hurdles towards open science

Citable?

http://dx.doi.org/10.6084/m9.figshare.97792

Page 28: Some technical hurdles towards open science

Citable!

Page 29: Some technical hurdles towards open science
Page 30: Some technical hurdles towards open science

JULIEN COLOMB

One person is not an institutional infrastructure!