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
January 27, 2017

Editoria Update

Editoria is the monograph production platform we are building with the University of California Press and the California Digital Library. 
 
The following are some screenshots with short explanations by way of update on progress. First, it is good to understand the names of the components that comprise Editoria, they are:
  1. Dashboard – where the users of the system can find all the books they are working on
  2. Book Builder – this is specific to each book and lists all front, body and back matter. The Book Builder also has some workflow features.
  3. Editor – the component that enables the content of the chapters (etc) to be edited.

Dashboard

The Dashboard hasn’t changed a lot as it was one of the first parts of the system to be built. More will be added to this component as it is a critical part of the workflow and users will benefit a lot from status information (etc) that will be displayed here. For now, it contains just a list of the books each user is working on (each user only sees their books).

Editoria Dashoard (more to come!)

Clicking on the ‘edit’ text for each book takes the user to the Book Builder for that book.

Book Builder

The Book Builder lists all the divisions (front, back, and body matter) and their components (chapters and parts). We are using the terminology from the Chicago Manual of Style to describe the book parts. 

Book Builder

Let’s look at it in a little more detail.

List of book parts and chapters.

You can see from the above that there is a list of chapters nested under ‘parts’. Users can add and remove as many chapters and parts as they need. Additionally, these can be dragged around to re-order. You will notice a few additional features:

  • status – Each title (part/chapter) has 4 status markers – Style, Edit, Review, Clean. Each of these can be clicked on to advance the status. For example, clicking on ‘To Style’ will advance the status to ‘Styling’. That would mean someone is styling (applying correct named styles eg. h1, h2 etc) to the content of that part/chapter. The status also has an additional effect – it is tied to access permissions. This can be changed for each organisation. In this instance, UCP wanted to lock authors out of edit mode for a component if the status was set to ‘Styling’ or ‘Cleaning’. 
  • Upload Word – it is now possible to upload an MS Word .docx to any chapter or part. Editoria is integrated with INK and XSweet (which we have spent a lot of time building) to enable the conversion of MS Word to HTML. The HTML is then displayed in the chapter. This enables publishing production staff (or similar) to be able to load the author’s manuscript into the system.
  • green tick‘ – this simply indicated that the chapter/part has some initial content.

Additionally, each of these chapters/parts has (at the right side) the following:

Right side of Book Builder

This enables the user to rename, edit and delete a chapter or part. The left/right box indicates the pagination break (used at render time). Clicking on one of these selects the left or right page as the starting page for the content (this is most important for printed books).

As you can guess from the image above, it is also possible (of course) to create new parts and chapters.

Clicking on ‘edit’ for a part or chapter takes the user through to the editor with the content for that part/chapter loaded.

Before moving on, it is worth noting that from the Book Builder, the Production Editor can assign the team through the Team Manager (which is linked from this interface).

Team Manager

The Editor

Editor with chapter content loaded

There are several things to know about this. First, the editor is a custom made Substance.io editor. This means we can build it exactly to meet the needs of the publisher (in this case UCP/CDL). Hence, if the publisher has a list of specific styles (they all do!) we can build these (pretty simply) into the editor to match exactly what they need. 

In addition, we can add whatever the publisher requires to this interface. In the case of Editoria, there are a few things of interest to point out:

  1. Annotations – we have built-in a commenting system, primarily so the copy editor can make comments on the text for the author to consider. This enables a conversation to take place on the text itself between the necessary parties. 
    Annotations in action
    It is possible to add annotations, resolve them, and reply to them in a thread.

  2. Track Changes – they are the best of tools, the worst of tools. As much as we would like to see the need for tracking changes functionality disappear, it is a pretty necessary tool for many publishers. So we have built this into UCP/CDL’s requirements.
    Track Changes in action

    It is possible to turn Track Changes on or off, as well as turning on or off the ability to see the tracked changes inline. In this way, a Copy Editor, for example, can turn on Track Changes, ask the author to make changes, and then view what has been changed and accept/reject as necessary. They can also view the text with the Track Changes view off if required.

  3. Structure – everyone can see the chapter/part chapter displayed on the right. This enables a quick look to check that the heading nesting (for example) is correct, as well as enabling quick navigation around the content.

    Chapter structure displayed

    In addition, we have notes management, links, images, super- and sub- script, and a lot more. Editoria is looking great and has been used in the production of its first book already. It is, of course, open source (everything Coko produces is open source). If you would like to know more, contact us or the good people at UCP/CDL who have plans to assist publishers wanting to use the platform.