[Sigia-l] DMS vs CMS

[Ruth Kaufman]

Tanya:
> Thanks for the helpful comments so far. I think one thing
> that has added to my confusion is that the strategy has been
> to solve the "web content" problem and the "document"
> problem as two separate unrelated things.

It may help your team to approach this as an end-to-end publishing process that involves BOTH managing documents (fully formed works that represent intellectual objects) and managing web content including (in no particular order): workflow; validations; transformations (e.g., XSLs, JSPs); expiration management; content delivery dynamics in a portal environment; syndication/content sharing; CMS interfaces (Interwoven calls them "data capture templates") for content authors; etc.

I recently heard someone refer to web content as "everything that's not code". You can also think about the content of the content (i.e., the message) and how you manage that -- editorial guidelines, campaigns, etc. But that's another can of worms.

HTH,
Ruth