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

[Stefan Franke]

Correct me if I'm wrong, but the only way I see to do this *inside*
the Zope application is to keep all your articles inside one folder
(pool) and have key documents in your tree structure which 
reference an article in the pool.

I don't know if problems appear when you establish an acyclic
directed graph structure in the object hierarchy itself (I asked
the question myself months ago without an answer).
I see no point why it shouldn't work, but it is not maintained 
by the application.

An interesting fact is that your object's properties vary when
accessed by different paths due to the acquisition structure.
An object inside Zope's database (again, correct me, if...)
doesn't know about its father. It only knows about its sons,
the aq_parent path is constructed on each access.

Would also like to hear more about this...
Stefan

> -----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 )