Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Leveraging the power of the web - Open Repositories 2015

3,757 views

Published on

Keynote from Open Repositories 2015, Indianapolis, Indiana - June 9, 2015

Published in: Technology

Leveraging the power of the web - Open Repositories 2015

  1. 1. kaitlin thaney @kaythaney ; @mozillascience open repositories / 9 june 2015 leveraging the power of the web for science
  2. 2. doing good is part of our code
  3. 3. help researchers leverage the power of the open web.
  4. 4. learning around open source, data sharing needed to further open practice; empowering others to lead in their communities.
  5. 5. code (interop) community (people) code/data literacy (means to learn/engage)
  6. 6. (0)
  7. 7. our current systems are creating friction. despite original intentions.
  8. 8. current state of science articles data patents
  9. 9. some have a firehose articles data patents
  10. 10. quality versus quantity measured systems
  11. 11. Source: Michener, 2006 Ecoinformatics.
  12. 12. (1)
  13. 13. what do we mean by “web-enabled research”?
  14. 14. communication access, reuse, scale community-building the web as a platform
  15. 15. power, performance, scale
  16. 16. - 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”
  17. 17. 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...
  18. 18. (2)
  19. 19. our models of discovery are rapidly evolving. shift from institutional to distributed.
  20. 20. http://bit.ly/1eZZC0f
  21. 21. access vs utility how to reconcile?
  22. 22. http://bit.ly/1MEcOmD An example of a false-positive in the field of Solar—Terrestrial research: A Purported relationship between Neutron monitor changes and extremes of the Indian Monsoon Dr. Benjamin A. Laken, Department of Geosciences, University of Oslo, Norway
  23. 23. (3)
  24. 24. freedom to prototype and innovate. (connecting the dots.)
  25. 25. code as a research object what’s needed to reuse ? http://bit.ly/mozfiggit
  26. 26. <institutional archives> <national archives> <code repos> syndication and storage (via APIs)
  27. 27. http://softwarediscoveryindex.org/report/
  28. 28. from campaigning to discovery
  29. 29. open, iterative development the “work in progress” effect
  30. 30. http://openresearchbadges.org/
  31. 31. http://mozillascience.org/contributorship-badges-a-new-project/
  32. 32. (4)
  33. 33. how do we build capacity? furthering adoption of open, web-enabled research
  34. 34. fostering a (sustainable) community of practitioners
  35. 35. rewards, incentives, reputation
  36. 36. Source: Piwowar, et al. PLOS.
  37. 37. supports needed for “professional development”
  38. 38. “Reliance on ad-hoc, self- education about what’s possible doesn’t scale.” - Selena Decklemann
  39. 39. https://mozillascience.github.io/studyGroupHandbook/
  40. 40. resbaz.edu.au
  41. 41. mozillascience.org/collaborate
  42. 42. lowering barriers to entry (+ leveling the playing field)
  43. 43. focus on building capacity, not just more nodes.
  44. 44. (5)
  45. 45. http://ukiyo-e.org/ ; @jeresig
  46. 46. we have a history of working collaboratively. (but there’s room for improvement.)
  47. 47. 63 nations 10,000 scientists 50,000 participants can we do the same / better for research on the web?
  48. 48. think beyond access, to utility. design for interoperability. remember the non-technical challenges.
  49. 49. we’re here to help. http://mozillascience.org sciencelab@mozillafoundation.org
  50. 50. kaitlin@mozillafoundation.org @kaythaney ; @mozillascience special thanks:

×