[OGo-Discuss] BLOGing/Journaling/ACTing [Was: OGo and asterisk, SUMMARY]

[Adam Tauno Williams]

> >> I think it is very important to keep things general-purpose;  if
> >> people need very specific functionality OGo provides to means for
> >> users to construct front-ends to the general purpose functionality  
> >> via
> >> an intranet or other means.
> > Btw, blogs are not really that bad when properly used assuming that  
> > the editor
> > has received a basic level of <snicker> training?
> Yes, and IMHO this wasn't Adam's point. I think his point is that a  
> blogging application would be written as a separate app on top of the  
> OGo infrastructure. Eg a blog could be easily build on top of an OGo  
> project.
> Which in fact is something I very much consider. Its more or less my  
> idea for the future of OGo, producing more focused interfaces on top  
> of the OGo infrastructure.
> Aka the "groupware construction kit" ;-)

Agree;  but I'm curious as to your thoughts concerning how to store the
content of something like a journal/blog.

1.) Store the entire BLOG as a document;  simple but seems hard to edit.

2.) Store the BLOG as a "folder" in a project, each file in the folder
being presented as an "article" or "entry".  Also simple but hard to
sort and/or search.

[ FYI to readers: 
    CREATE TABLE note () INHERITS(document); 
    CREATE TABLE doc ()  INHERITS(document); ]

3.) Store the BLOG in notes.  Each note being an article or entry.
Notes provide title, author, modification and creation time.  There is a
"file_type" attribute;  if this is other than "txt" does the note still
appear in the WebUI?  Sort of,  if the file type is something like "xml"
or "fred" (just to test something completely bogus) then the
title/author/time-stamp appear in the WebUI but the content is not
rendered;  one can still click the edit button and is presented with an
edit page where the content is blank. 

I suppose this is really the same as #2 since notes are documents;  I
would have thought that setting is_note = 0 would make something not
show up as a note, but it still does.  [ And here I was thinking I was
starting to get what was going on -  the parent_document_id of the note
is 12760 which is the root folder of the project  ( is_folder = 1 &
parent_document_id IS NULL ) but setting is_note = 0 doesn't make it
show up as a document even though it is in the document table ]