Catalog Center creates highly dynamic, easily navigable catalogs of content.
Catalog Center makes is an ideal solution for sites where visitors are looking for specific content. Using Catalog Center, developers can rapidly create sites that include sophisticated searches, comparison tables, and dynamic drill-downs.
In addition to the features and functionality of Content Server and Content Center, the following are major features of Catalog Center.
|
Feature
|
Benefit
|
|
Business Manager
|
|
Intuitive interface
|
An easy-to-use interface makes it possible for business managers such
as marketers, product managers, and reviewers to perform editorial tasks
without requiring IT intervention. This improves productivity, minimizes
bottlenecks and lowers the total cost of ownership of the content management
system.
|
|
Browser-based content entry and modification
|
A browser-based interface enables remote contribution of content and
minimizes IT headaches of managing client software. Thin client architecture
reduces the overhead of upgrades.
|
|
Flexible categorization schema
|
By organizing data into logical categories, business managers can increase
their efficiency by dealing with manageable chunks of data that can be
modified as a group. For instance, a business manager could group all
products or content that will be used as part of a summer special into
a group for easy modification.
|
|
Cross-asset management (i.e manage articles, products, and images through
a single interface)
|
Business managers can manage any type of content through a single interface
instead of using one interface to manage products and another to manage
articles and other related content. Products and articles can be associated,
cross-referenced, and workflowed together. This enables enterprises to
leverage their information assets by providing a comprehensive, consistent
view of any type of information.
|
|
System Developer
|
|
Customizable content acquisition
|
Using a variety of mechanisms (including XML Post, and a Bulk Loader)
existing data stores can be leveraged by Catalog Center. Such data can
then be merged with other rich content as part of the editorial process
or passed directly through Content Server templates for delivery.
|
|
Flexible hierarchies/inheritances
|
Flexible hierarchies of broad depth and breadth and a sophisticated inheritance
model make it possible for sites to deal with large volumes of structured
or categorized content. Here are two examples:
- A shoe may belong to the "football shoe" category, the "Nike" category
and the "specials" category. (Each category could belong to other categories
as well. For instance, the football shoe category might belong to the
"men's shoes" category). Products can inherit values from the categories.
For instance, a category of shoes could inherit that it is a Nike shoe
from one parent, and that its discount code is 1390 from another.
- This structure is useful not only for organizing products, but other
content as well. A financial services firm may offer funds that are
organized into fund families, type of investment, and typical investor
profile.
Hierarchies make it possible to effect change on groups of information
simultaneously (for example: all funds in Fund Family X need to have a
special disclaimer). Additionally, hierarchies enable content to be organized
so that visitors can drill down through content and search and sort content
dynamically.
|
|
Flex-asset technology
|
Flex-assets make it possible for system developers to rapidly create
new asset types or make changes to existing assets without changing the
underlying database schema. This saves administrators time during system
design while affording them flexibility for inevitable changes that come
down the road.
|
|
Site Developer
|
|
XML development environment
|
Template developers work with familiar XML code to create Content Center
templates. As Catalog Center tags are extremely efficient and flexible,
developers can avoid using SQL-something that saves time both during development
and during upgrades and system changes. Of course, SQL can be used if
a developer deems it necessary.
|
|
Order form development
|
Catalog Center includes an extensive set of tags which enable developers
to create a fully customized order process. Because this is managed as
a content management process (as opposed to a part of a commerce or ERP
engine), developers can leverage standard techniques such as caching,
personalization, or pagelet design as part of the order process. Cart
objects can be presented anywhere on a site, such as "cart quickview"
on a product page. Using Commerce Connector and Integration Center, the
Catalog Center order form can be connected to back-end systems such as
ERP systems.
|
|
Powerful search/navigation mechanisms
|
Key to any highly dynamic catalog site is the ability to find and sort
content efficiently. Template developers can rapidly employ a range of
search and navigation techniques through Catalog Center XML tags. Examples
follow below:
|
|
-Rich text
|
During the attribute creation process, system developers can determine
which attributes should be indexed by a rich text indexing engine such
as AltaVista.
|
|
-Hierarchical search
|
Developers can create sophisticated hierarchies that enable site visitors
to drill down to a particular piece of content. Content can be placed
at any node in the hierarchy and can belong to an unlimited number of
groups. For instance, a shoe may be categorized by manufacturer, price
range, style, and use-making it possible for a site visitor to find such
a shoe by drilling into many different categories.
|
|
-Parametric search
|
Parametric Search allows a user to specify a series of product attributes
that define the products (for example running shoe, size 9, price range
of $50-80). As the user drills down level-by level, only categories that
have valid results are shown (i.e. if there are no size-9 running shoes
in the $40-49 price range, but there are shoes in the $50-80 range, the
user would be given the option to drill down into the $50-80 range but
not the $40-49 range.)
|
|
-Mixed mode search
|
In a single search, a developer can employ both database and rich text
searching-enabling a user to search, for example, on both a series of
attribute parameters and rich text from a product or article.
|
|
-Search refinement
|
Users can choose to continue a search based on the returned result-set
or on the entire product category, enabling them to narrow searches.
|
|
-Dynamic ruleset presentation
|
Site visitors can choose to view products in a comparison table. Table
content can be dynamically rendered based on user input (i.e. a visitor
can select two shoes and choose to see a comparison table that comprises
price, colors, and tread material).
|
|
Integration
|
|
Content Server/Content Center
|
Catalog Center leverages the strengths of Content Server
to provide an open, scaleable platform for management and delivery of
dynamic content. Catalog Center also utilizes Content Center technology
to provide an intuitive interface in which business managers can manage
content.
|
|
Back-end integration
|
When combined with Integration Center or Commerce Connector,
Catalog Center supports real time queries to back-end systems such as
ERP systems, transaction systems, or CRM systems.
|
|
Marketing Studio integration
|
When combined with Marketing Studio, enterprises can further
leverage their content by cross-selling, upselling, and merchandising
content to targeted visitor segments.
|