Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Content Architecture for Rapid Knowledge Reuse-congility2011


Published on

A familiar content issue is gathering and integrating the knowledge of isolated subject matter experts (SMEs) throughout an organization into a robust content strategy. This presentation will give you some perspectives on how to engage your SMEs in contributing their knowledge as directly as possible in a structured format for ease of integration into a larger, more versatile content strategy. The first part of this presentation will lay out an architecture for a cross-organization, single source content strategy based on DITA (Darwin Information Typing Architecture) for this example. The second part of the presentation considers the use of that architecture for handling information flows during a disaster response. The system must allow people to respond appropriately to the rapid influx of disparate questions at the same time as receiving large quantities of information from multiple data sources of variable reliability. The use of structured content based on DITA can contribute to the effective use of information in a crisis.

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

Content Architecture for Rapid Knowledge Reuse-congility2011

  1. 1. Content Architecture for Rapid Knowledge Reuse<br />Don R. Day, Learning by Wrote<br />Doug Morrison, Mardi: Making a Real Difference Internationally<br />6/5/2011<br />1<br />
  2. 2. Agenda<br />Background of the problem<br />A proposed architecture<br />Implementation considerations<br />Scenario: Information flows in a disaster response<br />Summary<br />6/5/2011<br />2<br />
  3. 3. The Knowledge Paradox:<br />The greater the potential benefit of a particular piece of knowledge, the less available it becomes.<br />Reasons:<br />Visibility value to the owner<br />Anxiety (anticipating negative feedback, for example)<br />Responsibility (the need to answer questions)<br />Unaware of the value or need for this nugget<br />Busy, distracted, unwilling<br />“It’s too hard to comply with the content strategy.” (notes end up in hard to access formats)<br />Which leads to…<br />6/5/2011<br />3<br />
  4. 4. Content Obduracy (vsagility): When the quality or rate of information can’t keep up with the need<br />Dynamic situations such as emergency management in which timely, experiential information from the field can help improve response recommendations.<br />Time-constrained situations such as disease control where updated procedures must be quickly distributed to the public.<br />An effective, agile content strategy based on standards allows experts on both sides to quickly create and update information for urgent application in the field.<br />6/5/2011<br />4<br />
  5. 5. A “Rapid Response” Content Architecture<br />Standards-based: enable interoperability with other content creators and other tools<br />Open Source: where possible, leverage crowd-sourced knowledge for systems maintenance and features<br />Agile content: making use of structure, metadata, and semantics<br />Web-based: for wide availability, redundancy<br />Collaboration strategy: for open contribution<br />Topic oriented: for ease of:<br />Consistent authoring<br />Discovery<br />Reuse<br />Reassembly for publishing.<br />6/5/2011<br />5<br />
  6. 6. Collaboration architecture<br />6/5/2011<br />6<br />
  7. 7. The contributor/end user loop<br />“Editing in Browser” enables any reader to also be a contributor or reviewer.<br />Normally, the logistics center (or research center or command center) is where the subject matter expert assimilates incoming information to form new practices or policies. Yet,…<br />An end user IS a subject matter expert if they are able to report on information that is needed back at the center. (to wit: Zombie Survival Guide meme)<br />Collaborative systems enable this interaction and bring the content consumer into the contributor role.<br />As with Wikipedia, ‘user-generated content’ and ‘wisdom of the crowd’ are key to this architecture.<br />6/5/2011<br />7<br />
  8. 8. Opposing content paradigms<br />6/5/2011<br />8<br /><ul><li>Authority-oriented: managed by business rules and quality checkpoints.
  9. 9. Effectivity-oriented: driven by requests for news or information (Wikipedia is often cited; Twitter usage in the “Arab Spring” is a more recent and dramatic example of enabling change through information.)</li></li></ul><li>Proposed refinement<br />Intercept as many content streams as possible in DITA format<br />Content is directly useable in DITA-aware processing.<br />Content can be enhanced (made "intelligent") by adding:<br />Linking relationships<br />Metadata<br />Semantic markup (coaching, review/edit, etc.)<br />6/5/2011<br />9<br />
  10. 10. Why DITA for agile content?<br />Ann Rockley defines Intelligent Content (same idea) as:<br />“content which is structurally rich and semantically aware, therefore automatically discoverable, reusable, reconfigurable, and adaptable.”<br />XML technologies help that goal by:<br />Enabling content interchange with organizations across the company<br />Enabling content interchange with partners, contractors, OEMs<br />Enabling dialog between companies and customers<br />Facilitating process definition and execution within the company<br />DITA (Darwin Information Typing Architecture) is an XML application designed to provide many of these benefits.<br />6/5/2011<br />10<br />
  11. 11. Useful DITA Features<br />Reuse-oriented:<br />Reuse of Content (topic or element)<br />Reuse of Design (specialization)<br />Reuse of Processing (class-based processing)<br />Clean separation of competing concerns:<br />Content separated from Context<br />Content separated from Presentation<br />Rich provisions for Metadata<br />Conditional processing<br />6/5/2011<br />11<br />
  12. 12. The SME as a trusted author<br />Effective software for SMEs should be ubiquitous and accessible:<br />If they are used to using a word processor, enable those tools to produce DITA.<br />If they use wikis, give them a simple experience (Drupal and expeDITA).<br />If they are smartphone or tablet users, give them a tool that works well with soft keyboards or voice input.<br />And if they tweet, capture that!<br />Other collaborative interfaces for direct DITA :<br />Wikis & blogs<br />Forums<br />SMS text messages<br />Forms!<br />6/5/2011<br />12<br />
  13. 13. A simple, HTML form-based “task” editor might have the following required and optional fields, many of which correspond to the generated labels:<br />Task title: [input] *<br />Short description:[textarea]<br />Before you begin: [textarea]<br />About this task: [textarea]<br />Procedure: [textarea] *   More +<br />Results: [textarea]<br />Example: [textarea]<br />What to do next: [textarea]<br />SUBMIT *=required field<br />e.g., DITA from HTML forms<br />6/5/2011<br />13<br />
  14. 14. Getting content into DITA<br />Integrate DITA conversion to and from those native formats<br />Convert seamlessly from traditional sources:<br />"Data mining" for content in files, call center logs, chat logs, etc..<br />Use familiar desktop tools that are DITA-aware (Quark Xpress Author, Author-It, FrameMaker)<br />“What isn’t DITA” series explores “use what’s at hand” authoring: (and following)<br />6/5/2011<br />14<br />
  15. 15. Fostering contribution<br />Empower and encourage atmosphere of sharing<br />Reward/acknowledge mastery of markup goals<br />Provide wizards and other assistance for inserting metadata and markup<br />Devise "shell" templates to guide general flow of well-structured topics<br />Look to ease policies that impede spontaneous participation<br />Create and support communities around knowledge domains<br />Internal workgroups or meetups<br />Local DITA user groups<br />Worldwide DITA resources and forums<br />Training and reading resources<br />Make it easier to reuse knowledge (dita maps and conrefs)<br />6/5/2011<br />15<br />
  16. 16. Scenarios for disaster response<br />Discussion by Doug Morrison, Mardi: Making A Real Difference Internationally<br />6/5/2011<br />16<br />
  17. 17. Resources<br />About DITA, the standard:<br />OASIS DITA Focus Area,<br />OASIS DITA Technical Committee,<br />DITA forum,<br />DITA Open Toolkit, <br />Bob Doyle’s chronology of minimalism and topic oriented writing:<br />About collaboration:<br />The Evolution of Web-Based Collaboration at NASA & The Wiki-way Forward,<br />DITA for Drupal:<br />expeDITAContent Collaboration project,<br />6/5/2011<br />17<br />
  18. 18. Presenters:<br />Don Day (<br />Doug Morrison (<br />6/5/2011<br />18<br />
  19. 19. Questions?<br />6/5/2011<br />19<br />
  20. 20. Backup slides<br />6/5/2011<br />20<br />
  21. 21. 6/5/2011<br />21<br />Rethink playbook for nuclear accidents, IAEA chief urges<br />By the CNN Wire Staff<br />March 21, 2011 3:03 p.m. EDT March 21, 2011 3:03 p.m. EDT<br />(CNN) -- International regulators need to rethink their procedures for handling nuclear accidents in the wake of the crisis in Japan, the head of the U.N. atomic watchdog agency said Monday.<br /> The current framework for responding to emergencies dates back to the aftermath of the Chernobyl accident in 1986 and "reflects the realities of the 1980s, not of the 21st century," International Atomic Energy Agency chief Yukiya Amano said.<br /> "The speed at which information now travels and the huge volume of information in public circulation are among the most significant changes since then," Amano said. … "The responsibility of the IAEA is to provide authoritative and validated information as quickly as possible, but doing this under the current arrangements inevitably takes time and has limitations."<br />
  22. 22. Managing content in a collaboration space<br />What is a typical content lifecycle?<br />Preparation (analysis and design)<br />Initial document creation<br />Feedback and modification (test)<br />Readability testing and translation<br />Approval (publication/build implementation)<br />Subsequent updates and modification (support, enhancements)<br />6/5/2011<br />22<br />
  23. 23. Managing content, cont.<br />Options for turning original/curated content into reusable resources:<br />Rule-driven, heuristic tools (for example, using LegalZoom to create online wills, other DIY advice)<br />Specialist-vetted FAQs and How-To topics<br />Content migration services for legacy data<br />6/5/2011<br />23<br />