Re: ogo task reminder

[email protected] wrote: 
> > > >> - notification time column in the job table (as compared to the 
date x 
> > > >> table for appointments
> > > > Any schema changes are going to need the blessing of the PTBs; makes
> > > > upgrading/updating, packaging, etc... more complicated.
> > > I know, and I thought about that, but I decided, just for consistency, 
it 
> > > would make sense to copy the logic how things work from appointment, 
would 
> > I agree that this is the ideal solution (at least IMO)
> > > be the better idea. As there were no extendedJobAttributes... which I 
could 
> > > have used, as I started. At least I was not aware of the patch in 
bugzilla.
> > I just wonder if, for the sake of getting something sooner, if a simpler
> > solution wouldn't work. 
> > In my understanding tasks have a due *DATE* and not a start *TIME* like
> > an appointment.  Would it be sufficient to simply store a "reminder"
> > property on the task, and to process the tasks for the day?  Early in
> > the day an e-mail could be sent to user(s) concerning what tasks they
> > have due in DAY + 1 (Mon - Thu) or TODAY + 3 (Fri).
> > Or make the property an int, number of days 1, 2, 3, or 4.  Then you'd
> > only need to scan the tasks due in the next 4 days - even at large sites
> > that shouldn't be more than a few hundred.
> > In the morning the user could have an e-mail "Your due tasks" or some
> > such.
> > I do something like this with SQL, but with no OGo/WebUI integration,
> > you just get the message for all your tasks.  Just making that optional
> > would be a huge improvement.
> 
> FYI, the query I use is:
> WHERE "job status" NOT IN  ( '25 done', '30 archived', '02 rejected' ) 
> AND is control job IS NULL 
> AND start date <  'tomorrow'
> AND end date < 'tomorrow'::DATE + INTERVAL '4 days'

adding the 02_rejected makes sense to me, but I do not know what the 
control_job is for?

Sebastian

-- 
OpenGroupware.org Discussion [email protected]
http://mail.opengroupware.org/mailman/listinfo/discuss