Top Banner
Implementing a Full- XML Workflow: Why isn’t everyone doing it? Dana M. Compton Production Manager, PNAS Washington, DC www.PNAS.org
17

333 seminar2 danacompton

Apr 16, 2017

Download

Documents

Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: 333 seminar2 danacompton

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

Dana M. ComptonProduction Manager, PNASWashington, DC

www.PNAS.org

Page 2: 333 seminar2 danacompton

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

Page 3: 333 seminar2 danacompton

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

Page 4: 333 seminar2 danacompton

The usual challenges

Page 5: 333 seminar2 danacompton

So why do we bother?

Page 6: 333 seminar2 danacompton
Page 7: 333 seminar2 danacompton
Page 8: 333 seminar2 danacompton
Page 9: 333 seminar2 danacompton

… and there are five more pages just like this!

**workflow document created by Dartmouth Journal Services

Page 10: 333 seminar2 danacompton
Page 11: 333 seminar2 danacompton
Page 12: 333 seminar2 danacompton
Page 13: 333 seminar2 danacompton
Page 14: 333 seminar2 danacompton
Page 15: 333 seminar2 danacompton
Page 16: 333 seminar2 danacompton

Down the road for PNAS?

• Better search results

• Targeted RSS feeds

• More robust collections

• Additional delivery mechanisms

• New features, especially for Supporting Information

Page 17: 333 seminar2 danacompton

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