RE: [jats-list] How/When do you produce a JATS-XML version of you publication within your publication workflow

[Einbrodt Matthias <Matthias.Einbrodt@xxxxxxxx>]

Hi Kevin,

thank you very much for your thorough answer.

> You've already decided to use OJS, so the first question is whether to
bother
> producing XML at all.  You could use OJS in a way that the "layout" stage
does
> not use XML at all; instead, a typesetter uses Word, LibreOffice, InDesign,
or
> another desktop-publishing program to create HTML and PDF versions of
> each article for delivery through OJS.

[Einbrodt Matthias]
Indeed, that could be an option as well. Since we don't have the manpower and
brains to operate InDesign or another DTP we would have to use Word or Open
Office to copyedit and layout the authors manuscripts in such a way that we
can create a printable PDF version of the article directly out of Word or Open
Office.

Regarding the creation of the Html representation of the article one would
have to rely on the built in "Save as Html" functionality of MS-Word which I
heard produces a lot of unnecessary markup. However, from what I read it seems
to be possible to use some tools (e.g. CKEditor - http://ckeditor.com/) to
filter out the overhead and adapt the Html-markup to a suitable form. But to
be honest I really don't know if this really works. Does anyone have any
experience with that?

> However, it seems you are interested in having an XML workflow, perhaps
> not only for the ease of deriving HTML and PDF but also because it will
allow
> you to produce other formats (EPUB, MOBI, etc.) and to do things like
> provide the XML to anyone who wants to do further manipulation or data
> mining on journal articles.  While it takes more work to set up such a
> workflow than if you did something without XML, there are long-term
> benefits.

[Einbrodt Matthias]
Exactly. In the long term we also would like to produce EPUB and MOBI.
However, we'll still have a long but hopefully not so bumpy road ahead of us.

> Next is the choice between TEI and JATS.  If you're committed to using OJS
> (as opposed to having your journal hosted on Revues.org, which uses TEI),
> then you'll want to choose JATS.

[Einbrodt Matthias]
We also considered Lodel, but the documentation seems to be entirely written
in French. :-(
Furthermore the support for JATS / NLM regarding tools/scripts that convert it
to other formats seems to be more advanced.

There is a plugin included with OJS called
> "XML Galleys" that allows an NLM Blue version 2.3 document to be loaded
> into OJS and then dynamically rendered as HTML and PDF.  See:

[Einbrodt Matthias]
Thank you for the hint. I will check it out.

> Commercial publishers generally send edited manuscripts to offshore
> vendors who convert to XML and/or do typesetting.  If you use OJS with the
> XML Galleys plugin, all you need is conversion to JATS.  There are many
> vendors that will do this for you.

[Einbrodt Matthias]
Does anyone know how much that would cost? I suppose it depends on the volume
and the complexity of the article/publication, but are there some rough
estimates?

> a) Lemon8-XML (which is no longer being actively developed) essentially
> involves applying styles in a word processor.

[Einbrodt Matthias]
Does anyone have any experience with that software?

> b) Microsoft's Article Authoring Add-in for Word (which is a "Technology
> Preview" -- essentially, software in beta, but which was released in June
> under an Apache license: http://authoring.codeplex.com/ )

[Einbrodt Matthias]
I hope to test the plugin really soon and hope to share my thoughts here. But
if anyone has already tested this Add-On it would be great to get some
feedback on what you think about that.

> c) the Norm module of mPach ( http://www.lib.umich.edu/mpach ), which is
> being actively developed, also involves applying styles in a word
processor.
> In fact, mPach is planned to work with OJS so that you can send manuscripts
> from OJS directly into the Prepper interface (which includes Norm) for
> creation of JATS.  So your choice of OJS will position you to take advantage
of
> these mPach components once the software is released.  For now mPach
> developers are focusing on the DOCX format but hope to support ODT in the
> future.

[Einbrodt Matthias]
That sound really interesting. Can you tell me more about the timeline of the
project? When can a first release be expected?

> Hope that helps,

[Einbrodt Matthias]
It helped a lot. Thanks again very much Kevin.

Best regards, Matthias