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

[seb bacon]

It all depends, I guess, on the requirements for composite docs.  In
my application, Members are responsible for creating whole pages,
rather than snippets of content.  Therefore, my composite container
will only be used and indexed as a single component.  Its
subcomponents will never be moved between composites, they're never
indexed in their own right, and they only take part in a workflow
through their container.

In your example, you wouldn't necessarily need a new state.  For
example, if you are presenting all objects exclusively in composite
docs, then you *could* allow components to be published, but the only
available interface to viewing them would be through published
containers. 

cheers,

seb

* Jon Edwards <jon@pcgs.freeserve.co.uk> [010606 12:23]:
> (Thinking slightly clearer today... I hope!)
> 
> (Disclaimer : I'm not sure how composite docs will work, but I'm assuming a
> site will use them for all its presentation of objects to the end user?)
> 
> When you start using composite docs, this will solve the problem, as if all
> your user-facing pages are made up of composite docs, the user-searching and
> indexing only needs to index the composite docs. All the "components"
> (documents, images, news-items) will only be accessible as separate objects
> to members/editors. So you then get the separation of presentation from
> composition/preparation... the catalog is still serving two purposes, but
> the divide is a bit clearer... I think! :-)
> 
> However, does that mean that you will need a fourth workflow state for
> individual objects - "Published in Comp-Doc"?
> 
> So, for an example, a member would write an article, state=Private. He would
> request it be reviewed, state=Pending. The reviewer would approve it,
> state=Approved (and perhaps it would then appear in a "Content Repository"
> of available documents for Editors to insert in their composite docs?). An
> editor would include it in a composite doc for one of his pages,
> state=Published.
> 
> This might also impact on editing permissions? i.e. an object can be edited
> in any of the first three states, but not when it has been published?
> 
> Hope that makes more sense?
> 
> 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
> 
> 
> _______________________________________________
> Zope-CMF maillist  -  Zope-CMF@zope.org
> http://lists.zope.org/mailman/listinfo/zope-cmf
> 
> See http://www.zope.org/Products/PTK/Tracker for bug reports and feature requests

-- 

   [] j a m k i t 
           
        seb bacon
T:  020 7749 7218
F:  020 7739 8683
M:  07968 301 336
W: www.jamkit.com