kaitlin thaney
@kaythaney ; @mozillascience
RMACC / 12 aug 2015
leveraging the power
of the web for science
doing good is part of our code
help researchers leverage
the power of the open web.
learning around
open source, data sharing
needed to further open practice;
empowering others to lead in
their communities.
code
(interop)
community
(people)
code/data literacy
(means to learn/engage)
(0)
http://bit.ly/1eZZC0f
our current systems are
creating friction.
despite original intentions.
current state of science
articles
data
patents
some have a firehose
articles
data
patents
quality versus quantity
measured systems
Source: Michener, 2006 Ecoinformatics.
(1)
what does
“web literacy”
mean for research?
communication
access, reuse, scale
distributed environment
the web as a platform
power, performance, scale
- access to content, data, code, materials.
- emergence of “web-native” tools.
- rewards for openness, interoperability, collaboration, sharing.
- push for ROI, reuse, recomputability, transparency.
“web-enabled research”
research social capital capacity
infrastructure layers for
open research
open tools
standards
best practices
research objects
scientific software
repositories
incentives
recognition / P&T
interdisciplinarity
collaboration
community dialogue
training
mentorship
professional dev
new policies
recognition
stakeholders: universities, researchers,
tool dev, funders, publishers, libraries...
putting open ideals into practice
(+ paying it forward)
https://commonspace.wordpress.com/2015/07/15/web-literacy-and-leadership/
service learning: n. hands-
on, experiential learning
where people develop skills
by working on a project in
service of a bigger goal.
http://bit.ly/1JTMBSb
(2)
learning from (+ through)
open source
development
examples of “science like the web”
in practice
code as a research object
what’s needed to reuse ?
http://bit.ly/mozfiggit
<institutional archives>
<national archives>
<code repos>
syndication and storage
(via APIs)
http://softwarediscoveryindex.org/report/
from campaigning to discovery
open, iterative
development
the “work in progress” effect
http://openresearchbadges.org/
http://mozillascience.org/contributorship-badges-a-new-project/
(3)
fostering a (sustainable)
community of practitioners
how do we amplify within
research?
(... and beyond software
development?)
community-driven contributorship
http://mozillascience.github.io/leadership-training/
mozillascience.org/collaborate
2 days, 30+ cities, 53+ hours
http://bit.ly/1N331JV
100+ pull requests
(code, content, learning resources)
http://bit.ly/1N331JV
https://www.mozillascience.org/fellows
(4)
how do we build
capacity?
furthering adoption of
open, web-enabled research
rewards, incentives,
reputation
Source: Piwowar, et al. PLOS.
supports needed for
“professional development”
“Reliance on
ad-hoc, self-
education
about what’s
possible
doesn’t scale.”
- Selena Decklemann
https://mozillascience.github.io/studyGroupHandbook/
resbaz.edu.au
lowering barriers to entry
(+ leveling the playing field)
(5)
we have a history of
working collaboratively.
(but there’s room for improvement.)
63 nations
10,000 scientists
50,000 participants
can we do the same / better
for research on the web?
think beyond access, to
usability.
design for interoperability.
remember the
non-technical challenges.
we’re here to help.
http://mozillascience.org
sciencelab@mozillafoundation.org
kaitlin@mozillafoundation.org
@kaythaney ; @mozillascience
special thanks:

Leveraging the power of the web - Rocky Mountain Advanced Computing Conference