The immediate problem is keeping track of my own t...
# chat
m
The immediate problem is keeping track of my own tasks within and across the tools everyone else is using. Ideally, I'd like something that aggregates the tasks from all the different platforms into a range of views. A complete top-down overview, a "next task by project", mapping out dependencies, that kind of thing. And to be able to easily jump to the other tool if I need to do more involved stuff, and to automate/script things like well-known tasks, project structures, etc... But the really important part of this for me is maintaining links between the local interface and the remote service, as the costs of manual sync become rapidly untenable. All of the other features I've described are in extant products, but this last bit doesn't seem to be.
k
yeah, standardization is not a thing. did consulting in a past life and can definitely emphasize with this issue. the way i manage this is to keep a separate copy of all tasks inside of dendron. when i make a update to tasks, i'll do it in dendron first and then c/p it into whatever downstream task management solutino is there. something that can make this workflow more ergonomic is using proxy notes for commonly used uris. see https://github.com/dendronhq/handbook/blob/main/notes/ext.md#L8:L8
m
That's a really helpful pattern, thank you. Will look at writing some stuff to automatically grab some relevant items. This approach feels like a more organised, tidier version of the resource links in Microsoft Graph - https://docs.microsoft.com/en-us/graph/api/resources/linkedresource?view=graph-rest-1.0
To make this work in the longer run, I think we're going to need to establish what the SOLID project calls "vocabularies" (by which it means semi-formal ontologies), to be able to link up across services. It feels to me like Dendron could be an interesting tool to surface that kind of functionality in interesting ways.
3 Views