luhmann id

1. Rule
2. Fixed and Serious…. NOT!
3. is it of any use
4. Reference
Backlinks
- multiple org-roam notebases
  - (.dir-locals.el)

Luhmann id is an unique id system based on semantics of nodes.

A luhmann id would look like this: 1a4d5j

1. Rule

Figure 1:

Top level: 0,1,2,3,: if you have an idea that has nothing much to do with previous ideas, give it a top level id like 4.
Comments: if you have a note relating to a note 1 a lot, give it 1a
Continue: if you have a note that follows after 1a, give it 1b

2. Fixed and Serious…. NOT!

The border and definition on comment and continue is vague, but a way of thinking this is 1a1 would be all about 1a, while 1b could be following the discussion of 1 but not at all related to 1a.

This is a vague and fuzzy definition with a lot of space. In the end these are IDs and way of organizing files physically, to make more sense, use connections.

3. is it of any use

strucutre impressions: 0 - meta, 1,2,3,4 - seperate issues, 1a,1b - seperate issues about 1. It gives a hint of relationship just like mind mapping(the tree structure bear lots resemblance).

4. Reference

https://zettelkasten.de/introduction/ (where image is from)

Backlinks

multiple org-roam notebases

(`.dir-locals.el`)

Place a .dir-locals.el file with the following content to the root of the project notebase(in here ~/project/robotics/):

((nil . ((org-roam-directory . "~/project/robotics/") ;;don't forget the trailing "/", otherwise
;;org-roam-node-find would not find anything
         (org-roam-db-location . "~/project/robotics/org-roam.db")
         (org-roam-node-display-template . "${title} ${doom-type:12} ${doom-tags:42}")
                )))

on org-roam-node-display-template

I tend to use a large notes.org file with headings and luhmann id structure to organize project notes, so titles get very long if use doom-hierarchy if the id be 1b2a3 (displaying 1, 1b, 1b2 1b2a and 1b2a3 whell encoder)

effect: after setting up this file, each time you open a file under this directory, emacs would prompt you to load file-specific variables on our 2 objectives, and org-roam-node-find/insert would default to the directory, which makes sense: you’d want to visit zettels in the same zettelkasten.