SharePoint 2013-Concept Searching Enables Migration of Term Sets While Maintaining GUIDs

News Upcoming Webinars Trade Shows and Events Press Releases Newsletters Blog

SharePoint 2013-Concept Searching Enables Migration of Term Sets While Maintaining GUIDs

Along with our other SharePoint and Office 365 announcements we are happy to have solved the inherent issue within SharePoint of maintaining the Globally Unique Identifiers (GUIDs) when migrating term sets from one environment to another, such as from test to staging and staging to production.

This is an important announcement, following other recent statements from Concept Searching about its technologies being SharePoint 2013 and Office 365 ready, and accompanies the native integration that already exists with SharePoint 2007 and 2010.

Managed metadata terms and term sets each have unique GUIDs. Until now, when a SharePoint administrator takes a backup of a staging site that is using managed metadata in some columns in a list, and seeks to restore or migrate it to production, the GUIDs do not match up, resulting in a manual term by term process to re-align the GUIDs. While this is fine if the number of terms is small, it is of no use for enterprise clients, with many thousands of terms.

There have been some custom code utilities written to address this, and Microsoft offers some best practice advice, but what enterprise customers have been looking for is a way to manage the term sets using a simple migration process integrated natively with the platform.  Concept Searching’s conceptClassifier for SharePoint has solved the problem, and enables clients deploying the tool to migrate term sets, while maintaining the GUIDs from one environment to another.

• Term sets can be created on a staging server and then migrated to production using a simple export/import utility. The term sets can then be used independently on staging, production, or indeed any environment to tag documents with metadata.
• When the term set is updated on staging it can be migrated again to production, following a normal business approval cycle. The updated term set continues to work with all documents on production, because all existing term GUIDs have been preserved during the update.

To read the press release, click here.

Search Webinar