Substance Software GmbH

Michael Aufreiter

Oliver Buchtala

Simon Fraser University

Alex Garnett (me)

Juan Pablo Alperin

Background

PKP’s Open Typesetting Stack (OTS); JATSCon 2015

• Automated conversion from Word/PDF -> JATS using best-available tools

• “80% parse” -- very good results, but editing still needed for production quality

What now?

Could (and do!) continue to improve OTS

But how do we get to production?

Goal

Provide a complete fulltext XML workflow

• Encourage a transition away from Word typesetting

• Completely replace TinyMCE editors

We’ve gone and done it

Introducing Texture: An Open Source WYSIWYG Javascript Editor for JATS

Texture!

• http://substance.io/texture

• https://github.com/substance/texture

• Based on a new version of the Substance library used by eLife Lens

Configurable Views

• Different controls for authors and editors

• Can be a guide to tagging, or a plain authoring environment

• Offline version coming soon

Best-Practices JATS

• Imports any valid JATS

• Exports along JATS4R-like conventions (e.g. for consistent date formatting)

• Internally serializes JATS as overlapping annotations

• https://github.com/substance/texture-jats

Best-Practices Editor

• Collaborative editing (a la Google Docs) is (almost) supported

• Stores “weak links” to external services locally (e.g. CrossRef)

• Supports raw XML if you need to fine-tune

Current Feature Set

• Context enforcing!

• Regex find and replace

• Rearranging ToC to change section nesting

• Multilingual editing, and creating multiple languages of abstract

Why no demo?!

Next release is due NEXT month (May 2017)

• Will contain complete-enough set of JATS for production

• Any JATS elements not yet implemented are supported as raw XML

• Adding new elements is simple -- just write a "view"

PKP’s Use Case

• Integrate Texture into our workflow wherever full text is prepared

• Open Typesetting Stack performs the first pass

OJS 3

Facilitating Adoption

• Authors have been hesitant to stop authoring in desktop apps

• OJS3 use case takes over at the first upload

• But you can still author from scratch or use Texture offline

Public Roadmap

PKP has sponsored two development rounds so far

In general, early feature set reflects "post-processing" use case

However, many other possibilities for development

Substance Consortium

Early support from:

• PKP

• the Collaborative Knowledge Foundation (CoKo)

• SciELO

• Érudit

Please Get Involved!

This is a project many of us have wanted for a long time, and it’s already near-production-complete.

Anybody want to sponsor improved commenting and reviewing features? They aren’t scoped yet!