<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thanks for the reply! Sorry it's taken so long for me to reply. I'm
going out of town for 2 weeks, and this is crunch time. :) We're still
in the research stage at this point. We won't make a purchase until
2009 at the earliest. There's still no guarantee that the budget will
even be approved. Thanks for the heads up on Exponent. I'll keep you
posted.<br>
<br>
Bobby Metz wrote:
<blockquote cite="mid:030e01c8d1bd$4ec051f0$3c00a8c0@mulder" type="cite">
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<meta content="MSHTML 6.00.6000.16640" name="GENERATOR">
<style></style>
<div><font face="Arial" size="2">Doug,</font></div>
<div><font face="Arial" size="2"> Been away from the list for
quite awhile. Curious as to what your company went with. Also, if
they haven't decided, I would suggest you avoid Exponent. That's the
only CMS I have any experience with and I found it terrible. It's
based on MySQL and Perl/PHP but I found the documentation so lacking
that it was just too difficult to learn how to customize IMO.</font></div>
<div> </div>
<div><font face="Arial" size="2">Bobby</font></div>
<div> </div>
<div>----- Original Message ----- </div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div
style="background: rgb(228, 228, 228) none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>From:</b>
<a moz-do-not-send="true" title="perlguy@earthlink.net"
href="mailto:perlguy@earthlink.net">Douglas E. Miles</a> </div>
<div
style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>To:</b>
<a moz-do-not-send="true" title="friedman@highwire.stanford.edu"
href="mailto:friedman@highwire.stanford.edu">Michael Friedman</a> </div>
<div
style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>Cc:</b>
<a moz-do-not-send="true" title="phoenix-pm@pm.org"
href="mailto:phoenix-pm@pm.org">phoenix-pm@pm.org</a> </div>
<div
style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>Sent:</b>
Thursday, January 31, 2008 5:21 PM</div>
<div
style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>Subject:</b>
Re: [Phoenix-pm] OT - "Enterprise" content management systems</div>
<div><br>
</div>
I left out a "to". Place wherever is most entertaining. :) I need to
quit returning email when I'm in a hurry.<br>
<br>
Douglas E. Miles wrote:
<blockquote cite="mid:47A25EA3.60100@earthlink.net" type="cite">
<pre wrap="">Hey Michael! How's it going? This will be used support and serve up
our corporate website, so static content definitely won't cut it. I'm
still in the requirements/early evaluation stage here, but I thought I'd
see if I can learn from the collective wisdom of the list. :)
Michael Friedman wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Back when I used to work with FileNet we competed against Documentum.
Now I think they bought them, but that was many years ago.
Anyway, at that point, Documentum specialized in read-only documents.
You'd put things into the system and then could easily change metadata
about them, but not the documents themselves. Changing the documents
themselves was a pain. I would hope they've moved on from there, but I
admit I haven't looked recently.
However, building on Scott's point, you should do a serious
requirements analysis before picking even the category of "large
content management systems". It could be you only need something for
web-based content or could use a wiki with a proper set of
roles/authorization groups or something like Subversion. (Or, my
favorite, Trac, which combines a wiki, web access to a SVN repository,
and a request tracking system. It's written in Python, but for
development groups it's way cool.)
If what you really need instead is workflow management, there are also
other products out there for that market. Reviews and approvals, that
sort of thing. Heck, PDF has those capabilities built-in these days.
Anyway, good luck! I'd like to know what you end up with, because I'm
probably going to try again to get my company to get a better
documentation repository within the next few months. (It's an annual
thing. I keep losing, but I am persistent.)
-- Mike
On Thu, 31 Jan 2008, Scott Walters wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hey Doug,
I didn't have to work with any of these directly, but I worked
with people who did, at Mot*rola. My take on it is they're
all like aspirin... by the time you really need them to the
point where you'll go get one and use it, it's past the
point where it's strong enough to do any good.
If you need a content management system, you have a lot of data,
a lot of people accessing it, a lot of revisions, interdependencies,
etc. And then you need more than what a CMS has to offer.
If you start on it before you need it, you might have a chance.
A lot of people (and myself only second hand) are of the opinion
that they basically aren't worth the bother.
I wonder if you could do something completely custom and minimal
and wind up with more flexibility and utility... work operations
tend to be strongly tied to the org chat. If the org chat,
including work flow (who reports to who on what, including
ad hoc but long running relationships), and each person had
documents just throw out there (essentially ugo+r documents
in their file share), if a browser for those relationships wouldn't
would better. If it's a call center, something else. Or
manufacturing, something else again.
Oh well. Just a thought.
Good luck.
-scott
On 0, "Douglas E. Miles" <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E" href="mailto:perlguy@earthlink.net"><perlguy@earthlink.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">All,
This is somewhat off topic. Does anybody out there have any experience
with so-called Enterprise content management systems? I'm talking
about
systems from Interwoven, Vignette, Documentum, etc. I'd like to hear
about any recommendations or good/bad experiences. To make this
more on
topic: I'm especially interested to hear if Interwoven's TeamSite
still
uses Perl. The only information I can find is from 5-6 years ago. If
it does, and it meets our other criteria, I'd certainly love to make a
case for it. :) Thanks!
_______________________________________________
Phoenix-pm mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:Phoenix-pm@pm.org">Phoenix-pm@pm.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://mail.pm.org/mailman/listinfo/phoenix-pm">http://mail.pm.org/mailman/listinfo/phoenix-pm</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
Phoenix-pm mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:Phoenix-pm@pm.org">Phoenix-pm@pm.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://mail.pm.org/mailman/listinfo/phoenix-pm">http://mail.pm.org/mailman/listinfo/phoenix-pm</a>
</pre>
</blockquote>
<pre wrap="">---------------------------------------------------------------------
Michael Friedman HighWire Press
Phone: 650-725-1974 Stanford University
FAX: 270-721-8034 <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:friedman@highwire.stanford.edu"><friedman@highwire.stanford.edu></a>
---------------------------------------------------------------------
</pre>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
Phoenix-pm mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:Phoenix-pm@pm.org">Phoenix-pm@pm.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://mail.pm.org/mailman/listinfo/phoenix-pm">http://mail.pm.org/mailman/listinfo/phoenix-pm</a>
</pre>
</blockquote>
<br>
<p> </p>
<hr> _______________________________________________<br>
Phoenix-pm mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Phoenix-pm@pm.org">Phoenix-pm@pm.org</a><br>
<a class="moz-txt-link-freetext" href="http://mail.pm.org/mailman/listinfo/phoenix-pm">http://mail.pm.org/mailman/listinfo/phoenix-pm</a></blockquote>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Phoenix-pm mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Phoenix-pm@pm.org">Phoenix-pm@pm.org</a>
<a class="moz-txt-link-freetext" href="http://mail.pm.org/mailman/listinfo/phoenix-pm">http://mail.pm.org/mailman/listinfo/phoenix-pm</a></pre>
</blockquote>
<br>
</body>
</html>