Databases
StackOverflow2013
Postsdbo
POTimetable grouped by tag
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POTimetable grouped by tag
    primarykey
    data
    text
    <p>I'm looking for a way to use time tracking information from org-mode agenda files to build a timetable. Time spent in different tasks would be indicated, grouped by tag and restricted to a given time-frame, sort of like a clocktable dynamic block, but grouped by tag instead of file/category/headline.</p> <p>For example, if my agenda contained the following data (possibly scattered among different files):</p> <pre><code>* TODO project 1 ** TODO task 1 :tag1: :LOGBOOK: CLOCK: [2013-06-27 Thu 18:00]--[2013-06-27 Thu 19:04] =&gt; 1:04 CLOCK: [2013-06-26 Wed 17:00]--[2013-06-26 Wed 17:32] =&gt; 0:32 :END: ** TODO task 2 :tag2: :LOGBOOK: CLOCK: [2013-06-27 Thu 17:00]--[2013-06-27 Thu 18:00] =&gt; 1:00 CLOCK: [2013-06-27 Thu 15:00]--[2013-06-27 Thu 15:50] =&gt; 0:50 :END: * TODO project 2 :tag2: :LOGBOOK: CLOCK: [2013-06-27 Thu 19:04]--[2013-06-27 Thu 21:00] =&gt; 1:56 CLOCK: [2013-06-27 Thu 15:50]--[2013-06-27 Thu 17:00] =&gt; 1:10 :END: </code></pre> <p>I would like to get this kind of results:</p> <pre><code>#+BEGIN: clocktable-by-tag :maxlevel 2 :tags ("p1" "p2") :tstart "2013-06-27" :tend "2013-06-28" | Tag | Headline | Time | | |------+-----------------+--------+------| | tag1 | *Tag time* | *1:04* | | | | TODO project 1 | 1:04 | | | | \__ TODO task 1 | | 1:04 | |------+-----------------+--------+------| | tag2 | *Tag time* | *4:56* | | | | TODO project 1 | 1:50 | | | | \__ TODO task 2 | | 1:50 | | | TODO project 2 | 3:06 | | #+END: </code></pre> <p>Is there any standard way to do this with org? If not, I'm thinking of cycling through agenda files and tags, using <code>org-get-table-data</code> to collect clocking information; would there be another, more efficient way of doing things?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USFrancesco
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POTimetable grouped by tag
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POTimetable grouped by tag
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POTimetable grouped by tag
      1. USRubyTuesdayDONO
      1. VTFavorite
    1. COI don't know if there is a way to do it, but would be interested to find out, too.
      singulars
      1. POTimetable grouped by tag
      1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload