« Spontaneous Thought Memorialized | Main | ECM delivered using SaaS »

04/20/2008

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Compliance - Never Talk When You Can Nod

SharePoint-ECM Reference Architecture 3: Use SharePoint as a Portal Container

Read more about the seven reference architectures.

Compliance - Never Talk When You Can Nod

SharePoint-ECM Reference Architecture 2: Loosely Coupled Solution.

In the second of the seven architectures I take the general premise from the previous example and extend it. The content still lives natively in SharePoint while you are collaborating on it and is then "migrated" in to the traditional ECM system at a predetermined point in time...

Virginia Backaitis

Andrew, For Documentum users who are thinking about how they will integrate SharePoint into their existing environments, the “Seven Reference Architecture Organizer”, once it’s done, should be required reading. The first three choices, as far as I can see, wouldn’t be attractive to existing Documentum users in environments where minimizing risk is more important than cost and ease-of-use. Case and point? eCTD creation. The vendors in this space for whom I’ve recently completed searches, and who have close relationships with the FDA, have said things like, “SharePoint has a long way to go when in comes to getting through review and validation.” Will the Documentum/SharePoint integrations described in Reference Architectures 4-7 make these vulnerabilities go away? If so, does this mean that Documentum will have more users/client and sell more user licenses? Another question that I think needs to be addressed is whether a product like FCG’s FirstPoint can achieve the same time-to-market and compliance wins for a SharePoint customer as a SharePoint/Documentum integration can? In any case, I’m looking forward to learning more. EMC certainly gets their worth when they pay you. Virginia http://www.brilliantleap.com/blog/

Compliance - Never Talk When You Can Nod

SharePoint-ECM Reference Architecture 1: Keep Systems Separate, Restrict Usage.

aka Hobson's choice. In this architecture, an end user moves a piece content from SharePoint into the traditional ECM system by manually exporting the object from SharePoint on to their desktop and then importing that object back in to the Enterprise Content Management system as a net new object. Equally, if a user needs to get content between two SharePoint sites they will follow the same procedure, i.e. they will export the content from one SharePoint site out onto the desktop and then import it into a new SharePoint site....

Compliance - Never Talk When You Can Nod

SharePoint-ECM Reference Architecture 2: Loosely Coupled Solution.

In the second of the seven architectures I take the general premise from the previous example and extend it. The content still lives natively in SharePoint while you are collaborating on it and is then "migrated" in to the traditional ECM system at a predetermined point in time...

Compliance - Never Talk When You Can Nod

SharePoint-ECM Reference Architecture 3: Use SharePoint as a Portal Container

In the previous two examples we focused on moving content from the SharePoint document library in to the traditional ECM’s repository behind the scenes. That “publish to ECM” paradigm may work for you but you must consider that once the content has moved in to your traditional ECM system’s repository you will lose sight of it from within SharePoint...

Compliance - Never Talk When You Can Nod

SharePoint-ECM Reference Architecture 4: Passive Unification in Web Part

The objective of this fourth architecture is to create an environment where the end user is not aware of where an object actually resides. If the end user needs to see three documents in order for her to do her job then she should see all three documents in a single Web Part...

Compliance - Never Talk When You Can Nod

SharePoint-ECM Reference Architecture 4: Passive Unification in Web Part

Read more about the eight reference architectures. I represent the previous three architectures as being

Compliance - Never Talk When You Can Nod

SharePoint-ECM Reference Architecture 4: Passive Unification in Web Part

The objective of this fourth architecture is to create an environment where the end user is not aware of where an object actually resides. If the end user needs to see three documents in order for her to do her job then she should see all three documents in a single Web Part...

Compliance - Never Talk When You Can Nod

SharePoint-ECM Reference Architecture 5: Active Unification

Read more about the eight reference architectures. In the previous reference architecture we unified SharePoint and the ECM system at the Web Part layer and provided a limited subset of functionality, specifically passive operations. There's no doubt that this

Compliance - Never Talk When You Can Nod

SharePoint-ECM Reference Architecture 5: Active Unification

In the previous reference architecture we unified SharePoint and the ECM system at the Web Part layer and provided a limited subset of functionality, specifically passive operations. There's no doubt that this "passive connectivity" provides a huge amount of value, uses a nice, familiar paradigm and can constitute a complete solution in some cases. However, there are many times when you need to be able to act more fully upon the content in the disparate systems rather than just browsing and viewing the documents...

Compliance - Never Talk When You Can Nod

Reference Architecture 6: Passive Back-end Aggregation

Read more about the eight reference architectures. Let me preface this entry by saying that this reference architecture is similar to reference architecture #1 insomuch as it is not something that I recommend or endorse but it is something that I see in use fairly frequently today; in fact many of the solutions recommended by Microsoft fall in to this category. Best case, feel free to use this approach while you wait for more appropriate solutions to come along. In the previous architectures we were trying to create a unified model so that an end user ...

Compliance - Never Talk When You Can Nod

Reference Architecture 7: Active Back-end Aggregation

Read more about the eight reference architectures. So unlike little old RefArch 6, this guy is the real deal. In this architecture we aggregate the actual content from a multitude of SharePoint sites. The content is transparently taken from SharePoint's control then stored and managed in a truly aggregated single location. In theory, there are a number of different ways of doing this: You can replace the entire SQL Server layer with an ECM solution that emulates the entire SQL stack. This gives you control over the content, metadata, lists, calendar items, Blogs, etc... in ...

Brad Stuart

A client of mine is an active reader of your blog and would like to speak to you. I wanted to discuss a consulting project with you directly. Please email me so we can connect. I look forward to chatting with you.Regards,Brad

Compliance - Never Talk When You Can Nod

SharePoint Archiving - RBS vs. EBS vs. Content Transfer vs. Shortcuts

If you only read one of my series of posts this lifetime you might want to make it this one. It is certainly not my most coherent or interesting series but it is the one that is likely to save you the most grief over the next few years, (assuming you have something to do with SharePoint deployments). This was going to be a single post but I got a bit carried away so I've split it up in to the following posts: This one - An Overview of the Issues ...

Compliance - Never Talk When You Can Nod

SharePoint Archiving - RBS vs. EBS vs. Content Transfer vs. Shortcuts

Imagine a world where content created in SharePoint was automatically routed to the most appropriate location depending on factors such as values in the object's attributes, where the object is in its lifecycle and/or who created it. Imagine that this was done without in any way affecting the SharePoint end user experience or any applications built on top of SharePoint. Imagine if doing this didn't just reduce risk and costs but it also made your SharePoint deployments more scalable and robust...

Compliance - Never Talk When You Can Nod

SharePoint Archiving - RBS vs. EBS vs. Content Transfer vs. Shortcuts

Imagine a world where content created in SharePoint was automatically routed to the most appropriate location depending on factors such as values in the object's attributes, where the object is in its lifecycle and/or who created it. Imagine that this was done without in any way affecting the SharePoint end user experience or any applications built on top of SharePoint. Imagine if doing this didn't just reduce risk and costs but it also made your SharePoint deployments more scalable and robust...

The comments to this entry are closed.


Cloud Computing Journal
Top 100 Cloud Computing Bloggers