[geeklog-devel] Multi-Hierarchy Category Maintainance Plugin Idea (was Re: Geeklog Document structure)

[Heather Engineering]

I suggested this kind of thing late last year as "gNode" to Tom  
(WebSiteMaster), and actually started on it, but this code is too  
outdated and not working right now. Also, I have another plugin for a  
(hopefully) large project with a major archive (name is off-record  
pending approval) that I'm hoping to get going soonish, called  
"Documents", which is a hierarchical manager for academic primary  
documents.

To get to the point, if anyone wants a tarball, it's still a bit of a  
mess as I'm juggling too many things at the moment, but the basic  
hierarchical stuff from "Documents" might be of use to someone.  
Contact me with your email for a tarball. It's my first OO plugin, so  
don't laugh at the (surely many) obvious mistakes. :-) There is a  
base "Node" class, which is extended by different types for each  
level of the tree.

Alternatively, the stuff from Links should also be a useful starting  
point. And you're welcome to the "gNode" name if anyone wants it. (I  
went through a dromedarian phase.)

Even more off topic than usual: if there are developers interested in  
co-operating on the development of Documents, please let me know. In  
particular, I have been told by a professional DB researcher that I  
should be using XML for the DB, as records will easily enter the  
millions of entries and much data is optional/irregular at each  
level, so if there is anyone experienced in XML databases interested  
in this, please let me know. It is a major archive so could turn into  
an interesting project if I can organise financing or hardware/ 
bandwidth sponsorship.

Cheers,

Euan.


On 2007/09/27, at 4:44, Joe Mucchiello wrote:

> Thinking further, as a plugin, this really doesn't need core  
> support. If you turn off the standard topics menu, you can plugin  
> your own categorization menu. The trick is creating a fake  
> "article" plugin to handle categorization of stories. I'm going to  
> write the calendar category code as a separate plugin (initially  
> supporting one hierarchy, obviously) and then I can expand it into  
> something like static pages later. Once it's running perhaps  
> they'll think about pulling it into core and using it for stories/ 
> topics and the links plugin at a later date.
>
> Daz, I'll post something to calendar dev site to see if anyone  
> there is opposed to hierarchical event categories.
>
> I left out a couple features:
> * Option to create tables specific to each object (or certain  
> objects) for speed considerations.
> * Option to add field to the object's table when only one hierarchy  
> is attached to it. (Again, for speed considerations)
>
>   Joe
>
> At 02:06 PM 9/26/2007, Gary Moncrieff wrote:
>> Joe, please do this I very much have a use for it at the moment,  
>> I'm setting up Geeklog as a repository for our course materials  
>> (sick of emailing stuff to students basically) and a hierarchical  
>> topic section would be perfect for help notes etc
>>
>> Regards
>>
>> Dazzy
>
> ----
> Joe Mucchiello
> Throwing Dice Games
> http://www.throwingdice.com
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://eight.pairlist.net/mailman/listinfo/geeklog-devel