[Zope-PTK] Catalog system

[Kevin Dangoor]

Hello,

    I hope you don't mind the intrusion, but Paul let me in :)

----- Original Message -----
From: "Mike Pelletier" <mike@metamike.net>
To: "Paul Everitt" <paul@digicool.com>
Cc: <zope-ptk@zope.org>
Sent: Friday, January 14, 2000 12:55 PM
Subject: Re: [Zope-PTK] Catalog system


>     Presently, Members can abuse Zope.org by--
>
>   - Adding abusive content and not cataloging it.  They can then publish
>     the URL elsewhere.
>
>   - Adding acceptable content, having it reviewed and then replacing it
>     with abusive content.  This is especially bad, because their content
>     could very well be your front page headline.

You just negated a message that I was about to send :)

The crux of my message was that News Items were different from regular items
because they don't need to be "maintained" after they are created, and so on
and so forth, touching upon exactly what you mention above. By eliminating
the above possibilities for all items, I think it's fine for News to be
treated like the rest...

    With the exception that you probably don't want News Items to be deleted
without manager approval, because they are quite possibly part of an RSS
story flow that is showing up on sites all over the place, and you may not
want the link to suddenly just go dead...

>     Here's an idea, though perhaps one for the future-- Once an object is
> 'public', all changes to it automatically get made in a version.  Only
> reviewers would have the ability to commit the version to the public
> object.

This idea is nice, just as long as the version doesn't lock the whole
catalog (as it does now).

In general, I'll shut up until I've had a chance to look things over more.
Just wanted to say that I think your line of thinking here is great!

BTW, we'll be using PTK components for something very different from
Zope.org. But, it looks like the things you all have in mind are quite
flexible.

Kevin