[Zope-CMF] Re: Zope-CMF digest, Vol 1 #1289 - 12 msgs

[Carl Rendell]

Tim,

I have a case that is similar for ISO 9000 documenation, but my 
implementation is quite different.

I put all of these documents in a single container (folder), and 
allow users to create new versions of the same document via copy 
and paste for update. The new document is created in a 'private' 
state (thanks to CMF changes), and can be edited before using 
standard work flow.

I allow the 'latest' document to appear by using standard search, 
sorting on Date, and using a batch size of one. You could slice the 
results set as well.

In my case this allows consumers of the document the ability to see 
the latest - once published - and keep history in full without 
resorting to a complex object that has attributes that retain their 
individual history.

Definitely a low tech approach, but it works for me.

~C

On Thursday, August 15, 2002, at 10:25  PM, zope-cmf-
request@zope.org wrote:

> Message: 11
> Subject: Re: [Zope-CMF] Howto use CMFStaging?
> From: Tim Hoffman <timhoffman@cams.wa.gov.au>
> To: Shane Hathaway <shane@zope.com>
> Cc: "Zope-CMF@zope.org" <Zope-CMF@zope.org>
> Date: 16 Aug 2002 13:21:20 +0800
>
> Hi Shane
>
> OK, I am quite willing to give it a go.
>
> My case I think is fairly general for publishing of content within CMF,
> and I really need Versioning/Locking.
>
> In the current cmf, I can
>
> 1. create content
> 2. submit content for review
> 3. review content either approving, or rejecting it.
> (and obviously create other workflow variations)
>
> and now I have published content. I have to then be able to
> allow a content author to edit the published document, b currently I
> must force a retract, so that the publishing process is
> then revisited for every change (other wise someone could make
> undesirable changes). But this then means the old (approved version) of
> the document is no longer visible
>
> What I want to achieve is to allow the content author to edit the
> published document, but with some form of version control/locking
> which means when the published document is edited, a new version is
> created which is automatically retracted, leaving the previous version
> still published and accessible.
>
> Once the new unpublished version is approved, it becomes the new
> published visible incarnation of the document.
>
> I have no idea if CMFStaging could be used to implement such a process.
>
> If you think this could be done, I am quite willing to build, and
> document as a tutorial the required steps, code etc....
>
> I may need some help though.
>
> Is this requirement even feasible. I have to embark on such a solution
> and if I can utilise CMFStaging all the better.
>
> Regards
>
> Tim Hoffman

Carl E. Rendell
Solution43
Information Distribution Consulting        |   "Ahhhh the power of
cer@sol43.com                              |    acquisition"  - Chef Z