Hash: SHA1

mark hellewell wrote:

> I'm making a site that has a requirement for metadata and am
> unsure about the best way to proceed; whether or not to extend
> the CMF MetadataTool or create something afresh. Having looked
> at and played with the standard MetadataTool there are some things
> missing that I really need to have: 1) the ability to have different
> sets of metadata elements applicable to objects (but not based on
> that objects type), 2) the ability to configure the order in
> which metadata elements appear (when editing, searching etc.).
> And example of 1) is to have two sets of metadata elements:
> (food brand: 'colour', 'flavour', 'shape') and (car: 'size',
> 'horsepower', 'weight'). Now,
> for an uploaded object I want to choose which set of metadata
> to use.
> Any thoughts or insight would be greatly appreciated... It just
> feels like it would be a lot easier to implement my own tool.

You might look at morphing the current tool to add a 'schema' parameter
to the API methods, and then creating a MetadataSchema folder inside the
tool for each schema you need to support.

I imagine most of what you would be doing is copying the current tool
implementation to create the 'MetadataSchema' implementation, and then
causing the tool to locate and delegate to the correct schema.

I would be glad to see such an implementation contributed back to the
CMF, in fact.  It would be even nicer if we could do the CMFSetup export
/ import for it, to make the core bits "policy free";  we could then
figure out how to "wire up" the tool from the import / export bit,
rather than hardwiring it (likely via an event mechanism).

- --
Tres Seaver          +1 202-558-7113          [EMAIL PROTECTED]
Palladion Software   "Excellence by Design"    http://palladion.com
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org


Zope-CMF maillist  -  Zope-CMF@lists.zope.org

See http://collector.zope.org/CMF for bug reports and feature requests

Reply via email to