« Document Collaboration - A New Approach? | Main | SharePoint-ECM Reference Architecture 2: Loosely Coupled Solution. »



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

douq millar

A challenge with the continuously changing types of collaboration information such as discussion threads or wikis is determining the event to trigger the migration (or replication) into an ECM store. Wiki pages can undergo very tiny changes creating a vast array of versions in the repository. Threaded discussion may be separate "records" or just a single record that is updated by appending more comments at the end. All these mechanisms proliferate a lot of similar data to clog up the store, not to mention generate a lot of bandwidth feeding it. The typical wiki mechanism (presumably used in SP) of just saving diffs may have to be added when migrating this kind of date, ideally at the source (to reduce incoming bandwidth) but at the backend if that is the only convenient place for this function.

The comments to this entry are closed.

Cloud Computing Journal
Top 100 Cloud Computing Bloggers