Comments on: Documentum and SharePoint – Key differences for document control applications http://blog.tsgrp.com/2010/03/03/documentum-and-sharepoint-%e2%80%93-key-differences-for-document-control-applications/ Mon, 20 May 2013 01:54:51 +0000 hourly 1 http://wordpress.com/ By: Documentum, SharePoint, Alfresco – Document Control for Life Sciences | TSG Blog http://blog.tsgrp.com/2010/03/03/documentum-and-sharepoint-%e2%80%93-key-differences-for-document-control-applications/#comment-4861 Mon, 22 Apr 2013 14:54:22 +0000 http://blog.tsgrp.com/?p=865#comment-4861 [...] – SharePoint 2010 got a ton of attention from customers in 2010 (related post – Documentum and SharePoint – Key differences for document control applications) but many are viewing SharePoint as less of an ECM play and more of a collaboration [...]

]]> By: Documentum and SharePoint – Key differences for document control applications Part II « TSG Blog http://blog.tsgrp.com/2010/03/03/documentum-and-sharepoint-%e2%80%93-key-differences-for-document-control-applications/#comment-741 Tue, 07 Dec 2010 18:55:33 +0000 http://blog.tsgrp.com/?p=865#comment-741 [...] initial post back in March comparing Documentum and SharePoint for document control continues to be one of our [...]

]]> By: TSG Blog – 18 months and counting « TSG Blog http://blog.tsgrp.com/2010/03/03/documentum-and-sharepoint-%e2%80%93-key-differences-for-document-control-applications/#comment-616 Mon, 13 Sep 2010 12:16:53 +0000 http://blog.tsgrp.com/?p=865#comment-616 [...] – Multiple Documentum related posts including Understanding differences for Document Control , Documentum OR SharePoint for Compliance, SharePoint – Adding ECM Structure and [...]

]]> By: Mike Sharp http://blog.tsgrp.com/2010/03/03/documentum-and-sharepoint-%e2%80%93-key-differences-for-document-control-applications/#comment-600 Thu, 09 Sep 2010 23:44:42 +0000 http://blog.tsgrp.com/?p=865#comment-600 This statement isn’t quite correct, or is at least misleading:

“The difficult part of SharePoint is that within a library, the applications forces “common” property views.”

The relationship between a document and it’s properties is related to the content type, not the library. A single library can have any number of content types, each with it’s own set of properties. The properties are not necessarily related to the document type either; For example, you can have three PDFs, each belonging to a different content type and therefore having different properties. All can peacefully exist in the same library.

Also, search scopes are a separately managed thing in SharePoint. You can create search scopes that cover a variety of sites. And you’re in no way restricted to a single library per site. Even if you set it up that way, this statement is not correct:

“or a site per plant with libraries that contain more than just SOPs. (would force separate searches on each site).”

If you want a global search, you configure a global scope.

But, as you mention, one significant difference is the lack of native renditions in SharePoint.

Regards,
Mike Sharp

]]> By: Documentum, Document Control and Alfresco « TSG Blog http://blog.tsgrp.com/2010/03/03/documentum-and-sharepoint-%e2%80%93-key-differences-for-document-control-applications/#comment-538 Fri, 13 Aug 2010 15:50:26 +0000 http://blog.tsgrp.com/?p=865#comment-538 [...] differences in regards to renditions and other common Document Control functions.  See previous post on SharePoint for Document [...]

]]> By: Documentum OR SharePoint for Complaince? Thoughts on a mixed approach. « TSG Blog http://blog.tsgrp.com/2010/03/03/documentum-and-sharepoint-%e2%80%93-key-differences-for-document-control-applications/#comment-488 Fri, 23 Jul 2010 13:33:19 +0000 http://blog.tsgrp.com/?p=865#comment-488 [...] be as easy as email” – another unstructured collaboration tool.  As discussed in a previous post, using SharePoint for compliance involves moving away from a user driven collaboration application [...]

]]> By: Documentum Migration to Alfresco – Part 1 « TSG Blog http://blog.tsgrp.com/2010/03/03/documentum-and-sharepoint-%e2%80%93-key-differences-for-document-control-applications/#comment-471 Mon, 19 Jul 2010 13:03:00 +0000 http://blog.tsgrp.com/?p=865#comment-471 [...] clients are pursuing a SharePoint direction.  We have addressed some of the SharePoint thoughts in previous posts .  For Documentum users, some of the advantages of Alfresco [...]

]]> By: Documentum – Top 12 Tips « TSG Blog http://blog.tsgrp.com/2010/03/03/documentum-and-sharepoint-%e2%80%93-key-differences-for-document-control-applications/#comment-434 Mon, 28 Jun 2010 10:04:23 +0000 http://blog.tsgrp.com/?p=865#comment-434 [...] are your customers are already looking at it.  Proactive Documentum clients have considered SharePoint and understand how to leverage connectivity rather than replacement.  TSG connectivity items are [...]

]]> By: Documentum Implementations – “Over Customized” or “Over Sold” « TSG Blog http://blog.tsgrp.com/2010/03/03/documentum-and-sharepoint-%e2%80%93-key-differences-for-document-control-applications/#comment-359 Thu, 20 May 2010 11:01:09 +0000 http://blog.tsgrp.com/?p=865#comment-359 [...] types of structured things Documentum typically does is not easy and often not possible.  See our previous post for configuring SharePoint for controlled [...]

]]> By: bethtee http://blog.tsgrp.com/2010/03/03/documentum-and-sharepoint-%e2%80%93-key-differences-for-document-control-applications/#comment-248 Thu, 25 Mar 2010 19:21:31 +0000 http://blog.tsgrp.com/?p=865#comment-248 Yes, you are able to major and minor version in MOSS and it is facilitated through the checkin/checkout process. Within a document library you can even configure rules around how you want versioning to behave (similar to what you can do with Documentum Compliance Manager) – these include options such as “always major version” or “major or minor version”. In addition to configuring versioning rules, you have the ability to configure retention rules around versions (e.g., delete all minor versions after document is published). Out of the box, MOSS delivers quite a bit of flexibility with how documents are versioned.

]]>