Talk from the AAMC GREAT/GRAND meeting in Fort Worth, Texas.

1. building capacity for open
research practice
kaitlin thaney
@kaythaney ; @mozillascience
AAMC / 18 sept 2014

2. doing good is part of our code

3. help researchers use the
power of the open web to
change science’s future.

4. (0)

5. our current systems are
designed to create
friction.
despite original intentions.

8. current state of science
articles
data
patents

9. some have a firehose
articles
data
patents

10. traditions last not because they are
excellent, but because influential
people are averse to change and
because of the sheer burdens of
transition to a better state ...
“
“
Cass Sunstein

11. downside of output-driven
recognition systems

12. “There’s greater reward,
and more temptation to
bend the rules.”
- David Resnik, bioethicist

13. (1)

14. leveraging the power of
the web for scholarship

15. “web-enabled research”
- access to content, data, code, materials.
- emergence of “web-native” tools.
- rewards for openness, interop, collaboration, sharing.
- push for ROI, reuse, recomputability, transparency.

16. what do we mean by
“open research”?
community technology practices
collaborative interoperable open review
participatory discoverable data
management
recognition open tools sharing / reuse
mentorship designed for
reuse
documentation /
versioning

17. we’re rewarding the
wrong behavior.
at the sacrifice of scientific progress.

18. Source: Michener, 2006 Ecoinformatics.

19. “... up to 70 percent of research from academic labs cannot be
reproduced, representing an enormous waste of money and effort.”
- Elizabeth Iorns, Science Exchange

20. “research hygiene”
instill best
(digital,
reproducible)
practice

21. rethinking
“professional development”

22. “Reliance on
ad-hoc, self-education
about what’s
possible
doesn’t scale.”
- Selena Decklemann

24. (2)

25. shifting practice takes a
multi-faceted approach.
necessary v. sufficient

26. infrastructure layers for
efficient, reproducible research
research social capital capacity
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 ...

27. freedom to prototype
and innovate.
(connecting the dots.)

28. code as a research object
what’s needed to reuse ?
http://bit.ly/mozfiggit

32. (community driven)
metadata for software discovery: JSON-LD
http://bit.ly/mozfiggit

33. fostering a (sustainable)
community of practitioners

34. current activity:
235+ instructors
(60+, training)
4000+ learners

36. focus on building capacity,
not just more nodes.

37. (3)

38. shifting practice
(and getting it to stick)
is challenging.
(takeaways and closing caveats.)

39. 1. bake reproducible
practices into the fabric of
academia. and design to
enable scale.

40. 2. create opportunities and
incentives for students and
faculty to experiment,
teach, work across aisles.

41. 3. rethink how we reward
researchers and support
roles. (and don’t be afraid
to hit refresh.)

42. 4. be mindful of jargon/
semantics traps.

43. we’re here to help.
teach, contribute, learn.
http://mozillascience.org
sciencelab@mozillafoundation.org

44. kaitlin@mozillafoundation.org
@kaythaney ; @mozillascience
special thanks: