[Zope-CMF] List of subject/metadata sets?

Jon Edwards jon@pcgs.freeserve.co.uk
Tue, 5 Jun 2001 16:16:38 +0100


(Note to self : Remember to engage brain before typing!)

Yes, you're right - and as Marc pointed out, you can have everything you
need in one catalog.

I guess where I'm coming from, is that the catalog is serving two purposes,
and sometimes it gets confusing to a relative newbie like me -

1. For the end user it allows them to search the whole system, and is quite
often used to "construct" the pages - topics and sub-topics - they are
viewing. I'm assuming it will also be used in some way to construct
composite-documents. With a large site, containing many sub-sections (or a
large organisation with quasi-autonomous sub-organisations/departments) it
needs a lot of planning to allow all the possible searches users are likely
to want.

2. Behind the scenes it is interacting with workflow/workgroups to allow
people to process documents from creation to publication. ...and I'm still
trying to wrap my brains round how Composite Documents and Versioning will
fit into it all. This is assuming you have a site with multiple
editors/contributors working on many sections/subsections/pages in different
workgroups.

I guess at some scale the complexity reaches the point where you need to
separate the two functions... and my needs are somewhere in that vicinity!
:-)

i.e. you have two portals/catalogs, one for the internal organisation to do
its workflow, collaboration, discussions, document-sharing (perhaps on their
intranet)... and one where the finished results are published, and the
public can view, search, discuss. But you still want some two-way connection
between the two.

Is anyone else reaching similar levels of complexity? Maybe I should
re-factor and "divide and conquer"!!

Sorry if this makes no sense! I think I'm having a bad-brain day!

Cheers, Jon

--------------------------------------------------
> Going off at a tangent, does anyone ever get the feeling that you maybe
need
> two portal_catalogs? One for end-user searching, topics, etc. and one for
> the internals, composite-docs and that sort of stuff?

How do you mean?  Wouldn't that mean you end up with lots of objects
being indexed in two places?

seb