Creating a SharePoint Taxonomy Value column is very similar to creating any other column in the Metabase project.
To create a Taxonomy Value column:
1.Make sure you are connected to the target SharePoint server (currently only Local Object Model and Metalogix Extensions Web Service connections are supported).
2.In Explorer View, select any directory under the source connection containing documents for which you want to create a taxonomy column.
3.Switch to Items View.
·Select the drop down arrow next to the [Manage Column] button, and choose New Column to display the Add Column dialog
·Click [Manage Columns] to display the Manage Columns dialog then click the Add icon.
5.In the Property Name field, enter a name for the new taxonomy column.
6.In the Type drop down list, select the SharePoint Taxonomy option to display the Configure SharePoint Taxonomy Column dialog.
7.Specify the details of the term set to associated with this column. The details must be specified in the following order.
a)SharePoint Connection - The active SharePoint connection from which to load term stores. as each drop-down list populated based on the selection that precedes it.
Term Store - The parent Managed Metadata term store.
NOTE: You must already have Term Store Administrator permissions in order to successfully select a term store. This permission must be added in the SharePoint Central Administration, and is separate from Site Collection Administrator and Farm Administrator permissions. Term Store Administrator permissions can be set under Application Management > Manage Service Applications > Managed Metadata Service > [Managed Metadata Service Application]. If the user account that is adding a column does not have these permissions a message will be thrown indicating the lack of permissions.
b)Group - The parent Managed Metadata group.
c)Term Set - The term store to associate with this column.
NOTE: Each of these fields will automatically populate existing values base on the selection in the previous field, for whatever SharePoint connection is selected.
There is also an Allow multiple values check-box option that you can select to allow the new column to contain more than a single value. This option will be used if the new column is mapped to a new Managed Metadata columns during migration.
8.Click [OK] to accept the selected term set.
9.Specify the Description, Category, and Display Name for this new SharePoint Taxonomy data column.
NOTE: Only the Category option is required and will be set to Misc by default.
10.Click [OK] to close the dialog.
The new column has now been added to the Metabase project.
You can run a check between the source data and the target SharePoint taxonomy values to ensure that any taxonomy columns that have been created with the source data have values that are existing terms in SharePoint. The general use case for this option is to generate a report to determine if any of the SharePoint taxonomy columns that have been added to the source data still exist in the target taxonomy term stores.
For example, if a new column was added to the source as a SharePoint taxonomy column and values were assigned that correspond to existing SharePoint taxonomy terms. you can generate a report to check if these values still on the SharePoint target.
To validate Taxonomy values:
1.In Explorer View, select the source blog or Wiki site containing items with for which you want to validate SharePoint Taxonomy values.
2.Right-click and choose Managed Metadata > Validate Taxonomy Values to display the Validate Taxonomy Values dialog.
3.If you want to Remove missing terms from the source connection taxonomy column if no equivalent match can be found in the target SharePoint taxonomy term stores, check this box.
If you leave this box unchecked, the report will be run on the terms from the source, but if any terms are missing from the target the values will be left in the source column.
4.Once all the desired options are set, you can either Run the job immediately or Save the job to be run at a later time from the Jobs List.
When the action starts, a Job log will be created. The logs can be viewed (in progress or after the action is finished) by clicking [Details>>]. After the action has completed a note will be displayed in the bottom left corner of the dialog stating the number of completions, as well as any warnings or errors that may have been encountered (if there were any).
The taxonomy validation process itself looks at any SharePoint taxonomy columns that have been added to the source data, and logs all of the values that have been entered. Each taxonomy column that has been added to the source is compared to the connection in the SharePoint target. Any source values that are missing a SharePoint equivalent will be logged in the report that is generated.
You can use Content - Blogs and Wikis Edition to apply transformations to source content, to clean the HTML source at migration time and strip away malformed HTML or to fix invalid page code tags. Transformations must be applied to the source content before migration, and they can only be applied to Pages, Posts and Comments (any HTML content). Transformations are global settings, and are applied to all actions. This means that if any content will be migrated, and transformations are not needed for that content, any transformation actions that are configured would need to be cleared before migration; otherwise the content will be migrated with the set transformations. Transformations will not alter any actual source data. Metalogix Content Matrix will only apply the transformations to a copy of the data as it is migrated.
Content transformation is important for many reasons. The most common use case for content transformation is to clean up the source page HTML to better fit the SharePoint migration target. This allows the source content to meet any SharePoint restrictions without having to manually edit each page or comment. Other less common use cases include styling the HTML content with additional Content Style Sheet (CSS) properties. All of these can be achieved through the use of two supported search and replace algorithms: plain text and Regex search.
It is recommended that any Regex users should test their Regex before migration, to ensure that the Regex does not corrupt the HTML. If bad Regex is used it is highly possible that the migrated content will be corrupted. The source data itself will not be corrupted, as the transformations are applied to a copy of the content as part of the migration process. This allows you to experiment with your Regex (and plain text) to find your desired transformation configuration.
To transform page and comment content before migration:
NOTE: Once transformations are configured, they will be applied to all items in a migration until the transformations are removed.
1.In Explorer View, select the source blog or Wiki site to which you want to apply transformations.
2.Right-click and choose Edit Transformations to display the Transformations Settings dialog.
3.In the Match field, enter either:
§the value or pattern in the source data to match (for Text matches)
§a Regex equation (for Regex matches)
4.From the Match Type drop-down, select the search algorithm you want Metalogix Content Matrix to use to search for, and transform values; either
5.In the Value field, enter the value that should be used to replace the Match value on the source.
6.To add additional transformation settings:
a)Press [Tab] to create a new row.
b)Repeat Steps 3-5
7.After all of the desired transformations are set, click [OK].
All of the Transformations will be applied to any applicable content within a migration.
If transformations have already been set, and you want to migrate Pages, Posts, or Comments without using the configured transformations, you will need to open the Transformation Settings dialog, and delete all the set transformations listed.
You can create new SharePoint site collections, sites, folders, and lists via the Metalogix Content Matrix Console.