1. Building an Automated XML-Based Journal Production Workflow
ArticleExpress
Building an Automated XML-Based Journal Production Workflow
Provide an overview of what we will present – challenges associated with building a web-based, cloud-hosted journal article production system. While there have been many challenges over the past three years and have presented at other conferences about some of those challenges – JATS Con and Balisage where we discussed the challenges with track changes and collaboration - today we’ll focus on a few challenges specifically associated with creating a cloud-hosted journal article production system
Charles O’Connor
Technical Product Manager
Dartmouth Journal Services
Steve Haenel
Publishing Technology Specialist
Dartmouth Journal Services

2. The Sheridan Group Companies
The Sheridan Group (TSG)
Hunt Valley, MD
Dartmouth Journal Services (DJS)
Waterbury, Vermont
Dartmouth Printing Company (DPC)
Hanover, New Hampshire
The Sheridan Press (TSP)
Hanover, Pennsylvania
Sheridan Books (SBI)
Ann Arbor and Chelsea, Michigan
DJS
DPC
SBI
TSP
TSG

3. Dartmouth Journal Services
Peer Review
Editorial
XML-First
Composition
Electronic Deliverables
Online Hosting
Dartmouth Journal Services is focused on providing value-added publishing services and technology development for medium to large society, association, and university press publishers.
Customers: ~120
Journals: ~240

4. Traditional Publishing Process

5. Traditional Publishing Process
ArticleExpress Publishing Process

6. ArticleExpress Early JATS XML creation using Inera eXtyles
Automated XML-based composition system
HTML-based proof review and editing environment for use by authors, editors and publishers: ProofExpress
Granular change tracking system for tracking simple to complex changes, with accept and reject capability
Validating XML editor with advanced tools for managing the insertion or editing of highly structured elements

7. ArticleExpress Workflow7

8. Artemis Workflow Backbone

9. JATS XML Export

10. JATS XML Export

11. ArticleExpress JATS XML Editor

12. ProofExpress—Requirements
Maintain Publisher-Specific XML Start to Finish—Maintain not just valid XML but valid XML specific to the editorial and deliverables needs of multiple journals
For Authors
Easy-to -use interface—A majority of users will encounter the system for the first time
Word processor–like environment with a familiar feel, i.e., the presentation must resemble the online article presentation
Allow for collaboration among authors
Have the ability to view the article layout (PDF)
For Production Editors
Have a robust change-tracking system
Preserve author markup (foul matter)
Highly configurable
Journal style
Role access—corresponding authors, collaborating authors, Pes, publishers
Business rules—different functions for different tasks, such as Schematron validation or request revised figures

13. ProofExpress—Challenges
Track Change System—Changes, within changes, within changes, within…
Collaboration Feature
Customization
In-text author citations—Merge presentation with structure for complex editorial styles
Footnotes, affiliations, etc.

14. ArticleExpress JATS XML Editor

15. ArticleExpress JATS XML Editor

16. ArticleExpress JATS XML Editor

17. ArticleExpress Granular Track Changes

18. Obligatory Oxygen Screen Shot

19. Page Composition—Requirements
Fully Automated Composition—The system must be able to create pages without human intervention—Quickly!
Perfect or Near Perfect Page Presentation—Because we make all content changes in our XML editor and re-run pages, the pages must be perfect, or nearly so, as all layout changes will be lost at the next workflow stage.
Ability to Tweak Layout if Necessary—At the end of the workflow, we may want to make minor changes to the layout.

20. Page Composition—The Answer is . . .
but . . .

21. Page Composition—Challenges
Layout
Large Floating Elements
Unbalanced Columns
Versions Required for Proof, PAP, and Print
Workflow
Moving Assets to the Typefi Server
Retrieving InDesign Packages from the Server
Providing Information to Artemis Production Tracking

22. Meeting the Challenge—Scripting
Layout
Versions Required for Proof, PAP, and Print
Large Floating Elements
Unbalanced Columns
Workflow
Moving Assets to the Typefi Server
Retrieving InDesign Packages from the Server
Providing Information to Artemis Production Tracking

23. Layout Without Scripting

24. Layout With Scripting

25. Proof, PAP, and Print—Job Options

26. Workflow—Running a Job
<jobParams> <jobOption name="Final" projectName="DJS-RUP Pilot"> <xsl> <transform name="djs.xsl"/> </xsl> </jobOption> </jobParams>

27. Workflow—Zip and Ship
Package is FTP’ed to Artemis and Typefi Sends a Webservice Call

28. Workflow—Informing Artemis
Typefi Logs are parsed by Artemis, and Production is alerted about any warnings or errors

29. The Result Superior layout presentation Ability to tweak layout
Page production turnaround times shrink from hours to minutes
File transfers between Typefi and Artemis production management system
Granular error/warning information from Typefi logs informs Artemis workflows

30. Time for a Demo
We hope…

31. Questions?