[Zope-PTK] DISCUSS: What we want from reviewing

Mark Pratt mpratt@beehive.de
Sat, 15 Jan 2000 11:39:36 +0100 (CET)


hello mike,

On Fri, 14 Jan 2000, Mike Pelletier wrote:

> On Fri, 14 Jan 2000, Paul Everitt wrote:
> 
> > 	  <para><emphasis>Reviewing</emphasis>. By default, when a
> > 	  member authors a piece of content, the content isn't part of
> > 	  the "public site".  When a member requests that a piece of
> > 	  content get reviewed and the content is approved, it
> > 	  becomes part of the "public site".</para>
> 
>     Let's call the process of requesting and receiving a review
> 'publishing'.  I think joe user will more easilly grasp publishing an
> object that they have created as opposed to cataloging one.  The action
> will be 'Publish this object', which will take you to a form with the
> object's history and current state, with buttons for request, withdraw
> request, approve, reject, and revoke as appropreate to your roles and the
> object's state.
> 
>     As I've got it set up so far, an object has three possible
> review_states, 'private', 'pending' and 'published'.  The state is changed
> by going through a method which records the time, who changed the state,
> what action they took to do so (ie request, approve, reject), any comments
> that accompanied the change and the new review_state value.  There's no
> interface to view it yet, but it's coming.

does private mean that only users within a specific role can see
the content? for an online medical site we built we had the following
states:

public 
(or) private
is viewable

public or private was how we differentiated between content
availible to anybody and private content only for registered
accredited doctors.

we didn`t need an editor role for this project but the "is
viewable" feature was designed to give the author control
at what time an article was to enter the website cycle.

generally, we find the publishing issues you seem to
be getting into with the ptk very exciting.

we have a lot of "golden nuggets" of software from 
various projects we have done lying around beehive. 
ex: archiving of articles by:

xnumber <pulldown> days, weeks, months

we are currently working on putting some of this
code into metapublisher -- maybe we could figure
out a way to join forces here and help you embed
metapublisher code into the ptk?

do you have a version of the ptk we can take a look
at without having to install cvs?

regards,

mark

--------------------------------------------------------------
mark pratt  (managing director) 	mark@beehive.de
beehive elektronische medien GmbH       http://www.beehive.de
phone: +49 30 847-82 0                  fax: +49 30 847-82 299