Skip to content

Personal tools
You are here: Home » CMF 1.3 flexible metadata patch

CMF 1.3 flexible metadata patch

Working with the CMF can be fun - but also can be a pain. While using CMF for a customer, we discovered the missing functionality of flexible adding new metadata elements. This problem has been adressed by this patch.

Maintainer

Christian Theune ct@gocept.com

Current Version

stable
none
development
11282002-0754

Details

You use Zope? Ever used the CMF? It's fun, isn't it? Ever tried adding a new metadata element? - Now you can simply click a button and got a new metadata field, with flexible validation algorithms (Dictionary, String, Text, Date) and a new Metadata-Index.

BEWARE! This patch may be very unstable, but is in production use here at gocept. We didn't test it exhaustively but it runs very fine. This is only a disclaimer that we don't take responsibility for anything this patch may disturb, destroy or beam to another planet. Migration from current CMF 1.3 installations should work, but this is very unlikely. Best method to test is: Make a backup of your ZODB, remove the Metadatatool and install the CMFDefault:Metadatatool again. Your metadata configuration will be lost, but the metadata itself will be kept. Good luck.

Features

  • Modularized validation code
  • Flexible "proxy index"
  • Metadata elements independent of original object attributes
  • Editable ZPT formular.

You need Zope CMF 1.3 for running it.

A README with Installation/Configuration instructions is provided with the distribution.

ChangeLog since last snapshot

  • 27.11.2002
    ctheune
    The bug when adding a new field with a vocabulary seems to have gone. I don't know why.
  • 26.11.2002
    ctheune
    possible fix for Metadata if REQUEST has no "pop" method.
    ctheune
    getMetadata of PortalContent had a non-Default value "default" argument
    ctheune
    Fixed the kw argument. "kw" was already used in this function and so shadowed the kw argument.
    ctheune
    refixed the default dictionary. Of course it has to be a list. It's a list of valid values. Need an other fix for the problem.
    ctheune
    fixed catalog updates after changing the metadata
  • 25.11.2002
    ctheune
    Forgot the **kw argument in updateElementPolicies.
    ctheune
    Default dictionary was a list instead of a dictionary.
  • 22.11.2002
    ctheune
    moved reindexing after on metadata update after validation
  • 18.11.2002
    ctheune
    Updated Metaindex which had problems with wrong function results (None is unslicable )
    ctheune
    NullValidator wasn't compatible to FieldIndex. Index wasn't able to index "None" values.
  • 12.11.2002
    ctheune
    CreationDate was incorrectly initialized
  • 04.11.2002
    ctheune
    Dictionary input validator will show correct textarea sizes now.
  • 28.10.2002
    ctheune
    forgot to reindex objects after a metadata update. fixed.

Locations

You can download all releases from from ftp://ftp.gocept.com/CMF_metadata/.

Snapshots

Created by admin
Last modified 18.05.2003 21:40
 

Powered by Plone

This site conforms to the following standards: