summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorYann Herklotz <git@yannherklotz.com>2022-12-26 19:19:16 +0000
committerYann Herklotz <git@yannherklotz.com>2022-12-26 19:19:16 +0000
commit74514ec0e2bb06d0a0f87c0a7f8d593231b73e16 (patch)
tree0bb39fcd9bfc081c3a9faaf8eab0c915bea3bb20
parentaa4de4c3bae110f4b89b2ce98660415c24a69750 (diff)
downloadorg-zettelkasten-74514ec0e2bb06d0a0f87c0a7f8d593231b73e16.tar.gz
org-zettelkasten-74514ec0e2bb06d0a0f87c0a7f8d593231b73e16.zip
Update documentation
-rw-r--r--doc/org-zettelkasten-manual.org59
1 files changed, 14 insertions, 45 deletions
diff --git a/doc/org-zettelkasten-manual.org b/doc/org-zettelkasten-manual.org
index e5b424b..0584046 100644
--- a/doc/org-zettelkasten-manual.org
+++ b/doc/org-zettelkasten-manual.org
@@ -12,35 +12,30 @@
#+cindex: introduction
Niklas Luhmann’s Zettelkasten is becoming increasingly popular for being a great
-note taking technique. However, it is often misunderstood as taking notes
+note taking technique. However, it is often misunderstood as taking notes
without any structure, whereas Luhmann actually structured his notes
-hierarchically, but also allowed for arbitrary links between notes. This post
-will describe the general note-taking workflow that Luhmann used and a practical
-implementation of the Zettelkasten in Emacs’ built-in org-mode, which I have
-been using regularly for my notes and has been working well.
+hierarchically, but also allowed for arbitrary links between notes. Org
+Zettelkasten tries to following the general note-taking workflow that Luhmann
+used by using as much of Emacs' built-in Org as possible.
** Inserting new notes
#+cindex: notes
There are several possible notes that can be inserted into the Zettelkasten, but
-the need for them should arise naturally and one therefore doesn’t have to think
-about the separate types of notes directly. In addition to the following types
-of notes, Luhmann also had a separate box for references and notes about those
-references, however, these are not added to the Zettelkasten in my case because
-I felt like using tools specifically to keep track of references is a better
-system for me. This is mentioned further in the keeping track of references
-section.
+the need for them should arise naturally and one therefore does not have to
+think about the separate types of notes directly. For references I usually use
+the fantastic [[https://joostkremers.github.io/ebib/][ebib]] package.
*** Permanent Notes
#+cindex: notes
Inserting new notes into the Zettelkasten can be done for any new piece of
information one wants to permanently add to the tree of notes and therefore the
-network of notes. These are therefore called “permanent notes,” however, these
-are not the only notes that may appear in the network. The most important thing
+network of notes. These are therefore called “permanent notes,” however, these
+are not the only notes that may appear in the network. The most important thing
to take into consideration is that “permanent notes” should be completely in
your own words, and express an idea that also links to other parts in the
-network. At the start it may be necessary to create a few topics that these
+network. At the start it may be necessary to create a few topics that these
notes fit into, however, eventually one should be able to find notes that are
similar enough which this new note should follow.
@@ -49,36 +44,10 @@ similar enough which this new note should follow.
Apart from that, there can also be “index notes,” which try to give some
structure to a subsection that may have gotten lost with all of the branches
-that may have been added. In addition to that, these may tie in other notes from
-other topics as well that relate to that topic. These can therefore just be
-added whenever you feel like there are too many notes for a subtopic and cannot
-keep track of all the possible links.
-
-** Keeping track of references
-#+cindex: references
-
-Luhmann kept track of references by inserting them into their own box in a
-linear structure and then referring to them by ID whenever they needed to be
-cited. These are often called “bibliographical notes.” In addition to that,
-notes that were not permanent and more relevant to a specific paper or book were
-also added separately to the other notes and were called “literature notes,” as
-these often contained summaries of the papers or books that were cited. Even
-though these were written in his own words, they only really were relevant to
-the paper itself as temporary notes, which could eventually be added as
-“permanent notes” into the Zettelkasten and linked to other notes when a
-narrative developed that did link this piece of knowledge to other notes.
-
-As references are quite separate to the other notes anyways, I prefer to keep
-them quite separate as well, and instead use standard bibliography management
-tools to keep track of all my references as well as linking notes to the
-references in the tool itself. In my case this is using ebib in Emacs, however,
-any alternative works as well, such as Zotero.
-
-In my notes, I then reference these by their bibtex identifier that is
-automatically generated, and which is later used when referencing the same
-literature in LaTeX, for example. This allows me to keep these notes quite
-separate and forces me to think about links when I do eventually add them to the
-network as “permanent notes.”
+that may have been added. In addition to that, these may tie in other notes
+from other topics as well that relate to that topic. These can therefore just
+be added whenever you feel like there are too many notes for a subtopic and
+cannot keep track of all the possible links.
* GNU Free Documentation License
:PROPERTIES: