Thanks for sharing, @talazem. Best Zkn template I have come across so far.
P.s.: Just a minor correction. Zettelkastens should actually read Zettelkästen.
1 Like
Glad you’ve both found it useful.
p.s. You’re right, of course, Bernardo. But what with ‘zettelkasten’ becoming a household term (in an infintesmially small number of houses), one might be forgiven for slapping an ‘s’ to make the plural, as one does for all good foreign words that have entered the lingua franca of the internet. 
2 Likes
@talazem
Hi,
I have been using TBX for visual organization, and now I want to try the combination of Tinderbox and Zettelkastens. One year has passed. Has this template been improved and optimized?
Hello @Ting. I haven’t done any further work on the template, myself. It was more a template to inspire or help others learn how to use TBX for this purpose. I hope it remains helpful in that fashion. I think the additions of v9 do make this template even moreso for Zettelkasten-style note-taking.
1 Like
Very nice template, no friction with Zettelkasten.
@talazem
Excuse me again, I have roughly understood the operating principle, I want to continue to confirm the following:
1.Can the user manual be deleted directly?
2.What is the top-level container for demonstration purposes? What should be deleted?
3.I don’t see the container of InBox and Zettelkasten in the map view?
Thanks!
Hi @Ting. Yes, there is no harm in deleting the user manual. There is no single top-level container; get used to the file, then modify and delete to your content.
For this particular file, I paid no attention at all to the a map view. For my own way of working, I placed the Inbox and Zettelkastens as children under “The Zettelkasten”, which is a separator. I think this is why you don’t see them on the map.
@mwra Thank you very much. I have found that these 2 are hidden in the map view in a separator container, but I found a strange problem. The following picture is what I look like in Tinderbox9, but it is normal in Tinderbox8.
@Ting, I’m unclear as to what you are asking (also your screen-grab’s caption got truncated.
I think that is a misunderstanding. Just as map adornments are only seen in Map views, so the separator was an Outline view feature and deliberately not shown in map view (there were fewer views back then.
By original intent, separators were meant as just that: an outline affordance for dividing up content; different from adornments, obviously, but offering a similar sort of arrangement role. Separators were supposed not to allow nesting of notes (i.e. acting as containers. But, by the time it was realised they could do this, some users lobbied to keep the unintended functionality. But regarding it as ‘hidden’ will simply configure.
@mwra Sorry for my confusion, the latest question is: Using this template file, the browser view of “Personal”, “Keyword”, and “Reference” displayed by Tinderbox 8 is normal as shown in the figure. The 9 version is as shown in the figure above, and only the ranked first One is separated by a double horizontal line to highlight.
I’m sorry, I don/t have the document to hand, and you’ve only posted one screen-grab so I cant compare the two different things you describe. I might help to know what view type is active in the grab you posted. It looks like Attribute Browser view with columns enabled.
N.B.: Separators are not listed in AB view.
Now the old system and the 8 version of Tinderbox are not around, and the comparison screenshot will be uploaded later. The difference between them is the Mac system and the Tinderbox version!
@mwra This is a comparison of the two versions starting this thread file “quoting” the browser window.
This still doesn’t read coherently for me. The first screen grab above looks like what I get in v8 and v9. Here is an AB View in v9 on my (macOS 10.14.6) system. I’m using a ‘starter’ file simply because I don’t have the file you are showing:
Also I don’t understand the meaning of your caption “…version 9 only has first sorted” as it is an incomplete sentence description. Please understand this is a user forum . We can only see /know what you choose to share with us. We definitely can’t see the picture in your mind of the problem.
Could perhaps describe it in terms of;
- What you see
- What you expected to see, and why. The ‘why’ is important in flushing out untested assumptions (i.e. how we ‘assume’ things work rather than the way they actually do).
It might also help to upload a minimal test file showing the problem - i.e. not a whole zettel but just enough to replicate the issue (all the extra uninvolved note just create ‘noise’ when trying to look for the problem).
The first screenshot of the #68 floor screenshot is my screenshot in Tindebox8, which is also a normal screenshot, which I want to see, but I use Tinderbox9 to start the same file as the second screenshot. It is incorrect and its reference is not correct. The back is highlighted in gray to separate, please look at the background of “…Tinderbox Way”.
OK, I read this to mean your two screen grabs in message number 68 above (I suspect ‘floor’ might be a machine translation error). So, it seems the problem is you are saying the category headers in the Attribute Browser view aren’t showing with a grey fill? Is that correct?
But, as seen in my screen grab from version 9, this is not the case for all users:
So, does this issue affect Attribute Browser view in all TBX files on your Mac or only the Zettelkasten one? To understand the issue, it is necessary to repeat the problem on a different Mac using the same version of the app. It may be to do with the OS version (I only have 10.14.6 at present).
I don’t know if anyone else is not seeing a grey fill to the category banners in Attribute Browser view?
Yes, your understanding is completely correct. The banner is not filled in the “Property Browser” of Tinderbox9 version (it should be said that only the first one is filled). My system is 11.5.
1 Like
Thank you for that confirmation.
Dear talazem,
Thank you for sharing your nice Zettelkasten starter file.
I have been studying your starter file for the past few months.
I usually use org-roam in Emacs 27.2 to create note files with the same functionality as the Zettelkasten method.
Back to the main topic.
Please forgive me for asking such a boring question like a newbie.
I do not understand how to use “## Connections ##” and “## Literature ##” in your pt_Note.
How do you use these two places?
If you could unpack an example explanation of how you use them, I would be very happy.
Thx and regards, WAKAMATSU kunimtsu (from Japan)
Some thoughts. I love the Zettlelkasten framework and ideals, e.g. each “zettle” (aka your note) should be reduced to its atomic essence (1 idea, cited, in your own words). You can then curate these by linking, refining, etc. Which will ultimately lead to the next two steps in the 4C process, “create” and “contribute”.
When it comes to the Zettlekasten file I think it offers some amazing training wheels, but it does come with a lot of, IMO, unnecessary overhead. It feels like we’re applying a 1950 process to 2020 technology.
For example, at least in my workflow, I find generating a unique ZettleID unnecessary, as this ID already exists in the system, $ID. There are other affordances that I think can be stripped away in the workflow to create purity in an end-to-end workflow that is capable of leveraging any number of apps along each stage of the workflow.
Please, don’t get me wrong, I’m not criticizing the Zettlekasten file at all, it was instrumental in my own learning and development. But, when applying Decarte’s four rules to knowledge management–1) Accept as true only what is indubitable, 2) divide every question into manageable parts, 3) begin with the simplest issues and ascend to the more complex, 4) review frequently enough to retain the whole argument at once (Kemerling, 2011)–it is important to only bring forward those methods that are relevant for today’s context.
I’ve been working on the re-envisioned end-to-end flow for about 10 months now, presented a high-level review in last week’s meetup. More recently, I’ve been working with @lfriedla to refine it and plan on teaching it with @bmgphd in a more formal setting soon. And, as always, a huge shout-out must be given to @mwra for which none of my work would be possible were it not for his efforts and friendship.
REFERENCES.
Kemerling, G. (2011, November 12). Descartes: Method . Descartes: Method
2 Likes