Introducing Texture: An Open Source WYSIWYG Javascript Editor for JATS
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
Title |
| |
Title of Series | ||
Number of Parts | 36 | |
Author | ||
License | CC Attribution 3.0 Unported: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
Identifiers | 10.5446/51339 (DOI) | |
Publisher | ||
Release Date | ||
Language |
Content Metadata
Subject Area | ||
Genre | ||
Abstract |
|
1
8
9
18
20
31
35
00:00
Lecture/Conference
Transcript: English(auto-generated)
00:00
I'm Alex Garnett. I don't need this mic do I? I Need the mic, okay I'm Alex Garnett, and I want to talk to you all about texture our new WYSIWYG jazz editor This work also had major contributions from Juan and Kasim so not to be remiss It's just my name on the talk, but they've been a huge part of this project
00:24
So as you all may know for the past several years. We've been working on a project called the open typesetting stack Oh It comes out yeah, okay Which until very recently was a fully unsupervised
00:42
automatic parsing solution It was never going to be perfect. We claimed that for a little while We didn't stick to it very long because it wasn't a very plausible lie but very Important to get the parsing as good as we could because we were wary of trying to take on the Huge project of making a good WYSIWYG editor to go from 80%
01:04
Automatic best-in-class open source parse from word or PDF to JET's PubMed Central XML Going from there to 100% we can publish this It's actually like production quality better than the status quo of outsourcing your XML typesetting
01:20
We wanted to actually get a good Editor in there to close the gap. We were afraid to do it ourselves because the risk of making a Chocolate orange and lettuce no butter bodega sandwich was too great, right? If we want to make something we want to actually do it, right? We don't want to make it like a sociopath who doesn't know what a real sandwiches and you know again absent actual
01:46
You know UX UI design for a WYSIWYG editor these things can happen So we're very pleased to announce That as of last week, we have a very new release of texture, which is a new WYSIWYG JATS editor
02:02
from Substance the developers of the eLife lens who for those who have seen that that's the default XML viewer in OJS 3 Provides a complete full-text XML workflow. We've integrated it into OJS 3 with a plugin It works standalone and we hope this will encourage a transition away from word typesetting
02:23
You can basically get your document into JATS XML and edit it Even more easily than you could in Word earlier on in the typesetting process no more like Manipulating word tables until the very end when you send it off publisher and they send it off to somebody else And it's a whole waste of effort. This is you know a way forward we hope
02:43
It's a lightning talk. So I have just this slide with a lot of features on it now So we can kind of look through these I can do a demo later on if anybody wants one But it's got things like configurable views we can hide certain elements from Authors or from editors to make the interface better suited to either marking up a document or authoring from scratch
03:03
We can act as a guide to tagging, you know, like hey abstract goes here or a plain authoring environment It can do double duty There can be an offline version pretty soon. It's a JavaScript app. We can just package it So for anybody who's hung up over kind of authoring into a browser, you've got to work around for that
03:20
We can import any valid JATS including, you know the 80% output of our parser or any article currently in PubMed central for example and Export along JATS for our conventions So it's JATS but it's kind of a opinionated subset of JATS to make a huge XML schema more usable It supports a collaborative editing like Google Docs
03:41
So you can actually have your simultaneous editing feature which is again something else word does not have we're better than word now It stores weak links to external services locally So that if you pull in a DOI from cross ref and for whatever reason the meta that it changes remotely It'll get pulled in automatically So there's no just pulling down raw citation text strings
04:01
It supports raw XML editing. So it replaces oxygen, right? You know if you have an XML professional editor who's used to doing their work in oxygen They can have a nice WYSIWYG 95% of the time before the 5% fallback when they want to change an attribute in one tag They can still do that. So really fits existing workflows
04:20
Enforces context the editor cannot produce invalid JATS. This is something again that you know, it doesn't really work in word land Anytime you're changing a section heading you're indenting it that actually nests the section in the article So good stuff. It's very smart We hope and it is not a chocolate orange no butter lettuce would like a sandwich. Thank you