Toluu

Microsoft Enterprise Content Management (ECM) Team Blog

A blog about the ECM features in the 2007 Office system, with a focus on Microsoft Office SharePoint Server 2007, which includes document management, records management, and web content management capabilities. Enabling technologies such as workflow and information rights management, which are essential to ECM solutions, will also be covered.

Publishing Sites: Field Controls or Web Parts... That is the Question!October 9 2008

There isn't a week that goes by where I don't get an email asking me this very question.  More often than not, its because someone has been using the Content Editor Web Part (CEWP) when they should have been using the Publishing HTML field type.  This mistake typically goes unnoticed until a customer needs to roll back to a previous version of a page or when they run a content deployment job.  So what goes wrong?  Well, the CEWP doesn't store version history, it doesn't participate in any publishing approval workflow and it does store absolute URLs rather than relative URLs.  The first problem means you'll have to go to site backups to get access to previous versions of content, the second problem means that users will see updates to the content in the CEWP even if an editor hasn't approved the page for publishing and the third problem means that all your hyperlinks will resolve to the wrong address (e.g. http://staging.adventure-works.com/ vs http://www.adventure-works.com/).

Thankfully, all of these problems can be avoided by using the Publishing HTML field type.  I've talked at length with Andrew Connell (MVP) about this and I know it's something he is passionate about so I asked him to write up a guest post to explore the topic.

Ryan Duguid
Technical Product Manager
Microsoft Corp

Andrew Connell on Field Controls and Web Parts

One of the most common problems I see with people developing P

Announcing the Content Management Interoperability Services (CMIS) specificationSeptember 9 2008

Today, we're excited to announce the launch of a standards effort for Enterprise Content Management systems that Microsoft has been driving with several other major vendors (IBM, EMC, Alfresco, OpenText, SAP, Oracle) called "Content Management Interoperability Services" (or CMIS, for short).

The goal of CMIS is to define a web services standard for interacting with Enterprise Content Management systems like Microsoft Office SharePoint Server, EMC Documentum, IBM FileNet P8, etc.

Why: Integrating multiple ECM systems is hard

We've heard from many organizations that want to use SharePoint, but have other ECM systems or applications in place that they need SharePoint to work with. Often these deployments are the result of different business units that deployed different ECM systems or that were "inherited" from mergers or acquisitions, or the organization may be transitioning from one ECM system to another over time.

Having multiple ECM systems introduces integration challenges: Enterprises (rightly) want their users to be able to access and manage all content in the way that best meets their needs, regardless of which system it actually live in. For example, users want unified access to all the content they need to work with on their team site, organizations want their electronic discovery applications be able to find content and suspend its

New blog: To The SharePointJuly 29 2008

The SharePoint IT Pro Documentation team has launched a new blog. This is a great place to find out about new and upcoming SharePoint documentation and provide your feedback.  Check it out here:  To the SharePoint.

Content Deployment and the Infrastructure UpdateJuly 15 2008

On the 20th May, we released two hotfix packages focused on Content Deployment.  These packages delivered performance improvements and addressed a number of known customer pain points.  The hotfixes have been rolled in to the Infrastructure Update for Office Servers that was released today so if you've been experiencing issues with Content Deployment, download the pack, install it and you'll get federated search thrown in with the deal.

The updates can be downloaded from the links below:

Infrastructure Update for Microsoft Office Servers (KB951297) - x86
Infrastructure Update for Microsoft Office Servers (KB951297) - x64
Infrastructure Update for Windows SharePoint Services 3.0 (KB951695) - x86
Infrastructure Update for Windows SharePoint Services 3.0 (KB951695) - x64

Announcing: End-to-End Content Deployment WalkthroughJune 11 2008

Hi, I'm Cern McAtee, a technical writer for Office SharePoint Server 2007. I'm pleased to announce that the Office SharePoint Server 2007 content team and the Global Readiness team have combined efforts to write and publish a new walkthrough guide for content deployment: End-to-End Content Deployment Walkthrough.

What's covered

This downloadable guide is aimed at IT pros planning to use content deployment with their enterprise sites using Microsoft Office SharePoint Server 2007. The guide takes you through the steps for setting up source and destination site collections, creating a deployment path and job, and then running the job to see how it populates the destination site collection with the content from the source site collection. One important thing to note when it comes to doing content deployment is that when you first set it up, the destination site collection must be empty. You can create the destination site collection using either the Blank site template, or by using the Stsadm createsite operation to create an empty site.

In addition to the walkthrough, we have also published a set of topics about Administering Web content management that cover publishing and content deployment operations. These topics are intended for IT pros who manage publishing and content deploymen