Successfully reported this slideshow.

"The Mysterious Art of the Content Inventory" - Gilbane San Francisco 2010

1

Share

1 of 53
1 of 53

More Related Content

More from Blend Interactive

Related Books

Free with a 14 day trial from Scribd

See all

"The Mysterious Art of the Content Inventory" - Gilbane San Francisco 2010

  1. 1. The Mysterious Art of the Content Inventory<br />Deane Barker<br />Content Management Practice Director<br />Blend interactive<br />
  2. 2. @gadgetopia<br />
  3. 3. The reasons for a content inventory<br />The different types of inventory<br />Getting a list of all your content<br />The information to track<br />Challenges you’re going to encounter<br />The Rolling Inventory<br />
  4. 4. Why do a content inventory?<br />
  5. 5. Why do a content inventory?<br />To evaluate, implement, and execute a content strategy<br />
  6. 6. Why do a content inventory?<br />To guide or scope a re-development project<br />
  7. 7. Why do a content inventory?<br />To guide a content governance or operations management initiative<br />
  8. 8. What are the different flavors of inventory?<br />
  9. 9. What are the different flavors of inventory?<br />Editorial.<br />Review content for editorial value.<br />How valuable is our content to the consumer?<br />How well does the content serve our goals?<br />
  10. 10. What are the different flavors of inventory?<br />Census.<br />Identify content to better track or manage it, or to scope a migration effort.<br />How much content do we have?<br />
  11. 11. What are the different flavors of inventory?<br />Functional.<br />Review content to determine the level of functionality present.<br />How complicated is our content?<br />
  12. 12. What are the different flavors of inventory?<br />It’s very common for an inventory to mix the three goals.<br />
  13. 13. How do we identify all our content?<br />
  14. 14. How do we identify all our content?<br />Manual or automated, depending on the size of the site.<br />
  15. 15. How do we identify all our content?<br />Drawbacks<br />time-consuming<br />easy to miss hard-to-find content<br />Benefits<br />simplest<br />experience interacting with the content<br />Manual – start at the home page, and keeping surfing<br />
  16. 16. How do we identify all our content?<br />Benefits<br />Can be simple and fast.<br />Drawbacks<br />Requires a CMS<br />What about content not in the CMS?<br />Export– get a list from your CMS<br />
  17. 17. How do we identify all our content?<br />Benefits<br />Nicely comprehensive<br />Drawbacks<br />Won’t catch authenticated, non-linked, or non-addressable content<br />Crawl– get a list from a public or private spidering service or product<br />
  18. 18. How do we identify all our content?<br />The best solution will likely be a hybrid.<br />
  19. 19. What questions should we be asking about our content?<br />
  20. 20. What questions should be asking about every page?<br />Because, eventually, you get down to columns on a spreadsheet.<br />
  21. 21. What questions should be asking about every page?<br />Identifier<br />URL<br />Title<br />
  22. 22. What questions should be asking about every page?<br />Try to re-use the identifier out of your CMS, if feasible.<br />
  23. 23. What questions should be asking about every page?<br />What type of content is it? What “bucket” does it fit into?<br />
  24. 24. What questions should be asking about every page?<br />Who is the stakeholder behind this content? Who owns it?<br />
  25. 25. What questions should be asking about every page?<br />What format is the content in? HTML or PDF? Free-form or structured?<br />
  26. 26. What questions should be asking about every page?<br />Where does the source content live? In what repository?<br />
  27. 27. What questions should be asking about every page?<br />Who is the intended audience?<br />
  28. 28. What questions should be asking about every page?<br />What is the velocity of this content – how often does it change from both a creation and update standpoint?<br />
  29. 29. What questions should be asking about every page?<br />Why does it change? What is the trigger that caused an update of this specific content, or more content of this type?<br />
  30. 30. What questions should be asking about every page?<br />Why does it change? What is the trigger that caused an update of this specific content, or more content of this type?<br />
  31. 31. What questions should be asking about every page?<br />What are the security implications of this content? Is it public? If not, who can view it and why?<br />
  32. 32. What questions should be asking about every page?<br />Who can edit or delete this content, or add new content of this type?<br />Evaluate this both organizationally and technically!<br />
  33. 33. What questions should be asking about every page?<br />Who can edit or delete this content, or add new content of this type?<br />
  34. 34. What questions should be asking about every page?<br />How much traffic does this content receive?<br />
  35. 35. What questions should be asking about every page?<br />Does this content have any value? If it doesn’t have value, why is it here?<br />
  36. 36. ROT<br />Redundant<br />Obsolete<br />Trivial<br />
  37. 37. What questions should be asking about every page?<br />If this content went away tomorrow, would anyone care?<br />
  38. 38. What challenges will we face?<br />
  39. 39. What challenges are we going to face?<br />Getting a comprehensive inventory<br />
  40. 40. What challenges are we going to face?<br />Collaboration between multiple parties<br />
  41. 41. What challenges are we going to face?<br />Managing and documenting feedback and discussion<br />
  42. 42. What challenges are we going to face?<br />Keeping up with additions throughout the inventory process.<br />
  43. 43. What challenges are we going to face?<br />Getting information about content from the organization.<br />
  44. 44. What challenges are we going to face?<br />Making decisions about content at the individual or type level<br />
  45. 45. What challenges are we going to face?<br />Not all content has a URL<br />
  46. 46. The End Product<br />
  47. 47. The End Product<br />Invariably a matrix of some sort.<br />Often supplemented by some analysis document.<br />
  48. 48. The End Product<br />If multiple parties are involved, consider a single-source tool.<br />
  49. 49. The End Product<br />Can you use metadata in your CMS to store content inventory data?<br />
  50. 50. The Rolling Inventory<br />Or, how to keep it going…<br />
  51. 51. The Rolling Inventory<br />At least once per quarter, take some time to inventory new content.<br />
  52. 52. The Rolling Inventory<br />Set policy-based review dates on all new content.<br />
  53. 53. About Me<br />Deane Barker<br />Email: deane@blendinteractive.comBlog: gadgetopia.com<br />Twitter: @gadgetopia<br />

Editor's Notes

  • To answer questions about your content
  • HTML or PDF has a huge impact on migratbility
  • Helps with government and operations management.
  • Budget timeHave organizational authority to askHave authority to make a decision when there’s no compliance
  • 400 press releasesEditorial – yes, go through each oneCensus – no, just get the total numberFunctional – no, so long as I know what one looks like, it doesn’t matter how many there are
  • ×