[Zope-CMF] Metadata tool not used?

[kapil thangavelu]

i brought up this exact issue a few weeks ago

http://lists.zope.org/pipermail/zope-cmf/2002-July/013597.html

i was hoping for a response to my second email in that thread (hint, hint ;-).

basically i agree that its a site policy for metadata enforcement, but i 
think its an easily correctable *flaw* that the metadata tool isn't wired in 
by default. such that actual enforcement of a policy requires mucking about 
with the cmf internals or doing type by type enforcement in editing code.

this issue is apart from the ui perspective of metadata elements on forms, 
which i agree should be dealt with by a customized skin/product.

cheers,

kapil


On Tuesday 23 July 2002 08:28 am, Tres Seaver wrote:
> On Mon, 2002-07-22 at 04:35, Chris Withers wrote:
> > Hi,
> >
> > I was playing with the portal_metadata tool and noticed that it's not
> > actually used anywhere :-(
> >
> > In particular:
> >
> > - initial values of metadata are not set on content, so defaults supplied
> > are not used
>
> This one would make sense to do pretty much universally, I think (not
> much tradeoff here).
>
> > - validateMetadata is never called, so any policies about fields being
> > required, etc, you create are never used
>
> When to apply such policies is a policy choice in itself;  for instance,
> some sites might want the policies applied at each edit, while others
> might want them applied only at workflow transitions, etc.
>
> > - the metadata forms are all hard-coded so that if you add new elements,
> > or change the type of the ones there, the news elements aren't available
> > for editing.
>
> Skins are *supposed* to be customized!
>
> > Is this how it's supposed to be or am I missing something?
>
> Tres.