Content Matrix 9.10 - SharePoint Edition

Enabling Link Correction

From the General Options tab, you can enable a variety of Link Correction options.

See also Link Correction

To configure Link Correction options:

1.Use the information in the following table to determine the appropriate option to select for Link Correction Scope.

2.If you want Content Matrix to parse through all the "text" type metadata columns (such as single line of text, multi-line, etc.) and run link correction on any absolute links (for example, "http://Quest/Production") that it finds, select Enable text field link correction.

NOTE:  When this option is selected:

§Content Matrix will skip over any relative links (for example, "./Main/Quest/Production") in the text.

§Link correction is run on text columns only; not text within documents.

If this option is selected, it can significantly increase the amount of time it takes to run the Link Correction.  Content Matrix must parse all the text values for the included "text" type field columns, and look for links within that content before it can check them. The amount of time taken will depend on the amount of data within the text columns.  

3.If you are renaming the object being migrated, and you want Content Matrix to pre-populate the link correction list using the renaming scheme, so it can correctly apply link correctio, nselect Comprehensive Link Correction.:

NOTE:  This link correction option is only required when you are renaming an object.  When content is renamed in a migration, the basic link correction cannot always properly map the new links on the target side, especially for cases with a large amount of sub-content.

4.If  you want Content Matrix to compare source and target objects:

§Check the Check Results box.

§Select a comparison Level from the drop-down:

§Moderate (the default value and recommended setting, especially if you are anticipating a number of differences)

OR

§Strict

NOTE:  These options will only be visible if they have been enabled.  See also Comparing SharePoint Objects.

Transformation Options

If both Advanced Mode and Custom Transformers are enabled, you can view, create, and edit Transformers.

Transformers are used primarily to “transform” fields and columns into Managed Metadata. There are also several built-in, non-editable transformers that Content Matrix uses to process data during the migration.  Advanced users can also create custom transformers using PowerShell.

The Transformations tab is divided into two sections:

·The Available Definitions section list all of the transformation definitions that are available for the current migration action, in alphabetical order.  Only definitions that are valid for the level at which the migration was initiated are listed.

·The Applied Transformers For <Object> dialog displays all of the transformations for the selected definition.

Grayed out items are mandatory transformations that are run during the course of a normal migration, and these actions cannot be edited or removed. However, they can be reordered by using the up and down arrows to the right-hand side of the window. This allows you to create and apply a transformation action before a mandatory action, if you want your action to run earlier in the process. You can even add a second instance of a mandatory transformer to run at a different stage of the migration process.

Transforming a Site or List Column into a Managed Metadata Columns

Content Matrix can transform SharePoint site or list columns (fields) into Managed Metadata columns, as a part of a migration. This allows users to transform columns on the source into SharePoint Managed Metadata columns on the target.

Column to Managed Metadata transformation settings are not preserved, so they will have to be configured for each migration that is run.

NOTE:  This option is only available when:

·The prerequisites for migrating Managed Metadata are met.

AND

·The Resolve managed metadata by name and hierarchy option is selected.

Additional Considerations for Site Column Transformations

A site column can be transformed into a Managed Metadata column even if the site column's root site is not being migrated. In this case, Content Matrix will add the Managed Metadata site column(s) to the top level site that is included in the migration, and all of the content in the scope of the migration will inherit these new site columns in place of the old ones. When applying a transformation of site columns in a migration, the site columns transformation will be applied to all of the content within the scope of the action that uses the specified site column. This includes any sites, lists, libraries and even content types that use the site column, and are within the scope of the migration.

For example, if a subsite is being migrated to the target, and this subsite contains lists and/or content types that use a site column which is inherited from the top level site, then when the sub site is migrated these inherited site columns will be replaced by new Managed Metadata site column. These new Managed Metadata site columns will use the subsite as their root site (since it was the top level site), and all of the content within the migration scope will inherit these new columns instead of using their original site columns. All the data for these columns will be converted to Managed Metadata values. Any site columns within content types (in the scope of the migration) will be converted the same way, and placed at the top level site in the migration.

NOTE:  Content Matrix can only apply this transformation to action to site columns of a certain type. The available column types include: Choice, MultiChoice, Text, Lookup, LookupMulti, Number, DateTime, Currency, Boolean, Note, and User.