Content Management Matters ™

The eTouch team have released a new version of their enterprise Wiki platform today. Highlights of the update include greater support for internationalized content and an import function which will migrate content from your old Wiki, or from HTML sources, straight into your spanking new SamePage Wiki.

This is the third and final article in our series on migrating content from a previous version of Vignette to Vignette V7. The first article in the series painted the broad overview and in the last article we talked in detail about the Content Analysis part of the process. Now, we continue by digging into the final planning phase: Defining the Migration Approach.

When we left off from part one in this series, we mentioned that there are four steps involved in the content life cycle migration process -- analyzing the content, deciding on a migration approach, the actual migration and post-migration processing. Here in part two, we go into detail on the Content Analysis step.

Vignette revamped its Web Content Management technology with version V7 to adopt industry standards J2EE, XML and Web Services. While this move helped customers lower total cost of ownership by leveraging open standards and application server services, it posed new challenges in migrating existing sites running on earlier versions V5/V6.

V7 introduced an entirely new architecture, making V6 implementations almost obsolete. Customers going for the V7 platform have to model, design and rebuild the site.

Along with re-engineering the site, one of the most critical tasks in V7 migration is to rebuild the content into new V7 server from an old story server. As re-creating the whole site content is quite a tedious task, customers might wonder if there is any way out.