Get the real story via our monthly newsletter

Search

    2
    0

rss

Send to a colleague

Home > Commentary > Trends Archive > Migrating from Vignette

Browse TrendWatch Blog

Recent Blog Entries

The Complete Archive

Trends by Vendor


TrendWatch by Channel

Web Content Management Trends

Enterprise Portals Trends

ECM Trends

Web Analytics Trends

Enterprise Search Trends

SharePoint Trends

Digital & Media Asset Management Trends

XML & Component Content Management Trends

E-mail Archiving & Management Trends


Report Excerpt

The Web CMS Report 2008 looks at... Vignette Content Management

"One area where experienced content engineers will find Vignette lacking is in XML support. With its optional integration tool called "VBIS," you can import and output XML content, but while managing content, Vignette sticks to a straight relational model. Like most other CMS tools, Vignette can represent content as XML, albeit using its own schema (you cannot use arbitrary or industry-standard schemas in the management environment). The problem is not that the product uses a database for storage (most packages do that). Rather, by natively lacking strong notions of hierarchy, the product can work in unexpected ways, such as..."

(p. 244)

More about The Web CMS Report 2008

 

TrendWatch Blog

Migrating from Vignette

05-Jan-2006

Longtime readers know that an "upgrade" from Vignette's V6 to V7 CMS is really a complete product swap that has tempted many licensees to consider alternate packages. UK content migration software vendor Vamosa has developed a "Vignette V5 and V6 Migration Roadmap." (registration required, via Janus Boye). The white paper is tad too critical of Vignette and unduly promotes an alternative from Vamosa's close partner, IBM (which CMS Report readers know is a bit behind on the WCM front). Nevertheless, the paper offers some good general advice on migration, including the need to look beyond the act of transferring live pages. Vamosa points out that CMS migration also means moving and likely transforming: previous document versions, metadata, binary assets, and templates -- which are especially tricky when business and display logic get co-mingled. And often the best way to get at all that stuff is through your existing CM tool's API.

- Submitted by: Tony Byrne, Analyst

All CMS Channel Trends

Join the conversation

Digg This! Search Technorati Tag it on Del.icio.us



Get a Free Sample

Wondering about CMS Watch research? Sign up to receive free samples of any of our products.




What we do

CMS Watch™ evaluates content-oriented technologies, publishing head-to-head comparative reviews of leading solutions. What makes us special?

  • Our critical analysis exposes product weaknesses as well as strengths
  • We deliver unrivaled technical depth and comprehensive project advice
  • Our research is led by international topic experts
  • We only work for buyers -- never for vendors

Contact us

CMS Watch

info@cmswatch.com

18113 Town Center Drive, Ste 217

Olney, MD USA 20832

1 800 325 6190 (customer service)

+1 617 763 5336 (int'l customer service)

Fax: +1 214 242 3048