Implementing a Full-XML Workflow:Why isn’t everyone doing it?

Dana M. ComptonProduction Manager, PNASWashington, DC

www.PNAS.org

About PNAS: A single title, but…

• Broad, multidisciplinary subject matter

• Complex production workflows and editorial policies

• Nearly 4,000 research articles per year, ~23,000 pages

• More (and more, and more) Supporting Information every year

XML from our peer review system• Customization• Ongoing development• In-house and vendor expertise

XML to our online host

• We rely on our vendors• Conversion does not always happen at the

same point in the process• Basic knowledge in-house is crucial

The usual challenges

So why do we bother?

… and there are five more pages just like this!

**workflow document created by Dartmouth Journal Services

Down the road for PNAS?

• Better search results

• Targeted RSS feeds

• More robust collections

• Additional delivery mechanisms

• New features, especially for Supporting Information

Some advice

• Make your XML part of your project plans – early on!

• Involve all parties in the conversation

• Consider what else you *might* want to do

• Focus on the end goal and leave the technical stuff to the experts