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

[Helge Hess]

On Nov 27, 2006, at 18:00, Adam Tauno Williams wrote:
> I have three jounal/BLOG-esque applications:
>
> 1.) For CRM we record a contact journal for a contact and/or  
> enterprise.
> Currently we store this in a separate database,  which works but is
> messy and make writing consumers irritating (get this here, get that
> there, etc...).  We store the OGo Id in the external database and the
> application has to jump back and forth.
>
> For this case it is pretty simple: {Date}, {Object Id}, {Comment},
> {Commentor}, & {Type}.  Type relates closely to something like
> appointment type: meeting, call, etc...

Why don't you use a project, that is the notes of a project, for that?
Just because it a note has no type?
Because you can't enter the date of a note?

> In retrospect I could store
> this in the schedular since I think I can retrieve all the 'events'  
> for
> a contact or enterprise in a given date range.  For some idiotic  
> reason
> I didn't think you could create an appointment with no account
> participants;  so this one is really a brain-fart on my part.  I can't
> see any reason why that wouldn't work.  By only question would be  
> how to
> properly store events that only have a date and no time;  as all day
> events?

I wouldn't store that in the scheduler.


> 2. A work journal.
>
> This is for lawyer and engineering types.  This seems like it would be
> related to a project,  but the end-user really looks at it as a  
> journal.
> So some way to query and present a view of all entries by a particular
> user is needed,  which may traverse multiple "projects"  (at least how
> the end-user is thinking of the concept of "project").  This is the  
> one
> that seems really arbitrary - and they REALLY want it a certain way
> [ lawyers and engineers... if you haven't had the pleasure... :) ]

I can't follow that completely. Isn't that tasks? Attached to  
projects and also shows up in an overview.


> 3. The normal ability to BLOG/Journal on an actual project.  Has the
> same question as #2 but the 'where' is pretty obvious.

Well we already have that with project notes?


>> Most objects in OGo already do have a "journal" (tasks, appointments,
>> projects). I suspect whats actually needed is some kind of
>> "reporting" frontend here? Possibly just an RSS feed which cumulates
>> the "notes" of the individual object types?
> I agree,  at least on Tasks.  Otherwise they only 'sort of' have a
> journal;  notes could work but I think the functionality would need  
> some
> tweaking.

I was referring to notes. What is missing?

Greets,
   Helge
-- 
Helge Hess
http://docs.opengroupware.org/Members/helge/