Of course you can export the metadata into whatever
you want. The metadata is housed in the host server as
a database so the app server can query against it, or
you can export the meta data and the category
structure as an XML file and deal w/ it that way.

The tool does have some work to do in this area, but
I'm sure you can get started right now w/ what you
need. Why? b/c I helped design it. ;)

-- dave

--- mikejaixen <mikejaixen@...> wrote:
> Tools like this (or Interwoven's MetaTagger) appear to have a great
> deal of power to help categorize content. But they essentially stop
> after the content is categorized in the repository.
>
> They still lack the tools that allow me to export that metadata into
> a navigable web site, except through <META> tags that can be
> utilized by search.
>
> Perhaps CIS is different (we looked at Documentum until they
> cancelled on us), but I still haven't seen the power to take that
> metadata and taxonomy, and push out the structure of a web site.
> It's very disappointing to see much of the information I need buried
> deep inside the CMS, and no way to easily pull that information out.
>
> (As for the comment on being web centric, I plead guilty as charged.
> But I don't know that the need to be able to maintain a web IA of
> content is any different than the need to be able to maintain any
> other organization of content. The difference is merely the
> publication.)