[Sigia-l] DMS vs CMS

[Hilary Marsh]

The other piece of this, of course, is that no matter what 
technology/ies are in place, people need to change their behavior, 
and the change management component will make or break the project's 
success.

The fact that the Web content and document efforts are separate 
indicates that there's work to be done in building bridges between 
these. However, it's complicated. I'm in the middle of a project now 
where all we can do at the outset is build a new interface over an 
existing mess and plan for future phases.

As the discussion so far has pointed out, there are many products out 
there that have similar hype, very different costs and varying 
capabilities/features. I would recommend that rather than parallel 
tracks for two things, you might consider starting with one system 
for either the Web content or the document problem and see if/where 
there are opportunities to extend the product.

Best,

Hilary


>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.
>
>DAM makes me think of being able to track the rights
>management info of a document/image/etc. that we didn't
>create but host and reuse. But perhaps that's something that
>can be handled in certain DMS's/CMS's as well? Perhaps the
>space is further blurred among all three?
>
>-Tanya


-- 
Hilary Marsh
president, content company inc
plan  *  create  *  manage
http://www.contentcompany.biz
708.217.3922


Cosponsor, Ragan's 2004 Web Content Roundtable for Higher-Ed 
Professionals, June 15, Chicago: 
http://www.ragan.com/html/main.isx?sub=2394. Save $75 if you register 
using my special code: 405CC!