Re: [Tsheetx-developers] Feedback on branches/txsheet-2.0-demo

[paul c. <pdc...@bl...>]

One of the uses I have for  timesheet  is logging on call call-outs . 
Functionally ,  the time period from 5pm to 9am the next morning is 
considered as one ' night on call '  and a night 'on call' includes from 
5pm to 9am the next morning, So  if times were automatically split at 
midnight, id just put them back together again . The additional  
complication for me is that a different rate is paid between 7pm and 7am 
. Is an alterntive to store the timezone with the user config ?. If a 
user moves timezone then the 'clone user ' can  create a duplicate , and 
then its just a matter of  identifiying the users by TZ  ( eg PC(GMT) 
and PC(CET) )

I think its worth keeping start/end times and duration in the DB. It 
keeps things flexible for the future , at very little overhead and it 
would  make putting times  back together easy for me  ( ie Id just use 
start time  and duration) .

On 16/11/10 07:13, David Thompson wrote:
> Peter, today there are actually no reports that show any start or end 
> times at all, only durations are shown. That said, an attendance 
> report has been requested more than once.
>
> Scott, my aim with adding durations was to make the DB queries easier, 
> not harder. But you are right about the problem of date boundaries, I 
> think in the original project this was seen as a super feature - but 
> this does make all the querying harder.
>
> So I guess we need to start by clean data entry, for example 
> converting to UTC, and splitting tasks entered when they cross a (UTC) 
> date boundary. And the user profile then needs to hold his timezone.
>
> But, as an idea, we could also record the local timezone/DST every 
> time a time is entered. It might be useful for reporting later, in 
> particular when a user changes timezone. Bad idea? Good idea? Waste of 
> time?
>
> Dave
>