Envisioning the Global Information Experience
0 likes775 views
The document discusses the transition to an integrated content architecture using XML and DITA, outlining the benefits of scalable reuse and specialization across multiple levels of maturity. It emphasizes the importance of starting with the unique value of each organization to gain buy-in and improve operational efficiency. Ultimately, the document highlights how adopting such structures leads to significant returns on investment through streamlined processes and dynamic content integration.
Envisioning the Global Information Experience
- 1. Envisioning the global information experience Joan Lasselle and Amber Swope April 23, 2014 Presented by Data Conversion Lab, Inc.
- 2. Traditional approach Product content exists in multiple locations. Different schedules, processes, procedures, tools
- 3. The dilemma Customer confusion Operational inefficiency How do we move to a new model?
- 5. Where do you begin? Where do you begin? Many folks start with reuse; we want to suggest another approach
- 6. Change the conversation Start with the unique value of each organization
- 7. What’s in it for me? Get buy-in; it has to be better Understand where to gain leverage Does it free up time?
- 9. Move to XML Clear strategy and information architecture Structured content XML content DITA
- 11. Level 1: Topics A single file (document) can contain multiple topics Achieve simple single sourcing
- 12. Level 1: Return on investment INVESTMENT RETURN Migration to XML Generate multiple deliverables from a single XML source Store multiple topics in a single file Customize deliverables with conditional processing Savings from elimination of redundant content
- 13. Template Documentation 4/24/2014 Level 2: Scalable reuse Multiple maps reference topics in individual files
- 14. 14 4/24/2014 Level 2: Scalable reuse A single topic can appear in multiple maps
- 15. 15 4/24/2014 Level 2: Scalable reuse Enjoy the benefits of flexible reuse
- 16. Level 2: Return on investment INVESTMENT RETURN Separate topics into individual files for reuse Single source of truth for content Topic maps for deliverables Reuse topics in multiple deliverable maps and reuse content at all levels—element topic, and map Information architecture for reuse, metadata, and user access to deliverables Save time producing multiple deliverables
- 17. Level 3: Specialization All topic types are from Topic You can develop specializations from any topic type Achieve quality and consistency
- 18. Level 3: Return on investment INVESTMENT RETURN Adopt DITA standards Structure for creating content Develop specializations Custom elements for semantic value; custom structure for deliverables Reduce cost of integrating, translating, and publishing inconsistent content
- 19. Level 4: Automation & Integration Multiple users can create/share/use content from multiple repositories Multiple repositories contain multiple topics Achieve speed and efficiency
- 20. Level 4: Return on investment INVESTMENT RETURN Deploy Content Management System (CMS) Automating processes and workflow raises efficiency, reduce costs Deploy translation management system Metadata allows automation and customization Metadata model Reusable content across teams Lower translation costs
- 22. Level 5: Semantics Users can create/share/use information (content and data) stored in multiple content and data repositories
- 23. Level 5: Semantics Combining content and data enables dynamic publishing and creative mashups
- 24. Level 5: Semantics Dynamic, rich personalization of information
- 25. Level 5: Investment Return INVESTMENT RETURN Integrate content and data applications Personalized, integrated content and data Develop taxonomies Shared content and data across the enterprise, benefits from previous levels
- 26. Universal Semantic System All content becomes usable by all stakeholders Achieve universal knowledge management
- 27. Level 6: Return on investment INVESTMENT RETURN Change organizational mindset Adaptive network of integrated applications Recognize value of standards and collaboration Scalable architecture Define common goals Benefits of previous levels
- 28. Summary DITA is a flexible, scalable architecture = process and content improvement at each maturity level. Minimal investment = XML topics Maximum return = integrated, dynamic content and data provided by scalable architecture Benefits accrue at each level Learning and training content is an excellent investment for Level 4 DITA grows and evolves to meet your enterprise needs.
- 29. Questions Joan Lasselle Lasselle-Ramsay joan.lasselle@LR.com Amber Swope DITA Strategies amber@ditastrategies.com
Editor's Notes
- #9: Umbrella behind?Customersuccess umbrella.
- #12: MOVED BULLET TO SPEAKER NOTES: The shapes and colors indicate differ topic types.00:02-00:02/1In addition to chunking information into small units, DITA structures content by type. By default, DITA provides a base type, topic, and several more specialized types: task, concept, reference, and glossary entry. Each type has a specific structure that defines the valid elements that can exist within that type. For example, DITA does not allow you to create a <step> element in a concept topic because steps are parts of procedures and thus belong in task topics. Sample: An author for a government agency may need to produce audience-specific versions of a government policy. The author can write all the content in one file and apply conditional processing values to produce different versions of the policy for permanent and contract employees.
- #17: 00:09-00:09/1Released DITA TC specializationsBookmapGlossaryIn-progress DITA TC specializationsMachine industrySemiconductor Learning contentCS-Help Available specializations - sourceforgeAPI Reference CS HelpTroubleshootingTaxonomyMusic
- #18: 00:07-00:08/2Specialized types can inherit associated behaviors from their more generic ancestors, so even new DITA content types can be included in standard publishing streams, although it is common to extend processing to take advantage of some of the new markup. For example, a new content type for policy analysis might introduce sections for risks versus rewards, and processing could be extended to automatically create subheadings for the new section types.Sample: An insurance company wants to author all their content in XML to take advantage of the conditional processing and multi-channel output. They create specializations for each content type and automate their system to combine policy and procedure information with actual claim information to create just-in-time compound documents.
- #19: 00:09-00:09/1Released DITA TC specializationsBookmapGlossaryIn-progress DITA TC specializationsMachine industrySemiconductor Learning contentCS-Help Available specializations - sourceforgeAPI Reference CS HelpTroubleshootingTaxonomyMusic
- #20: Sample: The software division of a large technology company stores their content in a CMS, which allows all the teams in the division to reuse the content.
- #21: Efficiency:Workflow/translation
- #22: Sample; A financial services company can integrate financial data from a trusted source with quarterly report text and product marketing overviews written in DITA to create different combinations of year-in-review content for employees vs. investors.
- #23: Sample; A financial services company can integrate financial data from a trusted source with quarterly report text and product marketing overviews written in DITA to create different combinations of year-in-review content for employees vs. investors.
- #24: Sample; A financial services company can integrate financial data from a trusted source with quarterly report text and product marketing overviews written in DITA to create different combinations of year-in-review content for employees vs. investors.
- #25: Sample; A financial services company can integrate financial data from a trusted source with quarterly report text and product marketing overviews written in DITA to create different combinations of year-in-review content for employees vs. investors.