Keynote for RMACC event at University of Colorado - Boulder. August 12, 2015.

1. kaitlin thaney
@kaythaney ; @mozillascience
RMACC / 12 aug 2015
leveraging the power
of the web for science

2. doing good is part of our code

3. help researchers leverage
the power of the open web.

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

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

6. (0)

7. http://bit.ly/1eZZC0f

9. our current systems are
creating friction.
despite original intentions.

10. current state of science
articles
data
patents

11. some have a firehose
articles
data
patents

12. quality versus quantity
measured systems

13. Source: Michener, 2006 Ecoinformatics.

15. (1)

16. what does
“web literacy”
mean for research?

18. communication
access, reuse, scale
distributed environment
the web as a platform

19. power, performance, scale

20. - 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”

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

22. putting open ideals into practice
(+ paying it forward)
https://commonspace.wordpress.com/2015/07/15/web-literacy-and-leadership/

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

24. (2)

25. learning from (+ through)
open source
development
examples of “science like the web”
in practice

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

31. <institutional archives>
<national archives>
<code repos>
syndication and storage
(via APIs)

32. http://softwarediscoveryindex.org/report/

33. from campaigning to discovery

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

39. http://openresearchbadges.org/

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

42. (3)

43. fostering a (sustainable)
community of practitioners

45. how do we amplify within
research?
(... and beyond software
development?)

46. community-driven contributorship
http://mozillascience.github.io/leadership-training/

47. mozillascience.org/collaborate

48. 2 days, 30+ cities, 53+ hours
http://bit.ly/1N331JV

49. 100+ pull requests
(code, content, learning resources)
http://bit.ly/1N331JV

52. https://www.mozillascience.org/fellows

53. (4)

54. how do we build
capacity?
furthering adoption of
open, web-enabled research

55. rewards, incentives,
reputation

57. Source: Piwowar, et al. PLOS.

58. supports needed for
“professional development”

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

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

62. resbaz.edu.au

63. lowering barriers to entry
(+ leveling the playing field)

64. (5)

65. we have a history of
working collaboratively.
(but there’s room for improvement.)

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

68. think beyond access, to
usability.
design for interoperability.
remember the
non-technical challenges.

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

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