[Zope-PTK] Another use case for reviewing

[Jochen Haeberle]

Hi,

please excuse my intrusion into this thread. I must admit I did not
find the time to install PTK anywhere yet. Nevertheless I would like
to throw in my thoughts and more importantly wishes for this great
new thing, as I might have needs not mentioned yet.

Kevins ideas are really great - I guess he has seen many things on
portals because of his KM|net news, which I like very much, too.

As to the reviewing I would like to add my thoughts, because I have
not found any mentioning of this:

It is quite possible that people are considered Reviewer on one
Topic, but only contributor on another. Let's think of a news site
with several very different topics, no one can be expert in all the
fields, you will probably designate several people or groups for
different areas.

I think this is very important setting for the proposed role of of a
direct contributor, whose articles need not be reviewed. I don't
think many people would like that role to work on all areas of a site.

I don't know if this is already covered by PTK at the moment, but it
is not mentioned in the docs nor was there talk about it on the list
that I am aware of...

Jochen

At 11:23 Uhr -0500 22.01.2000, Kevin Dangoor wrote:
>     Thus far, all of the talk about reviewing of new content has centered
>around people having documents that they are individually responsible for
>and that live within their member folders. I could also see cases where
>there are groups responsible for maintaining certain objects. Let's call it
>the "IMDB model".
>
>     It may be possible to do this through Versions. But, then you'd probably
>run into difficulty if two people change two different properties of a movie
>before the change for the first one is reviewed.
>
>     There could be an object that basically contains information about the
>change. It could just be a dictionary of "property" and "new value"
>pairings. I think Versions would work great, if the whole object wasn't
>locked when a property changes...

Versions would be really great, it even implies that the problems
with versions changing cataloged object need to be resolved :-)
I guess one could live with the drawback that every change needs to
be reviewed before another could be made...

On the other hand, do you know the approach MS gives to the problem
of several reviewers in Word? For every editor the changes get
colored differently, deletes are marked striked-through.
I guess this could be transferred to Zope and would be helpful for
the reviewer anyway (see the old version and what was changed).

You could display the text in the described form on one side, the
editable code in the last state on the right for editing or
additional changes and a reviewer could be presented one change after
another for approval or rejection.

>     Anyhow, this is not something that needs to be in ZPT 1.0. But, it is
>something that I think has many applications beyond movies...

Well, as many good changes and additions should make it into ZPT as
soon as possible :-) but I guess this will take some time to work on
:-( But I think the need for reviewing groups and ways to handle the
groups and the work to be done (locking an article when one is
already reviewing it) for them is very important for the PTK as they
defenitely make it aim at bigger projects/clients.


Jochen