1. 3.0: An XML Workflow Upgrade
Presenters:
 Michael Haskell, Manuscript Editor and
Electronic-Manuscript Administrator, Columbia
University Press
 Scott Beebe, CMS/Data Analyst, Oxford
University Press

2. 3.0: An XML Workflow Upgrade
This introduction to the CUP Word Editing System
will include:
▶ About Columbia University Press
▶ History of the editing system
▶ Editing in Word and XML conversion
▶ The 3.0 upgrade: Reasons and features
▶ A demonstration of the system
▶ Future directions

3. More than just copyediting . . .

4. Columbia University Press
▶ Established1893
▶ 160 new book titles per year
▶ Diverse publishing program

5. History of the Editing System
▶ The Bronze Age
▶ Word and XML

6. Word and XML Workflow
▶ System of Visual Basic macros and
templates
▶ Originally developed by an outside vendor
▶ Upgrade done in-house to meet specific
needs

7. Attaching the Templates

8. CUP Initial Prep Options

9. Styled Text

10. Word Styles from the Menu Bar

11. Styling Toolbars

12. The Upgrade: Reasons and
Features
▶ Inefficient markup led to poor
communication with designer
▶ Lack of validation step for XML resulted in
problems with InDesign
▶ Limited library of special characters
disrupted workflow

13. Effective Communication of
Document Structure
▶ Strengthening of data model
▶ Consensus between editors and designers
▶ Enforcement via validation

14. Validation
▶ Identification
of problems before content
reaches design phase
▶ Departmental buy-in

15. Special Characters
▶ Original system used entity codes used to
represent special characters (ā = ā)
▶ Drawbacks
 Limited to predefined set of entities
 Editors creating undefined entities on the fly (&Twithudot;
for Ṭ)
 Undefined entities cause errors in typesetting
application (&Twithudot; = InDesign error)
 Workarounds removed MSS from standard workflow

16. Special Characters in Arial Unicode
MS Font

17. So . . .
In the original system the word Qurʿān would
need to be represented as:
Qur&ayn;ān
In the new system it can simply be:
Qurʿān

18. Demonstration of CUP Editing
System

19. Future Directions
▶ Further process automation
▶ More user-friendly XML processing/editing
▶ Staff and freelancer buy-in
▶ Emphasis on Press-wide workflow

20. Thank You
Michael Haskell
 mh2100@columbia.edu
Scott Beebe
 scott.beebe@oup.com