shifting scientific practice (k. thaney)
TRANSCRIPT
kaitlin thaney@kaythaney ; @mozillascience
ORCID / 3 nov 2015
shifting scientific practice
doing good is part of our code
we empower researchers to do more open, collaborative research on the web.
(0)
current state of science
articlesdata
patents
some have a firehose
articlesdata
patents
quality versus quantity measured systems
a few fallacies of the research system
the published record is the only useful record
if it’s published, it’s usable.
What Des-Cartes did was a good step. You have added much several ways, &
especially in taking ye colours of thin plates into philosophical consideration.
If I have seen further it is by standing on ye shoulders of Giants.
- Isaac Newton, 1676
“
“
... that this is good job advice:
the systems we’re crafting serve the community’s (evolving) needs
1. examples of the role identity plays in community.
2. means to shift practice. 3. ... and how to sustain it.
(1)
recognizing software and data contributions
code as a research objectwhat’s needed to reuse ?
http://bit.ly/mozfiggit
<institutional archives>
<national archives>
<code repos>
syndication and storage (via APIs)
http://openresearchbadges.org/
Contributorship Badges (Paper Badger)
•Conceptualization•Data curation•Formal analysis•Funding acquisition•Investigation•Methodology•Project administration
•Resources•Software•Supervision•Validation•Visualization•Writing – original draft•Writing – review &
editing
Project CRediT: Contributor Roles Taxonomy
http://casrai.org/CRediT
http://mozillascience.org/contributorship-badges-a-new-project/
http://mozillascience.github.io/software-discovery-dashboard/
https://github.com/mozillascience/software-discovery-dashboard/issues/1
https://github.com/codemeta/codemeta
CodeMeta: exploring ways to address discoverability of contributions
(2)
shifting scientific practice (and getting it to stick)
openness, participation, collaboration
communicationaccess, reuse, scale
distributed, participatory
the web as a platform
- 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”
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
how do we amplify within research?
(... and beyond software development?)
mozillascience.org/collaborate
100+ pull requests
(code, content, learning resources)http://bit.ly/1N331JV
community-driven contributorship
http://mozillascience.github.io/leadership-training/
https://www.mozillascience.org/teaching-leadership-like-mozilla
(3)
how do we build, support and sustain momentum?
furthering adoption of open, web-enabled research
rewards, incentives, reputation
supports needed for“professional development”
“Reliance on ad-hoc, self-
education about what’s
possible doesn’t scale.”
- Selena Decklemann
lowering barriers to entry(+ leveling the playing field)
https://mozillascience.github.io/studyGroupHandbook/
https://www.mozillascience.org/fellows
https://www.mozillascience.org/fellows
Richard Smith-Unna Christie Bahlai Jason Bobe Joey Lee
(4)
we need your help.
rethink beyond just access to usability.
don’t forget the user in the design.
remember the non-technical challenges.
acknowledgments: Arfon Smith, Matt Jones, Mark Hahnel, Lars Holm Nielsen, Amye
Kenall, Laura Paglione, Brian Hole, Austin Davis-Richardson, Ai Deng, Robert Peters, Garth Henson, Anita Perala, Ali Al Dallal, Will Simpson, Alister Cole, Adam Blaine, Matt Mokary, Stefan Neamtu, Luke Coy +
many more.(+ the Mozilla Science Lab team: Abby Cabunoc Mayes, Arliss Collins,
Zannah Marsh, Steph Wright, )