From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aankhen Subject: Timesheet from clocking data Date: Fri, 22 Apr 2011 01:33:48 +0530 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:48135) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QD06p-0000AC-Tp for emacs-orgmode@gnu.org; Thu, 21 Apr 2011 16:04:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QD06p-00029w-1M for emacs-orgmode@gnu.org; Thu, 21 Apr 2011 16:04:15 -0400 Received: from mail-vx0-f169.google.com ([209.85.220.169]:52793) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QD06o-00029m-Qc for emacs-orgmode@gnu.org; Thu, 21 Apr 2011 16:04:14 -0400 Received: by vxk20 with SMTP id 20so82354vxk.0 for ; Thu, 21 Apr 2011 13:04:14 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Org mailing list Greetings, Given an Org file with clocking data, is there a way to generate a timesheet? This would complement the clock table by focusing on the timings rather than the headings. As I haven=E2=80=99t come across anything like this as yet, I=E2=80=99ll tr= y to give an example (manually-created) to show what I mean, in case someone more familiar with Org can tell me something about it: ,----[ Org tree ] | * Foo | :CLOCK: | CLOCK: [2011-04-19 Tue 18:50]--[2011-04-19 Tue 20:30] =3D> 1:40 | CLOCK: [2011-04-18 Mon 20:15]--[2011-04-18 Mon 21:00] =3D> 0:45 | CLOCK: [2011-04-21 Thu 01:03]--[2011-04-21 Thu 02:03] =3D> 1:00 | :END: | CLOCK: [2011-04-19 Tue 12:30]--[2011-04-19 Tue 18:06] =3D> 5:36 | | | *** Bar | :CLOCK: | CLOCK: [2011-04-19 Tue 18:06]--[2011-04-19 Tue 18:50] =3D> 0:44 | CLOCK: [2011-04-22 Fri 01:00]--[2011-04-22 Fri 01:05] =3D> 0:05 | :END: | | *** Baz | :CLOCK: | CLOCK: [2011-04-21 Thu 03:10]--[2011-04-21 Thu 04:00] =3D> 0:50 | :END: `---- (Please ignore the very strange timings. I just threw together whatever I could for the sake of the example. :-) The table: #+BEGIN: timesheet :group day :scope subtree :block thisweek Timesheet | Entry | Time | | |------------------+---------+-------| | *2011-40-18 Mon* | *00:45* | | | 20:15=E2=80=9321:00 | | 00:45 | | *2011-04-19 Tue* | *08:00* | | | 12:30=E2=80=9320:30 | | 08:00 | | *2011-04-21 Thu* | *01:50* | | | 01:03=E2=80=9302:03 | | 01:00 | | 03:10=E2=80=9304:00 | | 00:50 | | *2011-04-22 Fri* | *01:00* | | | 01:00=E2=80=9301:05 | | 01:05 | |------------------+---------+-------| | Total | 11:35 | | #+END: As you can see, each day with any time clocked gets one entry in the table. Underneath that entry are all the non-contiguous blocks of time clocked in during that day. Clocked times from subtrees are summed up and subsumed by their parents, so in the example given, there is one single contiguous block from 12:30 to 20:30 on Tuesday, whereas there are two entries for the non-contiguous blocks on Thursday. I really have no idea where to begin in order to obtain this sort of report, if it is even possible. Any pointers would be most appreciated! Thanks, Aankhen