The Mysterious Art of the Content Inventory - Gilbane San Francisco 2010
Upcoming SlideShare
Loading in...5
×
 

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

on

  • 1,573 views

Presented by Deane at Gilbane San Francisco 2010.

Presented by Deane at Gilbane San Francisco 2010.

Statistics

Views

Total Views
1,573
Views on SlideShare
1,573
Embed Views
0

Actions

Likes
4
Downloads
15
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 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

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

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