Merge SharePoint 2010 Term Sets using MetaVis Migrator

Sometimes it becomes important to copy SharePoint term sets between different SharePoint server farms. The first idea is to delete the term set or part of its hierarchy from the target location and then re-import it from the source. It does not seem like a right approach though if there are some data (items or documents) in the target environment that already use the existing terms. With MetaVis Migrator it is possible to copy term hierarchies between SharePoint servers preserving terms that already exist in the target environment and adding the new terms from the source to the right branches of the taxonomy tree.

The feature to merge terms opens an interesting opportunity to author and manage term sets in a development or QA environment and then, when time comes, bring updates to the production environment. In some other cases, this copy process should go in the other direction when developers or vendors periodically want to get the actual copy or the production taxonomies into their systems without destroying their current content metadata.

Let’s take a look at the details of how this feature works. Like some other readers of this BLOG at some point we faced the problem of moving from beta version of SharePoint 2010 to the production one so we needed to copy term sets too. This is how our Cameras term set looks in our destination SharePoint 2010 RTM (it has port 8091 in its URL).

This is the same Cameras term set in the source SharePoint 2010 beta server farm (it has port 8090 in its URL). Someone added models for Canon cameras there while both environments were active.

The copy process is simple: first, right click on the Cameras term set in the source environment and select Copy. Ctrl-C (or Command-C on Mac) also works.

Then, navigate to the destination term store, right click on the term group with the Cameras term set and select Paste. Key combinations Ctrl-V for Windows and Command-V on Mac would do the same.

In response to Paste action MetaVis Migrator will display Copy Terms Wizard. Here we select Copy With Children to copy the whole term tree. We also select Merge that will instruct MetaVis to reuse the terms that already exist in the tree instead of generating an error. We click Finish to complete the copy process.

A couple of seconds later we pass a completion message with detailed log about what was actually copied. Here we observe the result – term set Cameras looks exactly like it looks in the source environment including our updates in the Canon branch. Hopefully, this time our users will stop updating taxonomies in our SharePoint 2010 beta and they will switch to our SharePoint 2010 RTM. If not then we will repeat this procedure again.

Advertisements

Tags: , , , , , , , , , ,

2 Responses to “Merge SharePoint 2010 Term Sets using MetaVis Migrator”

  1. One Year in MetaVis Development « MetaVis Architect for Sharepoint Says:

    […] many SharePoint 2010 specific features like copy and map managed metadata fields, copy and merge term sets, copy document […]

  2. MetaVis Blog» Blog Archive » One Year in MetaVis Development Says:

    […] many SharePoint 2010 specific features like copy and map managed metadata fields, copy and merge term sets, copy document […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s


%d bloggers like this: