Posts Tagged ‘hierarchy’

MetaVis Platform Features Overview: Copy content types with dependencies

March 29, 2011

A content type is a reusable collection of metadata (fields) and other settings that could be applied to SharePoint items. A content type in SharePoint may have a parent content type, which in turn may have another parent and so on. A content type may also have fields some of which it can inherit from its parents and the other fields could be created right inside this content type. Content types could also be added to lists or libraries that allows them to be used to assign metadata values to items or documents.

This way, content types form pretty complex structure in SharePoint site collections. Look at the example below generated by MetaVis Architect




MetaVis Migrator for SharePoint can copy all content types including their complete parent hierarchy and fields when a user copies a list or library that used these content types. MetaVis Migrator also reproduces source content type hierarchy in the target environment when copying the whole site.


Recently we added the function that allows users to copy just one selected content type from one site to the other one in one operation including all tree of the parent content types and all fields in these content types.


Select source and target sites in MetaVis Navigation Tree, Start Compare, expand Content Type compare area, select the content type to copy and click Copy from Left to Right button (or Copy from Right to Left button depending of the circumstances)



Using this operation MetaVis Migrator will copy the selected content type and all its dependencies.


MetaVis Change Manager allows scheduling content type copy activities using simple copy / paste or drag-n-drop gesture on MetaVis Navigation Tree. Unlike MetaVis Migrator, Change Manager displays content types in the navigation tree and allows copying them between different sites.



A part of MetaVis Change Manager functionality is to execute activities for multiple source and target site pairs provided by Excel spreadsheet. This function allows to mass-distribute content types between multiple site collections as a part of an execution of a single activity.

Merge SharePoint 2010 Term Sets using MetaVis Migrator

July 28, 2010

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.