| id: | 15 |
| title: | Nested tasks |
| priority: | 1 |
| status: | active |
| created: | 2008-05-25 17:08:59 |
| resolved: | 0000-00-00 00:00:00 |
The single-level task list set up using DataWiki is quite convenient, but at the moment the only structure I can set up is by defining a new domain (i.e. project) and putting everything into a directory for that domain.
It would be nice to be able to provide subtasks for a given task. From a formatting standpoint, this should work OK -- the single-record retrieval and list retrieval features can coexist in a single page. But I'm not sure how to set that kind of format up automatically, so that a page would gain a subtask list as soon as there were subtasks to be displayed.
Note also that closure of all subtasks could be specified to close the parent -- that would be a rudimentary form of workflow, so that we'd be coming back around to the wftk in this effort as well. Probably a foregone conclusion, ha.
Actually, this can be seen as a subset of nested data in general. I did some preliminary work on this for keywords in the Wiki index, so perhaps I can generalize it a little. Probably can, actually. Hmm...