 |
|
|
| |
|
Content Management |
|
|
|
|
| |
|
Content Management criteria describe the various features
and functions that facilitate the management of content. |
|
| |
|
Factor: Standard |
|
| |
|
Product Name |
TeamSite
4.5 |
V/5 Content Management
Server
5.5 |
engenda
1.0 |
Authoring Server
Suite
2000 |
Spectra
1.0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
Manufacturer |
Interwoven |
Vignette |
eBusiness
Technologies |
NetObjects Inc. |
Allaire
Corporation |
|
| |
|
|
Group Score:
460 out of 580
Total Score:
1302 out of 1660 |
|
Group Score:
436 out of 580
Total Score:
1266 out of 1660 |
|
Group Score:
412 out of 580
Total Score:
1188 out of 1660 |
|
Group Score:
344 out of 580
Total Score:
861 out of 1660 |
|
Group Score:
176 out of 580
Total Score:
805 out of 1660 |
|
| |
|
Automated
Link Creation |
|
| |
|
Weight: 3 |
|
Weighted
Score:
4
|
|
Weighted
Score:
16
|
|
Weighted
Score:
16
|
|
Weighted
Score:
16
|
|
Weighted
Score:
0
|
|
| |
|
|
TeamSite does not support automatic link creation out of the
box. However, automatic link generation can be accomplished using an
application server and DataDeploy. |
|
Through the use of category/keyword pairs associated with
individual content or code fragments, Vignette can allow site
designers to build intelligent links between pages and content; a
simple business rule can then dynamically retrieve related
items. |
|
engenda provides linking among other page and site
components via metadata. Users need not know the URL of a page, they
instead choose where in the site's category structure the content
should go, which allows flexibility in publishing, as the categories
can be mapped to one or more physical site structures. |
|
Automatically creates links and navigation bar images based
on the site structure. Customization options for the automatically
created links are not very extensive. |
|
None. |
|
| |
|
Check
In/Check Out |
|
| |
|
Weight: 5 |
|
Weighted
Score:
64
|
|
Weighted
Score:
64
|
|
Weighted
Score:
64
|
|
Weighted
Score:
32
|
|
Weighted
Score:
16
|
|
| |
|
|
TeamSite supports three types of Locking: Submit Locking
enables concurrent file use, but gives lock holders priority in
submitting to the staging area. Optional Write Locking prevents
other users from editing a locked file. Mandatory Write Locking
makes all files in a Workarea read-only until a user locks them for
editing. Locking options are configurable by the
Administrator. |
|
V/5 provides advisory locking functionality. All projects,
files, records, and templates, are automatically locked. If another
user opens the file that is already open, they are warned that the
file has a lock. The user can then open the file in read only mode,
or claim the file. |
|
Downloading a file for editing checks the file out and locks
it. A padlock icon displays next to the item. It is possible to
allow the same file to be edited by different people; however, they
cannot upload the file to be published. |
|
Adding a source code file as an asset would allow it to be
checked in or out. |
|
Spectra integrates with Source Safe on Windows which
supports checking files in and out. |
|
| |
|
Component
Search |
|
| |
|
Weight: 3 |
|
Weighted
Score:
8
|
|
Weighted
Score:
12
|
|
Weighted
Score:
12
|
|
Weighted
Score:
0
|
|
Weighted
Score:
0
|
|
| |
|
|
Users can perform a rules-based search to search for both
metadata and TeamSite Templating content. |
|
V/5 includes the Vignette Application Power Pack (Power
Pack), which is a set of prebuilt tools designed to accelerate the
assembly, deployment, and management of e-business applications. The
Power Pack contains an embedded search engine technology which can
be used. As content is added through the Power Pack Content
Management Application, it is automatically indexed by the search
engine and is immediately available to users of the site. |
|
A
comprehensive search allows for searches of items or content by
specifying the search criteria (name, content, creation date,
edition, custom, properties) from a drop down menu, and selecting a
match option. Wildcard searches are also possible. |
|
No. |
|
Component searches are not supported; however, the Object
Finder does maintain a list of all created components. |
|
| |
|
Content
and Metadata Storage |
|
| |
|
Weight: 4 |
|
Weighted
Score:
24
|
|
Weighted
Score:
24
|
|
Weighted
Score:
24
|
|
Weighted
Score:
24
|
|
Weighted
Score:
24
|
|
| |
|
|
TeamSite can store both content and metadata either in a
file system or database. |
|
Metadata, categories and keywords can be assigned to each
content item. The content itself is stored in a database (Oracle,
Sybase, SQL Server or DB2) or on the file system. |
|
All file-based content is stored in an object-oriented
database in its native file format and is organized hierarchically
using metadata. Data from web or other applications is stored
separately in either traditional files or relational
databases. |
|
Content and metadata are stored in a database internal to
the site. Content can also be stored in external sources such as
Excel, Access, ODBC, and JDBC databases. |
|
Spectra can store metadata within the supplied database or
an external database such as MS SQL. |
|
| |
|
HTML
Contribution |
|
| |
|
Weight: 4 |
|
Weighted
Score:
32
|
|
Weighted
Score:
24
|
|
Weighted
Score:
24
|
|
Weighted
Score:
16
|
|
Weighted
Score:
16
|
|
| |
|
|
Each user installs an application called LaunchPad which
allows the user to configure which HTML authoring tool to use with
HTML files. In addition, any tool can directly access the TeamSite
server via a normal network file system. |
|
HTML files are created and edited outside the Production
Center using any editor desired and then submitted to the Production
Center. When the file is added to the Production Center, it creates
a new Production Center file. When an HTML file needs to be
modified, it must be resubmitted to the Production Center. |
|
HTML files can be contributed with the engenda client or any
third party authoring application. |
|
TeamFusion Client and the Content Contributor Client are the
only tools supported out of the box. Licenses must be purchased for
each of these applications. Content Contributor is only appropriate
for adding data to existing or new pages. |
|
ColdFusion Studio as Allaire HomeSite works well. Any text
editor could also be used. |
|
| |
|
Import
an Existing Website |
|
| |
|
Weight: 5 |
|
Weighted
Score:
80
|
|
Weighted
Score:
80
|
|
Weighted
Score:
64
|
|
Weighted
Score:
80
|
|
Weighted
Score:
16
|
|
| |
|
|
Both local and remote websites can be very easily imported
into TeamSite. Users can simply drag and drop an existing web site
into a Workarea via TeamSite's file system interface. |
|
Both local and remote sites and pages can be very easily
imported. The process involves submitting the file or folder to the
Production Center. |
|
Existing websites can be imported with drag and drop;
however, sites must be stored locally and mapped to a Windows drive.
engenda can also import existing sites or portions of sites in
batch. |
|
From TeamFusion Client, local and remote sites can be
imported. |
|
Spectra uses proprietary tags making it unfeasible to import
existing sites unless the sites were created with ColdFusion
Studio. |
|
| |
|
Integration
with Multiple Tools |
|
| |
|
Weight: 4 |
|
Weighted
Score:
40
|
|
Weighted
Score:
24
|
|
Weighted
Score:
32
|
|
Weighted
Score:
16
|
|
Weighted
Score:
8
|
|
| |
|
|
TeamSite has outstanding tool integration capabilities. Each
user installs an application called LaunchPad. LaunchPad allows
users to configure which tools to use with which files. In addition,
any tool can directly access the TeamSite server via a normal
network file system. |
|
Content and templates to be delivered from the V/5
application can be built using any tool then submitted. Vignette
provides its own development environment. Content entry can be
integrated into Microsoft Office using VBA, as well as the WebEdit
Pro tool. |
|
engenda integrates easily with a wide variety of tools that
can be used to create and edit content. |
|
NetObjects integrates with Microsoft FrontPage, which
requires purchasing licenses for NetObjects FrontPage Connector.
External HTML can also be referenced, but this is not an acceptable
workaround. A Macromedia Dreamweaver Connector and Business
Documents Connector that allows any user to contribute to the web
site from within the desktop application they use to create it are
also available. |
|
Spectra integrates well with other Allaire products.
Integration with other third party products requires an API to a
standard object model such as COM or CORBA. |
|
| |
|
Link
Checking |
|
| |
|
Weight: 3 |
|
Weighted
Score:
0
|
|
Weighted
Score:
0
|
|
Weighted
Score:
0
|
|
Weighted
Score:
16
|
|
Weighted
Score:
0
|
|
| |
|
|
TeamSite does not include link checking. For this
functionality, TeamSite relies on third party link checking tools,
which work out of the box with TeamSite's file system
interface. |
|
Personalized Vignette applications can be developed with
links being automatically managed to best suit the needs of each
individual. The Vignette application can track the individual
visitor and store their profile, enabling the application to feed
them content in line with their requirements, without the need for
developers to hardcode links. |
|
Internal links are managed by the engenda system and
organized by metadata. Therefore, links are managed by the system
and can not be broken unless manually altered. engenda does not
support external link checking. |
|
From TeamFusion Client the Asset Screen can verify all links
in a site. |
|
Only with ColdFusion Studio. |
|
| |
|
Non-HTML
Contribution and Management |
|
| |
|
Weight: 5 |
|
Weighted
Score:
48
|
|
Weighted
Score:
48
|
|
Weighted
Score:
48
|
|
Weighted
Score:
48
|
|
Weighted
Score:
48
|
|
| |
|
|
TeamSite supports all types of non-HTML content, including
graphics, downloads, source code, server-side executables, scripts,
images, and media. They are contributed and managed just like HTML
content. |
|
V/5 Content Management Server supports all types of non-HTML
content. Non-HTML content is contributed the same as HTML files, by
submission to the Production Center. |
|
engenda supports all file types, including images, rich
media, Microsoft Office documents, and structured documents. It
provides advanced content management capabilities for standard Web
file formats (e.g. XML, XHTML, WML, DHTML). |
|
Image's and PDFs are managed by the Asset's Screen. They can
be easily added or removed from the site. |
|
Users access Spectra through a browser to add content such
as PDFs, images, and other non-HTML content to a website. |
|
| |
|
Templates |
|
| |
|
Weight: 5 |
|
Weighted
Score:
80
|
|
Weighted
Score:
80
|
|
Weighted
Score:
64
|
|
Weighted
Score:
64
|
|
Weighted
Score:
48
|
|
| |
|
|
TeamSite Templating provides extensive templating
functionality. There are two types of templates that can be used:
Data Capture Templates are rendered from XML files that define the
form for capturing content that is reusable. Presentation Templates
are files used to define how data is to be displayed, written in
XML, and can contain Interwoven XML tags, HTML, and Perl. |
|
The V/5 Content Management Server makes strong use of
templates and supports two types: Tcl templates and Microsoft ASP
(Active Server Pages) templates. V/5 uses Content Delivery templates
to create pages and Content Management templates, through which
users enter or edit content. V/5 includes a very comprehensive and
easy to understand Template Cookbook. |
|
engenda supports the use of templates for design and content
logic. engenda can also apply templates designed for specific
devices. Users can apply templates to HTML and XML without having to
perform scripting or programming. |
|
Templates are heavily supported in TeamFusion. Creating a
new site from a template is simple. The AutoSite templates take a
lot of the tedious work out of creating websites. |
|
Spectra supports the creation and use of templates to keep a
consistent format throughout the application |
|
| |
|
Versioning |
|
| |
|
Weight: 5 |
|
Weighted
Score:
80
|
|
Weighted
Score:
64
|
|
Weighted
Score:
64
|
|
Weighted
Score:
32
|
|
Weighted
Score:
0
|
|
| |
|
|
TeamSite maintains extensive file version histories.
Versioning prevents the copying of files over existing versions;
allows for comparing files in Workareas, staging areas, or editions;
and allows for comparing file details, visual differencing, source
differencing, merging files, and reverting to older versions. When
DataDeploy is used, database content version histories are
maintained for content created with TeamSite Templating. TeamSite
versions not only individual assets, but also entire web sites
through TeamSite Editions. |
|
V/5 Content Management Server provides extensive version
control that can be used if desired. Versions can be created for
items (files, records, or templates) or for a project and all the
items in the project. Versioning can also be implemented in workflow
using the version program task. |
|
engenda has extensive version control features. When an item
is checked out and modified, a new version is automatically created.
If an item is checked out but not modified, a new version will not
be created. |
|
A
backup of a site is created any time that site is published. The
site can be restored or recovered from the backup copy. It does not
automatically create a new version for each backup, but an
administrator could manually create new versions. |
|
New versions must be created the same as the original.
Adding a property to a ContentObject type to keep track of the
version is possible. |
|
| |
