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
Successful Open Source Projects
● The internet: TCP/IP (governing protocols), BIND (DNS
● 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)
● Cloud hosting services: OpenStack has 17% market share
against Amazon, Microsoft and Google
● 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
● Focusing on the layer that differentiates your
Get in touch:
[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.