XML for the smaller publisher Cambridge University Press Case study - PowerPoint PPT Presentation

1 / 16
About This Presentation
Title:

XML for the smaller publisher Cambridge University Press Case study

Description:

CUP books before copy editing. CUP journals after copy ... Get your customers' on board. Small scale experiments? Would we do it now (if we hadn't already) ... – PowerPoint PPT presentation

Number of Views:579
Avg rating:3.0/5.0
Slides: 17
Provided by: andy224
Category:

less

Transcript and Presenter's Notes

Title: XML for the smaller publisher Cambridge University Press Case study


1
XML for the smaller publisherCambridge
University Press Case study
  • Andy Williams
  • Manager Content Services
  • AcPro Production Director - Europe

2
Context Academic Professional books
  • Approx 1500 new titles per annum
  • XML first workflow for as many as possible
  • not author-supplied LaTeX
  • Probably about 65 of the frontlist
  • Since 2001
  • Single dedicated Academic books DTD (CBML)
  • All front list to Adobe eBooks, bulk of XML
    titles to Mobi/HTML eBooks

3
Books workflow
4
Context - Journals
  • 231 journal titles approx 1,000 issues/annum
  • 204 as XML workflow for full text
  • All require XML headers for online platform
  • Scanned archive references as XML
  • Dedicated journals DTD (informed by NLM but more
    granular) CJML
  • NLM used as the transfer format to hand to our
    online platform plus 3rd parties

5
Journals workflow
6
Context what weve already changed
  • Single DTD for books and journals didnt work
  • Single DTD for books doesnt really work
    (monographs, textbooks, MRWs)
  • Standards are open to interpretation (e.g. NLM)
  • XML editing environment make more user
    friendly
  • Clear, informed, decisions need to be made

7
Decision points
  • Why what are the objectives?
  • What do you want to get?
  • When in the workflow is best for you?
  • Where will processing control be handled?
  • Who will do the work?
  • How what workflow, tools and processes?

8
Why
  • Benefits to the production process
  • End (and interim) deliverables
  • Direct -- XML
  • Indirect -- linking within PDFs
  • Buy in and understanding
  • XML is not a magic bullet
  • Theres XML and theres XML

9
What
  • Bespoke DTD
  • Standard DTD (TEI, docbook, NLM)
  • No DTD
  • Schema
  • How many?
  • Who to maintain?
  • Just XML? Application files, style files?

10
When
  • At start, early, late or back end?
  • CUP books before copy editing
  • CUP journals after copy editing (cf RSC)
  • Constraints
  • Editorial tools
  • Tradition
  • Authors
  • Additional QA
  • costs

11
Where
  • In house
  • Out house
  • Offshore
  • Map where you stand today, future reality and
    draw a route plan
  • Take it steady

12
Who
  • XML coding
  • Typesetting/pagination
  • QA
  • Archiving
  • DTD maintenance
  • Associated tools automated QA and
    transformations

13
How
  • Put it all together
  • Do you predicate the supplier workflow and tools,
    or just the outputs you want?
  • InDesign and InCopy
  • Word templates
  • LaTeX 3B2
  • Return to beginning why? Monitor and review and
    change

14
Other lessons learnt
  • Drivers and buy in
  • Disruptive
  • Traditional publishing models may not be ideal
  • Support and infrastructure
  • People and cultural issues bigger than technical
    issues
  • Still need a decent user-friendly editing tool
  • Dont forget the non-XML titles

15
Conclusions
  • Full cost/benefit analysis first
  • Be clear on the implications (technical resources
    etc)
  • Automated not automatic
  • Get your customers on board
  • Small scale experiments?
  • Would we do it now (if we hadnt already)
  • Journals definitely
  • ELT trying to catch up
  • Academic books perhaps more selectively

16
Questions?
  • Andy Williams
  • Manager Content Services
  • AcPro Production Director Europe
  • awilliams_at_cambridge.org
Write a Comment
User Comments (0)
About PowerShow.com