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 21

The Open Source Ecosystem Transforming Research Communication

2

Share

Download to read offline

An emerging ecosystem of open source projects is evolving how research is communication, published and shared, improving the transparency, openness, integrity and discoverability of science and scholarship

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

The Open Source Ecosystem Transforming Research Communication

  1. 1. The Open Source Ecosystem Transforming Research Communication SSP 2018 May 31 2018 Kristen Ratan #osbazaar
  2. 2. 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.
  3. 3. The ecosystem is emerging
  4. 4. Coko’s Editoria Coko’s xPub eLife Libero OJS WaxTexture StencilaDAT INK xSweet Science Fair Substance library Platforms Tools The Open Ecosystem CERN’s Invidio Services Open Review Collabor- ation Hosting 3rd Party Peer Review Copy- editing Pop-up Publishing
  5. 5. 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
  6. 6. Collaboration in the browser
  7. 7. Collaborative Webspace
  8. 8. Digital-first workflow with automation and collaboration tools
  9. 9. Author Experience
  10. 10. Editor Experience
  11. 11. Reviewer Experience
  12. 12. The output must evolve
  13. 13. Static publication Living, versioned constellation of research objects
  14. 14. There is no one size fits all solution
  15. 15. PubSweet Three platformuse cases (so far) Books Journals Micropublications Design Developmentcycles Testing Launch
  16. 16. 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
  17. 17. Community-built and owned OS is sustainable
  18. 18. Successful Open Source Projects ● The internet: TCP/IP (governing protocols), BIND (DNS resolver) ● The Web: 75% adoption of OS browsers (Chrome, Firefox), 50% of websites delivered by Apache web server, 70% of sites use WordPress, Joomla or Drupal as a CMS ● Computers: Android + Apple (built on OS BSD Kernel) have twice as much adoption as Windows ● Phones: Android, iOS (built on OS Darwin operating system) dominate ● Cloud hosting services: OpenStack has 17% market share against Amazon, Microsoft and Google
  19. 19. Shared Infrastructure ● Pooling resources to get more for your investment ○ Technology stack ○ Maintaining standards ○ New functionality ● Sharing the burden of keeping up and the benefit of new ideas ● Focusing on the layer that differentiates your organization ○ Content ○ Brand ○ Quality ○ People
  20. 20. @kristenratan 21 Get in touch: @kristenratan kristen@coko.foundation

Editor's Notes

  • [Coko] I believe that research communication is a public good and the entire stack, from infrastructure to services to unique and branded publishing channels belong in the public domain. At Coko, we are building open infrastructure that can turn publishing back into a public utility AND supports experimentation. We do not believe in a single platform, a single methodology or a single innovator of new publishing models. We envision an ecosystem of tool builders, novel publishing models, platform and service providers. We would like to see governments and funders supporting this and elevating solutions that are effective so that the matrix begins to evolve into a more constrained set of recognizable models.
  • Modern, digital-first and easily accessible infrastructure will speed up research communication and lower the costs, but more importantly, it will unleash the pent up innovation that communities have to transform.
  • With a web-friendly version of the manuscript at the center of all activities, a web collaboration space is created that can support automatic and human curation of the document or its metadata. All actions done become part of the manuscripts metadata, in fact, and available in reports or as part of the published record.
  • A more rational workflow might involve converting author Word files into HTML as early as possible, preferably upon submission, and then applying a web-based workflow to these objects. This would enable much more rapid editorial and review processes, immediate and real-time revisions, and much faster and lower cost production. More automated checks on content as well as tagging and other forms of enrichment would be possible.
  • The output can be improved from static files to living documents, with all of the research objects networked and versioned. This is what researchers actually need.
  • Another key decision in our approach has been to decouple the architecture. Instead of building a monolithic platform, we’re building a modular set of components that can be assembled together to meet many different platform needs. There are many advantages, including the flexibility to create many different platforms from a pool of components, adding, editing or deleting components as needed without having to rearchitect or recode the whole platform, and the ability for anyone outside the original crew to build or modify components. This is the definition of future-proofing.
  • Hard problems get distributed
  • https://www.datanyze.com/market-share/iaas/openstack-market-share

    , I was there when publishing decided to not trust the open source web (JATS, offline systems and vendors). Let’s not do that again.
  • ×