[Zope] one 'document' in many 'folders'

[Wade Leftwich]

What a great mailing list! I posted my question, shovelled the 
driveway (Ithaca NY, 8" of heavy wet snow last night), had 
breakfast and an extra cup of coffee, then came back to my desk 
to find 2 good answers. Thanks Stefan and Kevin.

Well, on the one hand I'm pleased to hear that my question wasn't 
trivial. But I'm disappointed to hear that my problem is difficult.

I'm competing against Cold Fusion here, and the problem resolves 
itself pretty easily with linked tables. (At least until I actually try to 
write the code.) So maybe I should just co-opt the competition and 
use ZSQL? But the odb is so nice, I really want to make it work 
that way.

I don't really need for the URLs to look like a directory structure:
instead of /open_source/zopeiscool, it would be okay for the article 
URL to be /zopeiscool?section=open_source. But that still leaves 
the problem of generating a contents page for each section. I 
suppose I could have a script that periodically-or-on-demand walks 
through the articles and generates a fresh static contents page for 
each section. Seems kind of non-zopish, but that might be the 
best way to get decent rendering performance on the contents 
page anyway. (The site is very active.)

>an acyclic directed graph structure in the object hierarchy itself

Yow!

The original question:

> > -----Ursprüngliche Nachricht-----
> > Von:	Wade Leftwich [SMTP:wade@lightlink.com]
> > Gesendet am:	Montag, 22. März 1999 13:44
> > An:	zope@zope.org
> > Betreff:	[Zope] one 'document' in many 'folders'
> > 
> > As a demonstration project to try and get a client to go with Zope, I'm
> > converting a newsfeed database that I had originally built using Perl.
> > 
> > The object of the game is to pull fresh articles from a Reuters 
> > server every two hours and put them in a bin. A human editor goes 
> > through the bin, culls and sorts the articles, edits where 
> > appropriate.
> > 
> > One article may appear in more than one section of the site. For 
> > example, an article titled "Zope Is Cool" might appear in the 
> > Python, Web Development, and Open Source sections. Each 
> > section has its own contents page.
> > 
> > This is where I get confused. My Perl application simply used the 
> > filesystem as a database, and generated three separate static 
> > copies of "Zope Is Cool", placing one in each of  three directories:
> > /python, /web_development, and /open_source. I suspect there are much
> > better ways to do it in Zope, but how do I organize things?
> > 
> > My naive idea is to make each article a Document, one of whose 
> > properties is a list (or dictionary) of categories in which it should be
> > placed. Generating each section's contents page would then take some
> > figuring out, and performance on doing the contents page would be a
> > concern.
> > 
> > If there's a better way, I'd certainly appreciate hearing about it.
> > 
> > Signed,
> > 
> > Confused a/k/a
> > 
> > 
> > 
> > 
> > 
> > Wade Leftwich
> > Okay Network Services, Ithaca NY
> > tel 607-277-1334  fax 607-272-3612
> > 
> > _______________________________________________
> > Zope maillist  -  Zope@zope.org
> > http://www.zope.org/mailman/listinfo/zope
> > 
> > (For developer-specific issues, use the companion list,
> > zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
>