Great Video! Using in-line reference is very important, if you rename a tag or field. Fully agreed! I have a similar approach for the documentation. I document my changes in the daily note and tag them as tana_config. Additionally I have tana_sop tag for writing down my own rules in using tana. Last I have a supertag tana_roadmap which I assign to ideas in may daily notes. I collect all of them by searches in my central Tana node.
I mean you can keep them within Schema too and just ref them, but that has one drawback that I didn't cover in the video: if you want to copy a system from one workspace to the next, it's much easier if you have the supertag systems in one place.
@@cortexfuturatools But what if there's overlap between systems. Like if I have one system for task managemement and another for work log. Both might need the supertag "project", but it can't live in both systems. Any problem with that?
Great video, thanks for making these. Wondering why you populated the "Status (cf_oss)" field pre-determined options manually instead of from a source node (~4:11 in the vid)?
Hi Lukas. Super helpful, this organizing of supertag systems. I am having trouble bringing up the "bring reference nodes here" command. Any tips on where I might be going wrong?
Great framework for organizing tags! I'm struggling to conceptualize how it would work for my supertags. I have a multi-layered task management system with the following hierarchy: Area > Project > Task > Step. Each level is its own supertag; I attach each node with the todo supertag to the lowest required level (sometimes a todo just belongs to an Area, for example). Most of my fields are unique to each supertag. What approach would you recommend? An "area management" system supertag, with all supertags and fields from all levels? Separate systems for each level? Or something else?
Thanks! Learnt something again (the 'bring' command). Had not thought of describing my tag system this way, good idea! I prefer to have the original tag in the schema and reference it in the supertag system, but that's personal preference. Keep 'em coming!
For anyone wondering why Lukas decided to bring the tag references from the schema (like I was), check out the thread started by Alexander Schwarz below.
This would definitely help protect against accidentally deleting fields that you want to re-use. That was a problem when I first started.
Really like the structure and cleanliness of this approach. Could it also be extended to include fields? Tana suggests holding them in the Schema
Great Video! Using in-line reference is very important, if you rename a tag or field. Fully agreed! I have a similar approach for the documentation. I document my changes in the daily note and tag them as tana_config. Additionally I have tana_sop tag for writing down my own rules in using tana. Last I have a supertag tana_roadmap which I assign to ideas in may daily notes. I collect all of them by searches in my central Tana node.
I don't have semantic function under "Tana Labs". what should I do?
So the idea is that you don't want hundreds of supertags within schema but cluster them into systems for better overview?
I mean you can keep them within Schema too and just ref them, but that has one drawback that I didn't cover in the video: if you want to copy a system from one workspace to the next, it's much easier if you have the supertag systems in one place.
@@cortexfuturatools But what if there's overlap between systems. Like if I have one system for task managemement and another for work log. Both might need the supertag "project", but it can't live in both systems. Any problem with that?
Great video, thanks for making these. Wondering why you populated the "Status (cf_oss)" field pre-determined options manually instead of from a source node (~4:11 in the vid)?
Around the 2:33 mark, can you say why you didnt want the tags to live in schema please?
Hi Lukas. Super helpful, this organizing of supertag systems. I am having trouble bringing up the "bring reference nodes here" command. Any tips on where I might be going wrong?
Great framework for organizing tags! I'm struggling to conceptualize how it would work for my supertags. I have a multi-layered task management system with the following hierarchy: Area > Project > Task > Step. Each level is its own supertag; I attach each node with the todo supertag to the lowest required level (sometimes a todo just belongs to an Area, for example). Most of my fields are unique to each supertag. What approach would you recommend? An "area management" system supertag, with all supertags and fields from all levels? Separate systems for each level? Or something else?
Thanks! Learnt something again (the 'bring' command). Had not thought of describing my tag system this way, good idea! I prefer to have the original tag in the schema and reference it in the supertag system, but that's personal preference. Keep 'em coming!
Yes, that's of course totally fine!
For anyone wondering why Lukas decided to bring the tag references from the schema (like I was), check out the thread started by Alexander Schwarz below.
Any ideas on how to get an invite. I've been waitlisting for 3 months.
enroll cortexfutura MTC course. it include an invite
awesome idea, Lukas! I think I know what to do in the TPL :)
Haha, obviously the TPL was the root from which this flower sprang! :)
Try to say "inside Tana" quickly, sounds like a Japanese name 🎌
MegaTags...
Too fast for a new Tana user to follow. Frustrating.