Working in @obsdmd has forced me to rethink of a PKM strategy that is also compatible with Roam, and here's what I've come up with so far: Input Notes, Summary Notes, Connector Notes, Category Notes, and #properties. Let me explain what these mean...
This strategy was built because I needed some structure while preserving the anti-hierarchy of zettelkasten - inspired by MOCs, Zettelkasten and how language works.
Input Notes: Any kind of input - they can be notes taken down from media (pdfs, books, videos, courses, interviews, classes), conversations, thinking, journalling. These contain metadata - authors, links, dates, etc.
~ aka "reference notes"/"fleeting notes".
Summary Notes: What I take down under input notes gets extrapolated into atomic units of knowledge, ranging from single words to phrases. These function as nodes or APIs which will be connected together later and remixed to form new ideas.
~ aka "literature notes"
Connector Notes: These provide contextual relationships between atomic "summary notes". For example, "apple is red" is a connector note - whereas "apple" and "red" are two different summary notes.
~ aka "synthesis notes"/"evergreen notes"
Category Notes: These act like stars that pull planets into their orbit. In the same way, category-notes pull summary and connector notes into thematic connections. The difference is that one note can belong to many category notes.
~ aka "folders"/"MOCs"
#properties: As tags act differently in Obsidian, the only way it makes sense to use is as adjectives, status indicators or properties. I use them as descriptors.
In this example, two summary notes, [[hyponatraemia]] and [[ADH]], are linked indirectly through a connector note [[body senses increased osmotic concentration and retains water]].
This system doesn't just make you retain things... through visually browsing the graph (inspired by @RobertHaisfield's own zettel system), we can SEE how ideas can be linked together - we can build synthesis on top of existing ideas *just like that*.
What the actual note looks like...
Seeing these summary-notes, I can already see a contextual connection waiting to be made between [[fluid overload]] and [[pneumonia]]. It's like a symphony of ideas.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Winston

Winston Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @syncretizm

1 May
The directionality of attention is what drives usage of roam - not just the existence of bidirectional links. Some thoughts below...
Attention is like a spotlight - just as it can shift from a sound in the room to the taste on our tongue to a visual object or a sensation, it can move from 'concept' to 'concept'.
The shifting of attention from one object to the next object creates a chain of continuity. Going from bullet → bullet, idea → idea, or clicking links offers an unbroken chain of attention moving from object to object
Read 9 tweets
1 Jan
If there is no "hierarchy" in Roam, there is no true "nesting" of bullets. There are only different relationships.

Nested bullets *do not* indicate a parent-child relationship - they talk about "AND" (÷) vs "OR" (×) relationships.
A union B = OR relationship
A intersect B = AND relationship
A nested bullet has an AND relationship with its parent or child; A bullet in the same level has an OR relationship with siblings. Each time we create an indent, it is not creating something smaller - you are creating a new circle with an intersection with the "parent".
Read 7 tweets
31 Dec 20
My attempt to visualize the differences between a [[page]] and a ((block)) in @RoamResearch with my horrible drawing skills
It seems that [[page]]s seem to travel perpendicularly to ((block)) creation. Almost like it grows organically at the same time while sharing those blocks. It is almost like a query, but a fascinating question pops out:
Why is there an ability to generate blocks within a [[page]], if this page does not live as a block, but simultaneously in every other block? It's almost like the [[page]] is from a different dimension.
Read 9 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(