Presentation for the 2015 National Data Integrity Conference at Colorado State University - May 6-8, 2015

1. kaitlin thaney
@kaythaney ; @mozillascience
colorado state / 07 may 2015
making the web
work for science

2. doing good is part of our code

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

4. learning around
open source, data sharing
needed to further open practice;
empowering others to lead in
their communities.

5. learning around
open source, data sharing:
sprints, collaborate, study groups
empowering others:
fellowships, mentorship, resbaz

6. (0)

7. 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. leveraging the power of
the web for scholarship

18. (if we’re lucky...)

19. power, performance, scale

20. - access to content, data, code, materials.
- distributed work environments, participatory.
- emergence of “web-native” tools, efficiency.
- rewards for openness, interop, collaboration, sharing.
- reuse, recomputability, transparency.
“web-enabled research”

21. how this
maps to research
community technology practices
collaborative interoperable open review
participatory discoverable
data
management
recognition open tools sharing / reuse
mentorship
designed for
reuse
documentation /
versioning

22. (2)

23. learning from (+ through)
open source
applying lessons from open source
development to science

27. open, iterative
development
the “work in progress” effect

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. http://softwarediscoveryindex.org/report/

37. http://mozillascience.org/contributorship-badges-a-new-project/

38. http://www.mozillascience.org/collaborate

39. (3)

40. our practices are
limiting us.
how to further adoption of
open, web-enabled science?

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

42. fostering a (sustainable)
community of practitioners

43. supports needed for
“professional development”

44. https://mozillascience.github.io/studyGroupHandbook/

45. working within the reward system.

46. http://openresearchbadges.org/

48. resbaz.edu.au

49. next global sprint: june 4-5, 2015
mozillascience.org/collaborate

51. lowering barriers to entry
(not expectations)

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

53. (4)

54. shifting practice
(and getting it to stick)
is challenging.
open science’s collective action problem.

56. 63 nations
10,000 scientists
50,000 participants
can we do the same
for research on the web?

57. 1. bake reproducible
practices into the fabric of
research.

58. 2. design to unlock latent
potential of our systems.
(most of the technology is already there.)

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

60. 4. use cases as means to
show potential, sell trust
and drive adoption.

61. we’re here to help.
http://mozillascience.org
sciencelab@mozillafoundation.org

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