Published on June 28, 2011
Content Architecture for Rapid Knowledge Reuse
Don R. Day, Learning by Wrote
Doug Morrison, Mardi: Making a Real Difference Internationally
Agenda Background of the problem A proposed architecture Implementation considerations Scenario: Information flows in a disaster response Summary 6/5/2011 2
The Knowledge Paradox: The greater the potential benefit of a particular piece of knowledge, the less available it becomes. Reasons: Visibility value to the owner Anxiety (anticipating negative feedback, for example) Responsibility (the need to answer questions) Unaware of the value or need for this nugget Busy, distracted, unwilling “It’s too hard to comply with the content strategy.” (notes end up in hard to access formats) Which leads to… 6/5/2011 3
Content Obduracy (vsagility): When the quality or rate of information can’t keep up with the need Dynamic situations such as emergency management in which timely, experiential information from the field can help improve response recommendations. Time-constrained situations such as disease control where updated procedures must be quickly distributed to the public. 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. 6/5/2011 4
A “Rapid Response” Content Architecture Standards-based: enable interoperability with other content creators and other tools Open Source: where possible, leverage crowd-sourced knowledge for systems maintenance and features Agile content: making use of structure, metadata, and semantics Web-based: for wide availability, redundancy Collaboration strategy: for open contribution Topic oriented: for ease of: Consistent authoring Discovery Reuse Reassembly for publishing. 6/5/2011 5
Collaboration architecture 6/5/2011 6
The contributor/end user loop “Editing in Browser” enables any reader to also be a contributor or reviewer. 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,… 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) Collaborative systems enable this interaction and bring the content consumer into the contributor role. As with Wikipedia, ‘user-generated content’ and ‘wisdom of the crowd’ are key to this architecture. 6/5/2011 7
Opposing content paradigms 6/5/2011 8 Authority-oriented: managed by business rules and quality checkpoints.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.)
Authority-oriented: managed by business rules and quality checkpoints.
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.)
1. Content Architecture for Rapid Knowledge Reuse Don R. Day, Learning by Wrote Doug Morrison, Mardi: Making a Real Difference Internationally
View 3852 Content Architecture ... Get the professional knowledge you need on LinkedIn. LinkedIn Home What is LinkedIn? Join Today Sign In Main content ...
... content stored documents ... for Rapid Knowledge Reuse-congility2011. ... Architect KAPS Group Knowledge Architecture Professional ...