Tracking Changes to JATS XML in an Online Proofing System

1. Tracking Changes to JATS XML in an Online Proofing System

2. Dartmouth Journal Services

3. Content Services for STM Publishers

4. The Sheridan Group Companies The Sheridan Group (TSG) Hunt Valley, MD Technology Lab (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

5. The Question • If the online journal is the journal of record, then how come almost all production workflows only provide PDF proofs? • PDFs cannot incorporate, without significant cost, the elements of tomorrow’s scientific articles; (i.e., multi-media content, data linking, semantic enrichment, supplemental material) • HTML presentation is the future of science articles, even if PDF is the file of record today. HTML5 alone offers an expanding array of features that will improve presentation in the browser (i.e., MathML support, offline caching, native browser support for multi-media, etc.)

6. The PDF-Based Workflow Correction Cycle

7. Project Team Charles O’Connor Workflow Automation Specialist ArticleExpress Project Manager Antony Gnanapiragasam Workflow Automation Specialist ArticleExpress System Architect Tina Fleischer Technical Support Specialist ArticleExpress Quality Assurance Mike Hepp Director, Technology Strategy ArticleExpress Project Leader

8. The Solution Web-based Proofing, Editing, and Review System and Automated XML-Driven Composition

9. Online XML Editing Correction Cycle

10. Building Support for the Idea DJS

11. Collaborative Online Editing Environment Publisher Co-Authors Production Team Corresponding Author Production Editor

12. The Technical Challenge for Track Changes • For a browser-based XML article proofing system to function well in a journal publishing workflow, it must have a comprehensive change tracking capability: • Multiple users interacting with the system and document in the same workflow step • The ability to act upon the changes, regardless of what role/actor made them and regardless of what order they were inserted • Allow editors to accept or reject changes without breaking the underlying XML

13. Underlying XML Editing Environment

14. XML Editing Limitations • Although the XML editing environment choice was important, there were limitations that needed to be overcome through custom development: • No easy way for authors to add more complex XML structures • Change tracking – limited to insertions and deletions only

15. Sequential Editing 1 2 3 4 5 6 XML 4 XML 1 XML 2 XML 3 XML 5 XML 6

16. Parallel Editing 2 XML 2 4 XML 4 Merge 8 9 5 1 XML 1 XML 5 XML 7 XML 8 XML 9 3 XML 3 6 XML 6

17. Limitations of XML Differencing Approach • The Longest Common Subsequence Problem • We may get an accurate representation of the difference between the original and the edited versions of the text, but it may not tell us what the author actually did.

18. Limitations of XML Differencing Approach • Before: “I say cheese to you” • After: “I say oh pleeze to you” • Diff: “I saycohpleesze to you”

19. Limitations of XML Differencing Approach • Loss of Granularity • Attempting to overcome this problem by applying a cleanup parameter or otherwise grouping changes can lead to a loss in the granularity of changes. • Changes within changes will not be marked individually as changes, which is a problem if they should be dealt with discretely.

20. Limitations of XML Differencing Approach • Loss of Granularity • Before <p>hello world</p> • After<p><italic>hello silly italic world</italic></p>

21. Custom Elements • Custom Elements • Use information from event handlers in SDL LiveContent Create to create custom track changes elements and attributes. • Edits can be performed in a number of ways we needed different elements to capture these edits

22. Custom Elements Custom Elements

23. Custom Elements • Custom Elements • Example of formatting.

24. Random Access Sequential Editing 5 4 1 2 7 8 9 XML 4 XML 1 XML 3 XML 5 3 6 XML 2

25. Change Tracking Solution • Solved by designing and developing: • Comprehensive change tracking • Rule engine that protects the structure of the XML by governing the order of acceptance and rejection of edits • Denormalizationof nested elements to granularly expose all edits

26. Rule Engine for Accepting/Rejecting Changes

27. ProofExpress – Review Mode

28. Rule Engine for Accepting/Rejecting Changes • Problem: Order of decision making… • If the system does not enforce an order of decision making, then the process may break the XML.

29. Order of Decision Making Solution

30. XML Denormalization • XML Denormalization • For the accept/reject rule engine to work properly, the track changes tool must show how changed nodes are nested within each other. • As per the rule engine, insertions and deletions should always be the outside changes when they occur in relation to changes in formatting.

31. XML Denormalization • XML Denormalization • Formatting nodes

32. ArticleExpress Demo

33. Questions?