Information
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

Content Migration XML Schema Reference

Windows SharePoint Services 3

This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Windows SharePoint Services 3.0 content migration is supported by APIs that are provided in the Microsoft.SharePoint.Deployment namespace. Additionally, migration implementations are supported by XML schemas provided with the Windows SharePoint Services 3.0 SDK.

The Windows SharePoint Services 3.0 content migration architecture provides a public schema to support the migration export package. You can create a package to import content into Windows SharePoint Services. In this way, you can move content from Microsoft Content Management Server (MCMS) 2002 into Microsoft Office SharePoint Server 2007 by creating a content migration package from the MCMS 2002 data to import into the Office SharePoint Server 2007.

The Windows SharePoint Services 3.0 provides eight schema (.xsd) files to support content migration, as described in the following table.

Schema File

Description

DeploymentManifest Schema

  • Provides validation for the Manifest.xml file that is exported into the content migration package.

  • Provides a comprehensive manifest containing listings of both the contents and the structure of the source site. The migration operation uses the manifest file to reconstitute the source site and its components when it is imported to the destination site.

DeploymentExportSettings Schema

Provides validation for the ExportSettings.xml file exported into the content migration package.

ExportSettings.xml does the following:

  • Contains the export settings specified by using the SPExportSettings class and other classes that are part of the content migration object model.

  • Ensures that the subsequent import process (at the migration target site) enforces the directives specified in the export settings.

  • Maintains a catalog of all objects exported to the migration package.

DeploymentLookupListMap Schema

Provides validation for the LookupListMap.xml file exported into the content migration package.

LookupListMap.xml maintains a simple lookup list that records SharePoint list item (list item to list item) references.

DeploymentRequirements Schema

Provides validation for the Requirements.xml file exported into the content migration package.

Requirements.xml maintains list of deployment requirements in the form of installation requirements on the migration target, such as feature definitions, template versions, Web Part assemblies, language packs, and so forth.

DeploymentRootObjectMap Schema

Provides validation for the RootObjectMap.xml file exported into the content migration package.

RootObjectMap.xml maintains a list of mappings of secondary (dependent) objects, which allows the import phase of the migration operation to correctly place the dependent objects relative to the locations of the root object mappings.

DeploymentSystemData Schema

Provides validation for the SystemData.xml file exported into the content migration package.

SystemData.xml does the following:

  • Collects a variety of low-level system data.

  • Records the number and names of Manifest.xml files (in cases where the migration uses multiple manifests).

DeploymentUserGroupMap Schema

Provides validation for the UserGroup.xml file exported into the content migration package.

UserGroup.xml maintains a list of users and user security groups with respect to access security and permissions.

DeploymentViewFormsList Schema

Provides validation for the ViewFormsList.xml file exported into the content migration package.

ViewFormsList.xml maintains a list of Web Parts and tracks whether each is a view or form.

Show: