So you are finally planning that big move over to structured content. Great! You understand the benefits of reuse and what it means for your business.
But what do you do about the mountains of legacy content? Pack it all up and bring it with you? Leave it behind hoping you will never need to look at it again? Work in two worlds of structured (for the new content) and unstructured (for the old data) authoring?
In this one hour session we talk about the options you have for handling all of that old data. Like the Sherpa guides of Nepal, we can help you. In this session we will share with you what you will need to help you on the journey, what to plan for, and some hard won lessons learned along the way.
About Don Bridges
Don is the Manager of Commercial "Technical Documentation" projects at DCL. He manages DCL activities across divers markets such as aerospace, automotive, life sciences, manufacturing, semiconductor, software, telecom, and utilities. He's written several articles on the "business" aspects of implementing XML and is a frequent conference speaker.
About Data Conversion Laboratory
Established in 1981, Data Conversion Laboratory (www.dclab.com) has substantial expertise in complex conversion projects, including eBooks, TechDocs, Defense, and Libraries. They have experience with all the key DTDs, including DITA, ePub, MOBI, S1000D, ATA, NLM, DocBook, and TEI. They wrote the book, literally: They wrote the data conversion chapters in The XML Handbook and Columbia Guide to Digital Publishing.
About Single-Sourcing Solutions
Single-Sourcing Solutions (www.single-sourcing.com) is an elite PTC partner specializing in Arbortext products. With over a decade’s experience with the Arbortext toolset and in the practical development and deployment of mission-critical, custom XML development, Single-Sourcing Solutions has the expertise required for successful dynamic information delivery. We are very active in the global Arbortext community and related information development communities.
Watch the Video
Recorded: August 2011
View the slides
Reviews
Read the review of this session by Ugur Akinci on Technical Communication Center.
Tweet Roundup
In case you missed attending the session live, the event had a live Twitter stream.
Read the tweets
| SingleSourcing Webinar Today "Conquering the Mountain of Legacy Data" 10 AM Pacific/US with Data Conversion Labs & Don Bridges |
| SingleSourcing #S3IWebinar starting w/ @dclaboratory We will be high volume for next 60 mins |
| SingleSourcing #S3IWebinar @dclaboratory D.Bridges: DCL celebrating it's 30th year of finding themselves in complex data conversion projects |
| SingleSourcing #S3IWebinar @dclaboratory D.Bridges: Situations where XML is a good idea, what the options are, and how to plan for it.. and a few tips too |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: why xml? less publishing centric/complex than SGML, more robust than HTML with wider bizcom acceptance |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: XML is a good fit if you have tecnical docs, need print + electronic, fast, frequent update, versions.. |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: XML also key if you have print on demand |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: XML usu shw postive ROI - open standard, lots of vendors (relatively easy to switch) interchange simple |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: want an XML ROI calculator? Reply to the tweet |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: DITA is single source authoring, like lego blocks to go build anything you want |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: What does it take to build an XML system? Need 3 things: CCMS, delivery aspect, authoring tools |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: BTW, there's also conversion: how do you fill the tank of content? |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: What else do you need? Someone who's been there who can guide you. A Sherpa |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: What else do you need? Training. Get past the technical aspects of XML |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: What else do you need? Some way to get your content into XML |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: two ways to get your content converted: new content in XML/old content in old sys OR convert old stuff |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: very few writers have the clairvyance to author content thinking it will EVER be converted in future |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: it's def more fun to author anew, but not necess faster or cheaper |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: but ask yourself -- do you need to convert it? |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: 3 options: convert nothing ($0, Delay ROI), convert everything ($$$ low ROI), convert some (max ROI, $) |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: convert with intelligence - convert docs that are favorites, frequently used, long product lives, |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: when in doubt, start in the present and work backwards deciding on what to convert |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: Some people believe Automation not possible; some believe it is; some believe cheap labor 1st try works |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: What about rewriting? Think about cost - minimalism, simplified Eng, topic-based - Typically $60/pg |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: Rewriting typically takes 1 hr/pg -- do the math |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: rewriting may be technically the right way to go, but there might be a higher value option |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: if you've only got a couple hundred pages, cut and paste works, right? |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: Humas are rarely 100% correct and consistent in performing tagging |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: STC presentation of CSG Systems in-house conversion 11K pgs - 6 months & 4K hrs http://bit.ly/nBORX9 |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: If you just cannot release the content outside the confines of your building & have the time/$ do it |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: SAAS: really requires consistent, well-styled, maps well. You do manual clean-up before AND after |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: be sure to budget in the cost of clean-up |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: Oursourced conversion - no surprises, know $, schedule, quality up front. |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: out-sourced conversion typically turn-key operation for one-time events |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: One-Time Event: you intend to stay in XML forever. Often happens for aquired contnet |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: conversion can be topic-sourced or book-sourced |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: topic-sourced - analyze similar content and rewrite - manual process, maximized reuse |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: I discourage making paragraphs their own topics |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: book-based conversion: designate topics by type based on heading level, automated, limited reuse, |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: book-basd conversion when topics dnot need reauthoring right away, can do after conversion |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: there are 3 things to do before converting content 1) harmonize content - spelling/punct differences |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: content faux pas: tables created without table editor. |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: content faux pas: references to pages or locations |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: graphic overlays on tables |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: content faux pas: graphic overlays on tables -- think about your other formats |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:content faux pas: extra spaces for composition -- only applies to Print Presentation |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:XML separates Content and Format. Need to think about that when prepping for conversion |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:Style over-rides -- manual applications that can't be tracked easily |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:Content Model Violations easy when you're in a non-structured environment; hard to get right |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:know your new content model and refit your content before conversion |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:Look for those procedures authored as tabled #DITA content model violation |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:notes authored as tables another #dita content model violation |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:Other dita content model violations: http://bit.ly/mSADx0 Making Friends with Your DITA-Unfriendly Documents DITA is a hot topic in the 'Tech Docs' arena, and for good reason. DITA is an open standard that addresses many of the needs of technical documentation producers - most notably content reuse needs. |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:Things to remember? Be able to Justify ROI to management for XML system |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:Make sure your process is scalable - do a pilot or two or three |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:know your new content model and refit your content before conversion |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:Hire a Sherpa to talk to other people in the industry and to learn from their experience |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:notes authored as tables another #dita content model violation |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:You don't know what you don't know -- the unknown unknowns -- learn from others, hire someone |
| dclaboratory RT @SingleSourcing : #S3IWebinar @dclaboratory D.Bridges: Make sure your process is scalable - do a pilot or two or three |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:Be prepared! Train content experts. Working with XML is DIFFERENT. Working with DITA is MORE DIFFERENT |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:invest in tools that are XML-enabled and designed to enhance, not restrict, the process |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:let the tool do the work so you don't have to |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:use robust, comprehensive DTDS and purge the instinct to say "how does it look, how does it look" |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:Go to "what does it say" rather than "how does it look" |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:do your homework, ROI is hard to identify initially.. |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:DCL celebrating it's 30th year of finding themselves in complex data conversion projects |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:know what you know, and get help for what you don't |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:train one person to super-user status and have them train the rest |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:It can be as easy as, all updates go in at 2 AM and the website is updated at 2:01. It can happen |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:Resources: http://bit.ly/nDjN68 and http://bit.ly/oufovS |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:DCL's #1 article: how to convert from Quark |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:Questions ? Lots of good ones... |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges:if you've only got a couple hundred pages, cut and paste works, right? http://bit.ly/o1y4Ca |
| Single-Sourcing #S3IWebinar @dclaboratory D.Bridges: Thanks everyone for attending. |
| Single-Sourcing #S3IWebinar @dclaboratory L.Fraley: Next session: what single source information sharing really means & how to set about accomplishing it |
| CedricsMom Single-Sourcing @dclaboratory Thanks for having the webinar. |
| CedricsMom Single-Sourcing I'm a neophyte trying 2 understand SS, CM, DITA & XML & how they all work 2gether. Your webinar increased my understanding. |
You might also be interested in...
From FrameMaker to FrameMaker, Growing a DITA-Capable Department
Larry Owen and Liz Fraley
Tools and Development: Courtship, Commitment, and Relationship Goals
Dawn Stevens, Val Swisher, Sarah O'Keefe, and Liz Fraley
Topic Writing for Everyone
Janice Summers, Single-Sourcing Solutions
Key concepts
data conversion, make your business case, topic based writing
Filed under
Single-Sourcing Exclusive, Webinars