Envisioned use cases

Using taskopen as metadata storage for documents

Most of the times, I use taskopen/taskwarrior to group documents and make them easily accessible. A task could be a long-term pet project, a reading list, or a repetitive chore (e.g. backup checklist). In all these cases, a taskwarrior task stores meta information and state for a collection of documents/links/etc. Taskopen could be used to achieve a better organisation of documents by adding a meta data layer that allows filtering by contexts and other taskwarrior concepts. This use case would benefit from the following features:

• find task for a given file
• archive documents (must respect other references to the same document)
• moving/copying annotations to another task

A task referencing a given file can be found by using taskwarrior's filter functionality to search in annotations, e.g.:

task /path.to.file.ext/

Note, that using . instead of / resolves the problem of escaping the latter. Instead, the search term is interpreted as a regular expression. Yet, there is a little bit of ambiguity left. This might be solved by a new parser implementation in taskwarrior, though.

Archiving is achievable by an external script that checks whether the file is referenced by any other active task, moves the file and modifies the annotation correspondingly.

Moving/copying annotations is also achieved by an external script. The only challenge with this is how the ID of the target task is passed to the script. A viable and simple option is the addition of a --args option in order to fill an environment variable that can be referenced in the command.

Kanban workflow with taskopen and taskwarrior (taskban/kanwarrior)

t.b.d.

Workflow: from an idea to a kanban board

t.b.d.

Workflow: short-term scheduling

t.b.d.

Required features

t.b.d.