my research system

Table of Contents

My research system is organized with similar idea to my GTD integration, but with Zettelkasten as major component.

The system now consist of the following procedures and places/buffers:

1. idea capture

Idea capture is done with similar manner to GTD: Capture everything into one inbox for further processing. For now, idea capture are binded to s “slip box” template in org-capture, which collect ideas into RoamNotes/inbox.org.

  • strictly speaking, I capture everything inside OrgNotes/capture.org. but if I know clearly that it’ll end up in RoamNotes/inbox.org, I’ll just capture it there.

2. reading paper

Paper reading is handled with 3-pass method described in KeshavS :: How to Read a Paper.

3. literature review/survey

literature review/survey is handled with the literature survey method described in KeshavS :: How to Read a Paper

4. compilation

this is not completed, but it is likely I’ll find guideline in Ahrens, Sönke :: How to Take Smart Notes

5. writing article

The same with compilation, likely I’ll find guideline in Ahrens, Sönke :: How to Take Smart Notes

6. Tasks

6.1. HOLD review inbox.org

  • link to inbox.org
  • reviewed some entry in inbox.org
    • elaborated/simplified some of them
    • merged some of them
    • discarded some of them
    • promoted some of them into Zettels
    • create task out of some of them

Backlinks

Herman’s systems

(Current > way-of-life)

initiated by me; target of weekly review; my way of life; general system

atomicity make bad note better

When a note is of bad quality and written in whole, it can be hard to reuse any of it - like my GTD integration or my research system.

If a note does not make sense, but the subsections of it are atomic and thus make sense in a narrower context or simpler form, those subsections could be reused easily(if they are already zettel, they could immediately be reused; if they are only subtree in the bad note, making them their own zettel is only copy and paste), deleting the bad note is also easier

documentation

This is self-documentation of this knowledge base. Tools, representations and procedures are included

my GTD integration
capture - review
my research system
research with the notes.
tags
doors to the building of notes

review 2024-01-27

  • on Herman’s systems:
    • I simplified most existing things:
      • capture - I now use one capture inbox for everything: task, ideas, bookmark, so GTD capture and research capture are combined. This is a practice, not to say it is good or bad, it is simple enough to work decently
      • review - I now review my zettelkasten daily, but sometimes there’s more than what I can do on the instant.(like the whole of my research system is like a big pile of nonsense right now, and so is my GTD integration; I’ll reduce, or delete them entirely very shortly after)
      • tags - I don’t use it as of now. I may start it somewhere in the future, but now I don’t use it
      • process - One process diagram should be enough, instead of this giant load of text
      • engage - checking agenda, and that’s it. I use phone timer more often now.
    • in general, this whole page is very not useful. I use current life script more now, although it does not contain information on research and stuff. I could extend it to include these though.
    • I use some new concepts, like primitive action, and new set of very limited primitives in top of my mind.
    • I practice slow-carb diet and use a fitness program now, they should be included.
    • It is decided: I’m stuffing everything in the lifestyle script. research is a lifestyle, fitness is a lifestlye, shake the staticity off is a lifestyle, I live and I live with a style. Yet I may want to have it split into smaller pieces
  • on the zettelkasten
    • lots of places for reduction and improvement it is not very useful in general. old, rambling note that should be discarded in second batch processing are scattering at places where I quote them, thinking they are good concise notes. A lot of places could use visuals and concise words, examples or links to concrete examples
  • on the tasks
    • the reduction is working, there’s a lot to think for the tasks. this means a change to the my GTD zettel is in request
  • on tracking and experiments
    • tracking is hard to remember. but it is damn useful.
    • highlight + comment method and capture is a form of tracking thoughts
    • so I think I should track some specific, explicitly measureable things, and have them noted somewhere so I don’t forget

Author: Linfeng He

Created: 2024-04-03 Wed 20:20