Making the web work for science - UND

1,484 views
1,288 views

Published on

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,484
On SlideShare
0
From Embeds
0
Number of Embeds
35
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Making the web work for science - UND

  1. 1. making the web work for science kaitlin thaney @kaythaney ; @mozillascience univ. of north dakota / 5 feb 2014
  2. 2. doing good is part of our code
  3. 3. help researchers use the power of the open web to change science’s future.
  4. 4. (0)
  5. 5. science is still (largely) rooted in 17th c. practices. (and not in that “retro is cool” sort of way.)
  6. 6. early forms of knowledge sharing
  7. 7. our current systems are designed to create friction. despite original intentions.
  8. 8. “ 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
  9. 9. existing system is imperfect
  10. 10. data,
  11. 11. ability to reproduce experiments,
  12. 12. incentive to change,
  13. 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. 14. (1)
  15. 15. “open science” - access to content, data, code, materials. - emergence of “web-native” tools. - rewards for openness, interop, collaboration, sharing. - push for ROI, reuse, recomputability, transparency.
  16. 16. research cycle idea publish lit review share results analyze materials retest collect data experiment
  17. 17. types of information (added complexity) articles proceedings hypothesis/query prof activities mentorship teaching activities negative results content non-digital “stuff” protocols parameters analysis code datasets models
  18. 18. blocking points (to name a few ...) idea access publish attaining materials share results analyze retest collect data experiment
  19. 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. 20. Source: Michener, 2006 Ecoinformatics.
  21. 21. (2)
  22. 22. is open enough? what does it mean to “operate on/like the web”?
  23. 23. code (interop) community (people) code/data literacy (means to learn/engage)
  24. 24. our systems need to talk to one another.
  25. 25. “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.”
  26. 26. code as a research object what’s needed to reuse ?
  27. 27. code as a research object http://xkcd.com/285/
  28. 28. “There’s greater reward, and more temptation to bend the rules.” - David Resnik, bioethicist
  29. 29. (3)
  30. 30. we need to even (/ elevate) the playing field.
  31. 31. facing a digital skills gap
  32. 32. “Reliance on ad-hoc, selfeducation about what’s possible doesn’t scale.” - Selena Decklemann
  33. 33. learn from open source (culture as well as technology)
  34. 34. current activity: 129 instructors (60+, training) 109 bootcamps 3700+ learners
  35. 35. we need to build capacity, not just more nodes.
  36. 36. “research hygiene” instill best (digital, reproducible) practice
  37. 37. in an increasingly digital, datadriven world, what core skills, tools do the next-generation need?
  38. 38. education as a means of building community ... globally, as well as across disciplines.
  39. 39. (4)
  40. 40. shifting practice (and getting it to stick) is challenging. ... but not impossible.
  41. 41. disciplines as cultures
  42. 42. can we do the same for research on the web? 63 nations 10,000 scientists 50,000 participants
  43. 43. what are the necessary components? tools and technology cultural awareness, best practice connections, open dialogue skills training
  44. 44. (5)
  45. 45. operating in isolation doesn’t scale.
  46. 46. coordination and collaboration are key. design for interoperability. remember the non-technical challenges.
  47. 47. join us (and the conversation.) teach, contribute, learn. http://software-carpentry.org http://mozillascience.org
  48. 48. questions? kaitlin@mozillafoundation.org @kaythaney ; @mozillascience

×