Content is data: pushing re-use to the limit. Dr. Adrian R Warman
Agenda <ul><li>Introduction </li></ul><ul><li>Technical content and enterprise data </li></ul><ul><li>Real world examples ...
Introduction <ul><li>Who am I? </li></ul><ul><ul><li>Dr. Adrian R. Warman </li></ul></ul><ul><li>Where do I work? </li></u...
Terminology: Re-use   
Technical content and enterprise-level data <ul><li>Most organizations depend on 'scalable' repositories: </li></ul><ul><u...
Real world examples <ul><li>Many 'personalized' documents. </li></ul><ul><li>Pharmaceuticals. </li></ul><ul><li>GIS. </li>...
Re-use: panacea or problem? <ul><li>Does re-use scale? </li></ul><ul><ul><li>An example. </li></ul></ul><ul><li>Suggestion...
Controlling re-use <ul><li>Rockley [http://www.rockley.com/TheRockleyReport/V1I3/Information%20Architecture.htm] identifie...
Best practices 1 <ul><li>Identify re-purposing 'dimensions'. </li></ul><ul><li>Be cautious about adding dimensions. </li><...
Best practices 2 <ul><li>Identify / acquire / implement tooling to help manage re-purposing. </li></ul><ul><ul><li>For all...
Best practices 3
Conclusions <ul><li>Basically, re-use / re-purposing is an important technique. </li></ul><ul><li>In a short-term, small-s...
Upcoming SlideShare
Loading in …5
×

Content is data: pushing re-use to the limit

1,089 views
956 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,089
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Content is data: pushing re-use to the limit

  1. 1. Content is data: pushing re-use to the limit. Dr. Adrian R Warman
  2. 2. Agenda <ul><li>Introduction </li></ul><ul><li>Technical content and enterprise data </li></ul><ul><li>Real world examples </li></ul><ul><li>Re-use: panacea or problem? </li></ul><ul><li>Controlling re-use </li></ul><ul><li>Best practices </li></ul><ul><li>Conclusions </li></ul>
  3. 3. Introduction <ul><li>Who am I? </li></ul><ul><ul><li>Dr. Adrian R. Warman </li></ul></ul><ul><li>Where do I work? </li></ul><ul><ul><li>Hursley Park, Winchester IBM United Kingdom Limited </li></ul></ul><ul><li>How can you contact me? </li></ul><ul><ul><li>Tel: +44-1962-819176 </li></ul></ul><ul><ul><li>Email: [email_address] </li></ul></ul><ul><ul><li>Google+: Adrian Warman </li></ul></ul><ul><li>What do I do? </li></ul><ul><ul><li>Information Architect </li></ul></ul><ul><li>Disclaimer </li></ul><ul><ul><li>Any views or opinions expressed in this presentation are those of the author, and do not necessarily represent official positions, strategies or opinions of International Business Machines (IBM) Corporation. </li></ul></ul><ul><ul><li>No guarantees are offered as to the timeliness, accuracy or validity of information presented. </li></ul></ul><ul><li>Acknowledgement </li></ul><ul><ul><li>Clip art used in this presentation is from the Open Clip Art Library http://www.openclipart.org/ </li></ul></ul>
  4. 4. Terminology: Re-use   
  5. 5. Technical content and enterprise-level data <ul><li>Most organizations depend on 'scalable' repositories: </li></ul><ul><ul><li>Database content. </li></ul></ul><ul><ul><li>Development source code. </li></ul></ul><ul><ul><li>Standard tools / applications / spreadsheets. </li></ul></ul><ul><ul><li>Documentation. </li></ul></ul><ul><li>They provide a single 'go-to' location for organizational material. </li></ul><ul><ul><li>Reduces duplication. </li></ul></ul><ul><ul><li>Helps with version management. </li></ul></ul><ul><li>Provides an opportunity: </li></ul><ul><ul><li>Technical content created and stored for one purpose might be re-used for another purpose. </li></ul></ul><ul><ul><ul><li>Manuals / guides. </li></ul></ul></ul><ul><ul><ul><li>Training materials. </li></ul></ul></ul><ul><ul><ul><li>Product literature. </li></ul></ul></ul><ul><ul><li>Especially if it can be accessed through a 'portable' format: XML or SQL. </li></ul></ul>
  6. 6. Real world examples <ul><li>Many 'personalized' documents. </li></ul><ul><li>Pharmaceuticals. </li></ul><ul><li>GIS. </li></ul><ul><li>Product development </li></ul><ul><ul><li>Software, in particular </li></ul></ul><ul><li>But …. </li></ul>
  7. 7. Re-use: panacea or problem? <ul><li>Does re-use scale? </li></ul><ul><ul><li>An example. </li></ul></ul><ul><li>Suggestion: Recognize that solving one problem introduces another. </li></ul><ul><li>Suggestion: Distinguish between re-using and re-purposing. </li></ul>
  8. 8. Controlling re-use <ul><li>Rockley [http://www.rockley.com/TheRockleyReport/V1I3/Information%20Architecture.htm] identifies four ways of controlling re-use: </li></ul><ul><ul><li>Opportunistic reuse </li></ul></ul><ul><ul><li>Systematic reuse </li></ul></ul><ul><ul><li>Nested reuse </li></ul></ul><ul><ul><li>Workflow </li></ul></ul><ul><li>Suggestion: Think about the distinction between controlling re-use and managing re-purposing. </li></ul>
  9. 9. Best practices 1 <ul><li>Identify re-purposing 'dimensions'. </li></ul><ul><li>Be cautious about adding dimensions. </li></ul><ul><li>Think about whether you are really re-purposing, or simply sharing. </li></ul><ul><li>Is the content Factual? </li></ul><ul><ul><li>Static, resilient, rarely changes. </li></ul></ul><ul><ul><li>Good candidate for re-purposing [Green flag] . </li></ul></ul><ul><li>Is the content Editorial? </li></ul><ul><ul><li>Definitive, highly variable between re-purposing dimensions, but static within the dimension. </li></ul></ul><ul><ul><li>Possible candidate for re-purposing [Amber flag] . </li></ul></ul><ul><li>Is the content Opinion? </li></ul><ul><ul><li>Sales, marketing, highly variable. </li></ul></ul><ul><ul><li>Poor candidate for re-purposing [Red flag] . </li></ul></ul><ul><li>Can you isolate and so push content from Opinion -> Editorial -> Factual? </li></ul>
  10. 10. Best practices 2 <ul><li>Identify / acquire / implement tooling to help manage re-purposing. </li></ul><ul><ul><li>For all but the simplest scenarios, management is more important than enabling re-purposing. </li></ul></ul><ul><li>Identifying factors: </li></ul><ul><ul><li>Ability to 'collapse' instances of re-purposing. </li></ul></ul><ul><ul><li>Support for 'Test Driven Documentation'. </li></ul></ul><ul><ul><li>Support for metadata rationalization (managing the dimensions). </li></ul></ul><ul><ul><li>Links with software source code management </li></ul></ul><ul><ul><ul><li>In particular, for merging changes. </li></ul></ul></ul>
  11. 11. Best practices 3
  12. 12. Conclusions <ul><li>Basically, re-use / re-purposing is an important technique. </li></ul><ul><li>In a short-term, small-scale case, it can and does save time and effort. </li></ul><ul><ul><li>But don't equate small number of re-purposing dimensions with small number of content files. </li></ul></ul><ul><li>Increasing the number of re-purposing dimensions will, by definition, introduce complexities to be managed. </li></ul><ul><ul><li>They increase the time and effort required to perform all documentation tasks. </li></ul></ul><ul><ul><li>They enable errors. </li></ul></ul><ul><ul><li>They can be extremely difficult to remove. </li></ul></ul><ul><li>Be aware of the risks. </li></ul><ul><ul><li>Have processes / tools in place to help you detect scaling issues. </li></ul></ul><ul><ul><li>As you hit a pain point, think about the number of re-purposing dimensions. Use this as an early warning flag for 'next time'. </li></ul></ul><ul><li>A small change early can avoid a big change later. </li></ul>

×