[ZDP] Short !!! Implementation plans for ZDP Awareness Tools
Maik Roeder
roeder@berg.net
Mon, 20 Dec 1999 05:28:27 +0100
Hi !
I just want to give a quick update on my current implementation plans.
For this, I am just sending the notes on what has changed.
The Requirements Specification Draft has not changed much, but
there are some new ideas which I am trying out in the implementation.
Please have a look.
Thanks,
Maik
Version 0.5 20 Dec 1999
Changes:
- Dropped the original design of a state. A member can no more
select "Working on an unpublished draft", "On holiday",
"Private"
or "Too busy", because these descriptions are too restricted
to
explain the state of involvement of a member.
- A login name for a Member does not have to be kept in the
implementation. The login name is exactly the name of the
folder
in which the member creates the Member ZClass in his user
folder
For example in http://zdp.zope.org/Members/membername
- Documents have no more comments. Instead, Documents are now
Containers, which can contain a Comments ZClass which can
hold
Documents of type Comment.
Implementation
Member ZClass
property_sheets:
1. external_info
1. string: id (as provided by acl_users)
2. string: public_email
2. internal_info
1. string: name (as provided by acl_users)
2. string: company
3. string: internal_email
4. string: fields_of_interest
5. string: fields_of_expertise
6. string: statement_of_involvement
The DocumentFolder is what is called a Document in the
Problem description. Inside a DocumentFolder, there can
be some ZClasses or normal Zope Documents, XML Documents
and so on.
DocumentFolder ZClass
When a writer wants people to read his Drafts, but does not yet
want any comments, he just puts a Reader ZClass inside his
Document.
Reader ZClass
- Boolean NeedsReaders
This changes the access rights so that members and Visitors can
see the Document.
Inside the DocumentFolder ZClass, the Maintainer can place some
services. If the Maintainer needs some comments on his Draft,
then
he places a Comments ZClass inside the Draft Folder.
Comments ZClass
- Boolean NeedsComments
The Maintainer can also place a Writers ZClass inside his
Draft.
Writers ZClass
- Boolean NeedsWriters
The Mainainer can place a History ZClass inside the Draft
- Writers, Editors and Approvers jot down what they
have done on the Draft
The writer of a Draft can place an Editor ZClass inside his
Document.
Editor ZClass
- Boolean NeedsEditor
- String CurrentEditor
When the NeedsEditor Property of the Editor ZClass is
automatically
activated, and the Draft folder becomes automatically
accessible
for Members with the Role of an Editor.
When an Editor wants to work on the Draft, he just signs in.
- The NeedsEditor Property of the Editor ZClass is
deactivated.
- The Editor's name is noted in the CurrentEditor Property
- The Editor starts working on the Draft inside the users
Draft folder.
When an Editor has edited the Draft, he can call for an
Approver
by a similar process.
Approver ZClass
- Boolean NeedsApprover
- String CurrentApprover
Writers are Maintainers of a Document which they have written.
A Maintainer can call for a new Maintainer by placing a
Maintainer
ZClass inside his Document.
Maintainer ZClass
- Boolean NeedsMaintainer
The NeedsMaintainer Property of the Maintainer ZClass is
activated
The Draft folder becomes automatically accessible for Members
A Member can copy the complete Document folder over to his home
directory. The Member signs in for taking responsibility for
the
Document.
- The NeedsMaintainer Property of the Maintainer ZClass is
deactivated
- The NeedsReader Property of the NeedsReader ZClass is
deactivated