How Wiley Uses Word to Invite Authors, Engage Editors, Improve Production, and Put XML at the Source...

Getting to the Source:How Wiley Uses Word to Invite Authors, Engage Editors, Improve Production,and Put XML at the Source of Its Content

Frank Grazioli | Director, Production TechnologyJohn Wiley & Sons, Inc.Start With XML, January 13, 2009

Who Are We

Production Technology Group– Improve the publishing process through technology: digital workflow, QA

and archiving, e‐books, XML– Small team with backgrounds in book/journal production, editorial,

graphic arts/design, content technology

Wiley Professional & Trade Group– 1,200 US publications; globally >2,000; 70/30 consumer/professional– Very simple to very complex content– 80% of publications in XML workflow– >200 Production and Editorial staff; freelance copyeditors; authors– We are delivering XML for

• Aggregators, online learning, websites• Global licensing and custom publishing• Typically full‐book product in WileyML 2.1—proprietary content model

and book DTD

01/13/09 2Frank Grazioli, WILEY | StartWithXML

Workflow


MS Word Template Is Foundation for Workflow

• No extraordinary technical skill required• Decoupled from other technology: able to adapt for evolving business need• Controlled list of styles covers most content elements

– Structural: sections, headers, tables– Semantic: terms, expressions, feature types

• Clean UI: basic styles and extended menus for advanced use• Approximates our XML content model—requires some training• Macros speed formatting and cleanup of manuscript to help workflow• Production supplies some metadata to guide print layout


01/13/09 Frank Grazioli, WILEY | StartWithXML 5


• Word’s XML not deep enough to support our DTD• Compositors convert our Word to XML and provide additional tagging:

– Bibliographic and rights metadata sourced from Wiley systems– Linking between elements (exhibits, sections)– Conversion of some expressions to entities; some math to MathML– Additional tagging generates navigational elements such as chapter‐level

TOCs (not part of the edited ms)• We don’t prescribe paging platform—whatever is most efficient/cost‐

effective—but this does affect QC (20‐30 minutes to hours per ISBN)• At the end of the process compositor:

– Extracts and delivers WileyML– Generates new MS Word manuscript templated with our styles

Compositors Transform Word to XML


What’s Been Working for Us

• Collaboration between Editorial and Production to establish styles• Group training—Production and Editorial together—fosters community• We focused early effort on series books• Flexible author “recruiting” strategy: 20‐60‐20 rule• We put our message, tools, and documentation “out there” (website):

downloads, style guides, cheat sheets (“placemats”)• Monthly roundtables to resolve technical, workflow, usage issues• Upside

– Efficiencies in workflow (staff and freelancer skills normalized; able towork across product areas)

– More use of standardized book layouts and series (saves $)– Clean ms at the back end– Process feels “normal” with flexible points of entry: authors, editors,

copyeditors


Further Advice for Best Prac7ces

• Use styles or tags meaningful to content users• Avoid “print” language if you intend to deliver more than print—or support

variant language with your XML• Understand how your compositors work with your DTD: It will affect your own

QA efforts and your ability to reuse the content the way you expect to– Non‐native use of our DTD means more thorough QA by us because our

XML must be backed out of theirs– Parsing/validation not equal to good usage (tag correctly from start)– Completeness: if your XML model “chunks” differ from ms– Entities: as your usage requires?– Tags misapplied to mimic print: drop/small caps; ornaments– Linking: within and across publications: does your DTD support them?– Overtagging : <term><i>modified adjusted income</i><term>

final


Get out of a “Box”:15 Standard Feature Types that Mean More to Your XML

“Box” and “sidebar” define appearancebut do liKle to describe purpose.

In our process:

- Feature types are selected from adropdown menu

- Author or editor create 7tle(s)

- Can take on any design: Compdirec7ve and design specifica7on

- Retain their underlying values in theXML as metadata


Choosing a Feature Type

Feature Type Defined Might be 7tled

ac3vity asks the reader to applyideas from the exercise,prac3ce, assignment,ac3vity, or body text toformulate solu3ons or toac3on points prove theconcepts

exercise, prac3ce,assignment, ac3vity,ac3on points

caseStudy situa3ons or events, real orhypothe3cal,that illustrate, amplify, orargue themesand ideas in the body text

case study, project,scenario, tale, RealWorld Scenario, situa3on,vigneAe, caseextract, project case



Where To?

Continue to evaluate/benchmark the process– Time/resources for content outside of the workflow– UK, Asia, Australia, Canada– Need OpenOffice, Word 2008– Current book DTD will give way to book‐journal schema—simpler model

but will need to remap Word stylesBeyond Full‐Product XML: Travel “Chunks and Nougat”

– Objec7ve data “chunks” that are places and events of interest (hotel orconcert)

– Prose wraps the places and events in a point of view (thriW seeker or familytraveler?)

– An ontology of audience interests to capture par7cular associa7ons betweenthe two content types to model products or customize content deliveries

External taxonomies (standardized key terms) for discipline‐ or industry‐specificrelevance: GAAP/IFRS, Engineering, Architecture, Psychology


Date post:	29-Nov-2014
Category:	Education
Upload:	toc
View:	4,648 times
Download:	1 times

How Wiley Uses Word to Invite Authors, Engage Editors, Improve Production, and Put XML at the Source...

Education