How to order Zettelkästen
@zettelkasten
I keep thinking whether I should use a naming convention for Zettels. The original Zettelkästen system uses a hierarchical addressing system, where the naming of the notes is of crucial importance to indicate which notes belong together.
The address space often uses this system with alternating digits and letters. This would be a sequence, a @Folgezetteln :
1a - 1a1 - 1a2 - 1b - 1c - 1c1 - 2
New notes can be insert somewhere in this chain by extending the address space. However, this creates inflexibility because you can never change this namespace anymore without breaking your system. It also fixes connections rather than allowing free rearrangement. You can of course always still cross-link notes, but nevertheless the "Folgezetteln" risk becoming normative for your approach to a particular topic.
The main argument against such a strict address space that implies a hierarchical ordering, is that it is only required for physical indexing systems, whereas we now have better tools to achieve similar ends but with more flexibility:
Some alternatives to Folgezetteln are outlines and tags. An outline is an index of Zetteln that create a sequence. Tags reveal indexicality in a search.
In other words, if filenames do not indicate sequencing anymore, we need to manually make extra notes that indicate sequences. This is indeed what I currently do.
Question: at what point does the system turn into a wiki? Outlines are characteristic of wiki's.
A remaining controversy regards the historicity of Folgezetteln.10 Do they have a place in a digital Zettelkasten, or were they simply a by-product of the material constraints of index cards?
The primary argument for maintaining sequences of Folgezetteln so far seem to be that they provide a visual overview of links at the level of file browsing, search and listing of notes. This is a argument that is based upon lack of tools and methods to otherwise accomplish the same overview and is therefore a compromise of the Zettelkasten system
Source: [ https://omxi.se/2015-06-21-living-with-a-zettelkasten.html ]
On computers, we do not have to be restricted to the idea of having a piece of paper in a single folder. We can store the same note in many folders, or better, represent it in a graph rather than a tree structure.
Should a digital Zettelkästen not be a relational database?
The idea that “in the end”, a Zettelkasten consist of a folder where each Zettel is a file in a file system is a limiting metaphor compared to a dynamic database that can arbitrarily construct relations between data
The reason for this limitation is that the file system as a framework for data handling is itself a metaphor based on a paper based file handling system in which Folgezetteln makes sense. The idea that “in the end”, a Zettelkasten consist of a folder where each Zettel is a file in a file system is a limiting metaphor compared to a dynamic database that can arbitrarily construct relations between data.
Different ideas to explore this idea while still using plain text:
One way of doing that while still keeping with a plain text file based system is to use scripts that render outline files. These outline files could follow links in the Zettelkasten – provided that links are unidirectional (which makes sense) – and render indexes of note sequences. This could both be rendered as notes in themselves, or it could be dynamically rendered as STDOUT. A combination of both is preferable. The reason that unidirectional links make sense is that only one of the notes (the linking note) is written with the knowledge of the other note (the linked note). Instead of the linked note also containing a traceback to the linking note, a dynamic index should be possible to render as a list of several note sequences where this note is a part.
The discussion boils down to a conflict between a rendering of relations as a sequence or as a network. The sequence allows a note to only be part of one history (but several futures in the form of branches) while a network has no time-variant to the links, but on the other hand do not allow a tracing of a sequence in more that one step. In a network we can’t visualize a sequence of more than one jump. If the relations are to come in the form of a database, that is as a network, then the sequencing need to happen with manually constructed outlines indexing sequences of jumps throughout the network. This is similar to how a wiki relies of indexes of links between files or parts of files. In a file-system based organisation on the other hand, a note can’t be part of several histories unless there is a merge of these histories into one future. Once the two histories arrive at the point of merger, they can’t have separate futures anymore, although it is possible that there are new branches created
Follow-ups:
- How to order Zettelkästen specifically with Markdown
- I have this fantasy to make a text only relational database with ultra-simple tools
- For example, see [ http://matt.might.net/articles/sql-in-the-shell/ ] on relational shell programming.