Atomic Creation in Tana: A Smart Note-Taking System
Vložit
- čas přidán 27. 02. 2023
- In this video, I introduce you to a new Zettelkasten system called SN(A)CK, which unifies sources, notes, creations, and knowledge in one seamless setup.
I'll show you step-by-step how to use atomic creation in Tana to streamline your note-taking and personal knowledge management. With SN(A)CK and Tana, you'll have a powerful and effective zettelkasten that focuses on creative output.
Tana Templates Library: help.tana.inc/tana-templates-...
My SN(A)CK System Template: help.tana.inc/snack-system-at...
Love your video from China. I copied so much zettelkasten templates from everywhere but eventually failed to implement to my practice. Looks your design is an intuitive one.
That’s awesome to hear😊
Great work mate! Really intuitive system build. Great to see a fellow Tana enthusiast diving into CZcams content creation. Keep up the good work 💪
Thanks, Sam!! Awesome to hear! Tanarians stick together😁
This was remarkably presented and implemented. It gave me a lot of inspiration for my system and I learned a lot of neat tricks by watching your workflow. Looking forward to future updates from you. All the best.
Excellent format, Theo! You rocked it 👊🏻
Glad you liked it, DDV!!🤩
Awesome video, Theo ... I loved the way you did this.
Thanks, David! Means a lot!
This is excellent, Theo, thank you for sharing!
Nice work!🎉
Appreciate it, Maciej!
very helpful！
Glad it was helpful, Leslie😊
Tasty!
Hi Theo! Thanks for this handy template. I'm curious about the question - what's the point of moving nodes to the library?
Hey Artem! Awesome to hear you find it handy, and really good question. Should have made it more clear why in the video! The reason is that the Related Knowledge field has "Auto-initialize to parent with this field" turned on, and hence, when you tag a new topic within the Related Knowledge field, that new topic gets a reference to itself (and the other topics in the field) in *its own* Related Knowledge field. It is a quirk that didn’t have a simple solution.
That said, there is no reason for sending it to the Library in particular. As long as the node you are tagging doesn’t live in the Related Knowledge field you’ll get around the quirk. So sending it to the day page for example works equally well. And there is no real harm done if you don’t send it anywhere, just that it gets related to itself which might not be what you want😊
Hope that clarifies! Sorry for the delayed response.
@@tanarian thank you for clarification!
Hi, Theo. At about 3:00 in your video you add Publisher as an instance tag of a Publisher supertag. Did you have to create this supertag? If so, where does it live?
Hey, Will :) That’s a supertag I had created beforehand. It’s not part of the SN(A)CK template. Used it as an example of how you could add (instance) fields to the template as needed. I keep all my supertags living in the Schema.
I created some fleeting notes with your fleeting notes tag but they are not populating in the dashboard. Did I miss any steps? Moreover ,the book super tag is not populating the title of the book in the Source dash board. Could you create step by step video to ensure everything works?
This shouldn’t be a problem… Sent you a DM in Slack so we can take a closer look there😊
@@tanarian Thanks a lot for taking the time to help me and clearing my confusion. Great Help!
Could you let me know if you produced any actual output from this system? Something like an article or a book?
Hey Valery! The video itself was ideated and scripted with the help of SN(A)CK :) I also recently posted my first article that was drafted several times over with the help of my notes and thoughts in SN(A)CK. I also have several unreleased outlines and drafts that might be shared in the future. You can check out the article here if you’d like: www.collider.space/issue-3-harnessing-the-power-of-curiosity/ 😊
No book yet😄 But I’m definitely building a good base for it😁
@@tanarian Thanks, I’ll check it out. I was wondering if your process works end-to-end.
and how you think the differences between atomic note and permanente note ?
Interesting question!! I think they have some common attributes, but quite different focus. These are some of my thoughts:
Both permanent and atomic notes contain stand-alone ideas that are permanently understandable.
I think the Permanent note focuses too much on the physical attributes of a note. In a digital system it is less relevant if a note will be thrown away (deleted) or not.
I tend to think of all notes in SN(A)CK as permanent, but not static… they can evolve, grow and be combined (into synthesis notes).
I think the attributes of an Atomic note is way more valuable and coherent with Tana’s "granular" node structure. One node contains one atomic note. It can be surfaced and reused wherever you want. They should be brief and contain only one single idea. If there are two ideas, it’s a synthesis note based on two atomic notes.
Atomic notes can be used directly in your content. They are written in your own words and you can find the source and highlight that inspired them. They are created because you think they are interesting. Don’t be too strict with your atomic notes.
If you think something is interesting, try your best to break it down into a singular idea using your own words, relate it to knowledge, and think about + explore how it may link to existing atomic notes in your SN(A)CK system.
Hope that was clear! Thanks again for the question, Leslie☺️
@@tanarian Thank you! for your answer.it is very clear .and my views is basicly same to you.
the permanent note come from the old Zettelkasten system as you said, it focus on the physical attributes of a note ,for it is from a card note . but in digital system, i more care about a note’ valuable and refuse for creation which will become my own knowledge, and further i can share it to others. that is my final purpose for note-taking, and knowledge managament.
so i think you system based on atomic note is very suitable for me ,and it have the same Philosophy from the book 《atomic habit》。
I have used the system for several days ,here is my some thoughts about the system：
1、For note tag : i see atomic note and systhesis note as permanent note. they should be saved for refuse. of cause the knowledge note ，but for fleeting note ,i see it as Temporary notes， i will review and changed it to an atomic note , and keep it clean daily. it is Thought Buffers zone。
2、for atomic note ,in setting，i want to add a related source field，and the source tag added a related note field ，How you think about?
because when i indent a atomic note ,i want to see which sources it referenced to . the same from a source type note .not only related to knowledge note。
I think the source
ote\and knowledge ,they are connect each others, but maybe the system became more complicated in the end .
thanks again！looking forward a more deep thoughts connetionts about Tana and the note-taking system。
Theo Køppen☺
Excellent video and super effective and efficient system. Very well done
Thanks for help along the way, Dee☺️
I feel like it’s a bit too much work and it can feel overwhelming quick
Hey! I totally get you. That is the biggest problem with PKM for me, and it’s the issue I’m most concerned with solving. It’s about making the benefits larger than the costs.
I recently wrote an article about curiosity in PKM that could spark some ideas about how to make your PKM practice feel less like work😊 Feel free to check it out here: www.collider.space/issue-3-harnessing-the-power-of-curiosity/
Awesome comment, thanks!☺️ (sorry for very late reply)
Please Don't be so close to the camera