[Zope] ZClasses design questions

[Kevin Dangoor]

-----Original Message-----
From: Tom Schwaller <Tom.Schwaller@linux-magazin.de>
To: zope@zope.org <zope@zope.org>
Date: Sunday, September 19, 1999 7:46 AM
Subject: [Zope] ZClasses design questions


>Here is one of my general design questions for zclasses:
>
>I will have an folderish "author" class and a special
>"article" class. To organize the workflow I prefer
>to have the articles of one author in his "folder",
>but once finished with them, I prefer to have them in
>a "issue" folder with the article connected to the author
>(How?? Several authors are possible (where to put the articles?)
>Collecting the  articles from all the authors each time I want
>to see the content of one issue gives no sense, this is
>fixed after pubblishing and will not change and I want
>something like /issue/1999/10/Zope and not /author/Zope
>in the overview for the links. Generating it once is
>the best solution in that case I suppose..).

Particularly now that ZCatalog exists, the exact layout of the hierarchy is
not as crucial. To ensure that security works as you need, you'll want to
make sure that your acquisition path results in the correct security
settings.

Here are some options:

Have the articles get added to a "submissions" Folder. Maybe you could use
the Owner role to allow the authors to continue editing the articles until
an editor has gotten around to moving theirs into the "issue" Folder. If you
want a view that shows all articles by a given author, just use ZCatalog to
list that author's articles (regardless of which issue they are located in).
So, you can still maintain and author view, while your article URLs are
stable.

In KM|Net News, the URLs of the articles don't change at all through the
process. Only the status changes...

ZCatalog, and the upcoming "Topics" objects, do a lot to allow for arbitrary
object organization.

Kevin