1. kaitlin thaney
@kaythaney ; @mozillascience
UQ / 23 june 2014
making the web
work for science

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

3. (0)

4. science is still (largely)
rooted in 17th c. practices.
(and not in that “retro is cool” sort of way.)

5. early forms of knowledge sharing

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

11. 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
“
“

12. existing system is imperfect

13. 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

14. (1)

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

16. research cycle
idea
experiment
lit review
materials
publish
share results
retest
analyze
collect data

17. types of information
hypothesis/query
protocols
parameters
content
non-digital “stuff”
articles
proceedings
negative results
analysis
code
datasets
models
(added complexity)
prof activities
mentorship
teaching activities

18. blocking points
idea
experiment
access
attaining
materials
publish
share results
retest
analyze
collect data
(to name a few ...)

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

20. Source: Michener, 2006 Ecoinformatics.

22. (2)

23. is open enough?
what does it mean to “operate on/like the web”?

24. code
(interop)
community
(people)
code/data literacy
(means to learn/engage)

25. our systems need to
talk to one another.

28. “One worry I have is that, with reviews like this, scientists will be
even more discouraged from publishing their code [...] We need
to get more code out there, not improve how it looks.”

29. code as a research object
what’s needed
to reuse ?

30. code as a research object
http://xkcd.com/285/

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

38. (3)

39. is open enough?
what does it mean to “operate on/like the web”?

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

41. “web-enabled science”
what’s missing?
- access to content, data, code, materials.
- emergence of “web-native” tools.
- rewards for openness, interop, collaboration, sharing.
- push for ROI, reuse, recomputability, transparency.

42. we need to even
(/ elevate) the playing field.

43. facing a digital skills gap

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

49. learn from open source
(culture as well as technology)

50. current activity:
130+ instructors
(60+, training)
3700+ learners

51. we need to build capacity,
not just more nodes.

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

54. in an increasingly digital, data-
driven world, what core skills, tools
do the next-generation need?

55. education as a means of
building community
... globally, as well as across disciplines.

56. (4)

57. shifting practice
(and getting it to stick)
is challenging.
... but not impossible.

58. disciplines as cultures

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

61. tools and technology
cultural awareness, best practice
connections, open dialogue
skills training
what are the necessary components?

62. (5)

63. operating in isolation
doesn’t scale.

64. coordination and
collaboration are key.
design for interoperability.
remember the
non-technical challenges.

65. join us
(and the conversation.)
teach, contribute, learn.
http://software-carpentry.org
http://mozillascience.org

66. questions?
kaitlin@mozillafoundation.org
@kaythaney ; @mozillascience