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.
Upcoming SlideShare
What to Upload to SlideShare
What to Upload to SlideShare
Loading in …3
1 of 16

Beyond the journal coko and the open source ecosystem



Download to read offline

To transform research communication we need incremental results, data, and all outputs shared at each stage, with incentives that match. Preprints and open data policies are not enough.

Related Books

Free with a 30 day trial from Scribd

See all

Beyond the journal coko and the open source ecosystem

  1. 1. Beyond the Journal: Scholarly Communication Throughout the Research Life Cycle Presented by Kristen Ratan to the EC Expert Panel on the Future of Scholarly Communication 26 March 2018, Brussels
  2. 2. Proposal: Return scholarly communication to being a public good An open ecosystem that ensures that the production, communication, access, and use of all research objects across the research cycle maximizes the global public good by being rapid, transparent, relevant, equitable, and inclusive.
  3. 3. Research Lifecycle – Sharing Outputs At Every Stage Data/results Micropublications PreprintArticle Discovery and Use Data is annotated and openly available, notebooks are shared Short, citable publications are shared early and often Early forms of article are posted and available for comment, and various forms of review Article is a living publication, able to be updated, versioned, and open access Research objects are networked to each other and available for real-time collaboration Incentives and rewards motivate the behavior at each stage
  4. 4. Challenges in research communication Slow Static Incentives don’t work Entrenched commercialization
  5. 5. The path is not linear
  6. 6. Communities are working to solve these problems • Caltech Wormbase Micropublications, RapidScience, eLife’s collaborative peer review, PLOS Currents, F1000Research, preprint projects/services Slow • Stencila living figures and data-driven documents, RapidScience Evidence Reviews,, data/code repositories Static • Removing journal name in researcher assessment, RapidScience’s collaboration score, alternative metrics, “counting” preprints in tenure/promotion/grant, funder publishing channels Incentives • Open access, standing up to “big deals”, open source alternatives to commercial vendors, efforts to track true costs of publishing, low cost/free publishing alternatives Entrenchment
  7. 7. Coko believes... No one platform can solve all the problems. We need an ecosystem of tools and software. We should build modular & interoperable things. The community must create and own solutions.
  8. 8. Coko’s Editoria Coko’s xPub eLife Libero OJS WaxTexture StencilaDAT INK xSweet Science Fair Substance library Platforms Tool s The Open Ecosystem CERN’s Invidio Services Open Review Collabor- ation Hosting 3rd Party Peer Review Copy- editing Pop-up Publishing
  9. 9. ConversionSubmission Semantics enhancers AnnotationNotebooks Metadata Peer review Versions Production PubSweet Publishing Authoring Editorial tools Revision Syndica- tion Web delivery Reviewer matching Real-time collabora- tion Discovery tools Open, modular architecture enables innovation and collaboration
  10. 10. PubSweet Three use cases (so far) Books Journals Micropublications Design Developmentcycles Testing Launch
  11. 11. PubSweet Books: Editoria
  12. 12. PubSweet Journals:xPub
  13. 13. PubSweet Micropublications:xPub
  14. 14. Service providers Partnering tech organizations First wave adoption Early adopters Code contributors Core OS project Broad Community Community Led Open Source Core OS project Core OS project
  15. 15. It’s working An improvement for one becomes an improvement for all. Individual communities can focus on core areas of expertise — peer review, hosting, discovery — knowing that their innovations will improve the entire system. The result is more creativity, a more diverse set of solutions, and, ultimately, faster progress. -Andrew Smeall, Hindawi Having other people build components to solve the problems you are facing is a great benefit of a common infrastructure. but also knowing that what you’re building is useful to more than just your team really adds energy and purpose to our teams of developers and designers. -Paul Shannon, eLife
  16. 16. @kristenratan 16 Get in touch: @kristenratan