The document discusses how scholarly communication can learn from open source practices such as publishing works early and often, using open licenses, and making intellectual projects and processes openly accessible and editable. It traces the concept of open access publishing back to open source software and discusses how practices like source code management, open bug databases, and releasing works early and iteratively could translate to academic research. The document advocates for making the scholarly process and content more openly accessible and collaborative.

1. What can scholarly communication learn from open
source? Publish early, publish often!
Stian Håklev
FOSS Brown Bag Seminar at the iSchool, October 27, 2011
CC BY

5. Going beyond this

11. Text
“What is inside our full-text articles, and how do we improve access to it? Or: Stories, that persuade with data.”, Anita de Ward

12. “What is inside our full-text articles, and how do we improve access to it? Or: Stories, that persuade with data.”, Anita de Ward

13. “What is inside our full-text articles, and how do we improve access to it? Or: Stories, that persuade with data.”, Anita de Ward

14. Opening up the process

15. The Open Scholar, as I'm defining this person, is not
simply someone who agrees to allow free access and
reuse of his or her traditional scholarly articles and
books; no, the Open Scholar is someone who makes
their intellectual projects and processes digitally
visible and who invites and encourages ongoing
criticism of their work and secondary uses of any or
all parts of it--at any stage of its development.
Gideon Burton, www.academicevolution.org

16. Going back to Open Source

17. Going back to Open Source
tracing the concept of OA back to FOSS

18. Going back to Open Source
tracing the concept of OA back to FOSS
open licenses

19. Going back to Open Source
tracing the concept of OA back to FOSS
open licenses
access to source code

20. Going back to Open Source
tracing the concept of OA back to FOSS
open licenses
access to source code
open development practices (source code
management, open bug database, “release early,
release often”)

21. Going back to Open Source
tracing the concept of OA back to FOSS
open licenses
access to source code
open development practices (source code
management, open bug database, “release early,
release often”)
how does this translate to academic research?

34. Making it real

36. Features

37. Features
Integrates BibDesk, Skim, Chrome and DokuWiki using Ruby,
AppleScript and keyboard shortcuts

38. Features
Integrates BibDesk, Skim, Chrome and DokuWiki using Ruby,
AppleScript and keyboard shortcuts
Easily import Google Scholar bibtex and PDFs

39. Features
Integrates BibDesk, Skim, Chrome and DokuWiki using Ruby,
AppleScript and keyboard shortcuts
Easily import Google Scholar bibtex and PDFs
Mark up PDFs in Skim (or on Kindle)

40. Features
Integrates BibDesk, Skim, Chrome and DokuWiki using Ruby,
AppleScript and keyboard shortcuts
Easily import Google Scholar bibtex and PDFs
Mark up PDFs in Skim (or on Kindle)
Auto-generate nice wiki pages for each publication, with
metadata and notes (plus indices)

41. Features
Integrates BibDesk, Skim, Chrome and DokuWiki using Ruby,
AppleScript and keyboard shortcuts
Easily import Google Scholar bibtex and PDFs
Mark up PDFs in Skim (or on Kindle)
Auto-generate nice wiki pages for each publication, with
metadata and notes (plus indices)
Easily process raw notes to higher level notes, cite publications
on topical wiki pages, etc. Also use citekey on blog, or when
authoring articles

42. Features
Integrates BibDesk, Skim, Chrome and DokuWiki using Ruby,
AppleScript and keyboard shortcuts
Easily import Google Scholar bibtex and PDFs
Mark up PDFs in Skim (or on Kindle)
Auto-generate nice wiki pages for each publication, with
metadata and notes (plus indices)
Easily process raw notes to higher level notes, cite publications
on topical wiki pages, etc. Also use citekey on blog, or when
authoring articles
Offline file-based wiki, easily synced with public server

43. Ryan Muller, http://learnstream.org/wiki

44. Niklas Karlsson, http://kollaboration.se/wiki

45. Challenges

46. Challenges
Very difficult for others to install, because of the
number of software packages that are integrated,
and the difficulty of making a Ruby installer

47. Challenges
Very difficult for others to install, because of the
number of software packages that are integrated,
and the difficulty of making a Ruby installer
Finding ways of sharing data or interconnecting
different wikis

48. Thanks!
Stian Håklev
shaklev@gmail.com
http://reganmian.net
http://reganmian.net/wiki/
researchr:start