Blog
Coko & eLife partner on first PubSweet fueled journals submission & peer-review platform
Seeding a New Ecosystem: open infrastructure
Take Editoria for a spin
Making decisions in a small team and keeping it fun
A look at the future of journals with xpub
Editoria 1.1: Meet the Automagic Book Builder
A sneak peak at what’s next for PubSweet
Travel the long and winding road to PubSweet
Ink 1.0 is here!
Baby steps to user-centric open source development
Why we’re all in open source now
Getting Started with Coko
Editoria 1.0 preview
Preprints won’t just publish themselves: Why we need centralized services for preprints
INK – the file conversion engine
How we’re building the ‘mountain chalet’ of complex conversions
Sowing the seeds for change in scholarly publishing
Open Source Alliance for Open Science
Editoria Newsletter Out Now!
INK client upgrade
All About INK (explained with cake)
Track Changes (Request for Comments)
Book on Open Source Product Development Method Released!
Italics, Buenos Aires and Coko?
Editoria Update
Where we are with File Conversion
A Typescript for the Web
Coko Celebrates Year One
Editoria – Scholarly Monograph Platform
Adam Hyde’s Blog
Introducing Christos
Introducing Yannis
New PubSweet release
Attribution in Open Source Projects
Open Source for Open Access
Reimagining Preprints: a new generation of early sharing
Introducing Stencila and Nokome Bentley
Reimagining Publishing
Introducing Charlie
PubSweet 1.0 “Science Blogger” alpha 2
PubSweet 1.0 “Science Blogger” alpha, INK 1.0 alpha RELEASES!!!
Collaborative Product Development
Publishing for reproducibility: collaborative input and networked output
Substance Consortium
UCP & CDL Announcement
Release 0.2.0 is here!
CKF receives funding from the Gordon and Betty Moore Foundation to transform research communication
Technology Slows Down Science
[tech post] CSS and Drop Caps
Vote for the pubsweet logo!
Introducing Substance
Digging Collaboration and Cooperation: Code for a New Era
Coko 2015
PubSweet 0.1 Release
Coko Resources
Making science writing smarter
What I Have Learned About Building Community
Introducing the Tech Team
Knowledge and Communication
PKP and CKF Strategic Alliance
CKF Launches
May 9, 2016

Publishing for reproducibility: collaborative input and networked output

Coko has a broad mission to reformulate and improve how knowledge is produced and shared. As a starting point, we’re focusing on scholarly publishing because, while the knowledge is crucial to us, the process is convoluted, expensive and slow. It can take months to even years for finished research to be published and the final product is missing key components such as the data, protocols, code and materials needed for other scholars to reproduce the work.


Evolving the scholarly communication workflow

Most scholarly communication workflows are still very much as they were 10 or 15 years ago, with work being done in isolated, proprietary tools and formats and these being shuffled around between people using email.

Peer Review today

Because the very process of producing scholarly knowledge is flawed, the final published product, be it a journal article or a book chapter, is severely limited. At each stage, the research is dumbed down, data and context removed. To improve the published product, we must add value at each stage rather than remove it.

Coko is a community effort to build collaborative processes and technologies that respect the research process and improve the output. The open source tool chain being assembled enables real-time collaboration around the content and data as the published record is being produced. This means that the published product can mirror or exceed the research itself.

Collaborative workspace.png

Shifting from a linear, largely offline submission and editorial workflow to a collaborative webspace means taking creating a digital first process that posits an HTML document at the center of a flexible set of tasks and action. The Coko community is building many tools including a sophisticated web editor and a workflow engine that can be configured for many different workflows and be adjusted easily to fit changing process needs.


Creating a community of exceptional open source projects

Coko’s philosophy is to bring together the best open source projects into an interoperable tool chain rather than try and build everything as one monolithic platform. For example, The Coko community is working closely with Substance.io which has built the first open source real-time and concurent web editor focused on scientific and scholarly content. All of the work is done within the document itself and using web collaboration tools for discussion and annotation. All actions are tracked to make the process transparent

Substance Editor.png

And Coko and Substance are partnering with Stencila, a platform for creating documents that are driven by data, enabling templates for embedding data analysis and presentation code that work well within Substance’s WYSIWYG editing tools.


HTML first: content conversion and adding intelligence

INK transformation.jpg

Authors overwhelmingly prefer to write in MS Word. Rather than try to change author behavior overnight, it’s possible to transform Word and other largely unstructured documents into highly structured HTML early on in the production process, such as upon submission to a publisher. INK is another tool the Coko community is working on for content converters and other transformation tools and acts as a job management system, allowing users to configure a recipe of actions upon a document as it is being converted into HTML, such as enriching with identifiers, entities, links and semantics. INK normalizes metadata and connects all of the research objects that went into creating a body of research work, laying the foundation for a networked publication that will improve reproducibility.


The networked, living publication

By building the publishing process directly from the research objects such as data, code, materials, media and discussion, the collection of Coko community technologies will improve the published output, enabling a dynamic and evolving body of work to replace the static journal article or book chapter of today.

Networked output.png

Post by Kristen Ratan, small improvements by Adam Hyde