Obsidian Note-Taking System for Academics & Students - Full Tutorial & Demo (Write Papers Faster)

Main ideas, concepts, and lessons

• Personal motivation / origin story

  • The speaker (a biology PhD student/researcher) restarted learning from scratch after a long break from biology knowledge.
  • They explored multiple note-taking/learning systems (e.g., Smart Notes, Second Brain, Zetle method) and digital tools, then built their own approach in Obsidian.
  • Claimed outcomes:
    • Finishing a PhD 5 months early
    • Producing four first-author papers
  • The system supports writing faster and reusing verified claims.

• Why a complex information system is needed

  • Core analogy: PhD = chess
    • Winning requires strategy, not grinding.
  • Many students “grind” rather than apply strategy; therefore, the solution is organizing knowledge.

• Inspiration from Wikipedia

  • Wikipedia’s structure:
    • Links connect concepts.
    • References separate fact from speculation.
    • There’s no “folder” hierarchy—content is navigable via linked concepts.
  • The speaker’s goal: build a “personal Wikipedia” for academic research—knowledge as a network of linked, referenced claims.

• Key methodology: shift from sequential summarizing to topical/scalable notes

  • The system’s biggest challenge is mindset, not tools:
    • Don’t take notes as “sequential paper summaries” (highlighting + paraphrasing).
    • Instead extract topical claims so the repository can scale to hundreds/thousands of notes.

---

Step-by-step methodology (detailed)

A) Software stack and basic setup approach

• Use Obsidian as the “browser” for your personal knowledge network.
• Store knowledge as text files on your computer (a local vault).
• Add PDFs and other resources into the vault so they’re part of your system.
• Enable an Obsidian formatting convenience plugin:
  • Install the community plugin “Editing toolbar” to avoid learning Markdown syntax.

B) Create and structure notes to mimic Wikipedia-like knowledge networks

• Start with concept nodes:
  • Create a note like “biodiversity”
  • Create another like “tropical forests”
  • Paste initial text/examples (the speaker uses Wikipedia as seed content in the demo).
• Use links instead of folders for navigation between concepts:
  • In Obsidian, create internal links using [[note name]]
  • Obsidian supports autocomplete even when the typed text is only part of the target name.
• Link to external sources via URLs:
  • Use Markdown link formatting (Obsidian generates it) so clicking opens outward.

C) Use note UI features to support readability (optional)

• Headers
  • Create header levels (e.g., H2) by formatting header text as a header.
• Callouts (boxed sections)
  • Use callouts to separate content types (definitions, summaries, AI outputs, warnings).
  • Support collapsed callouts via a special marker (described as a “minus after the square bracket”).
  • Optional: install “call out manager” to streamline callout usage.

D) Academic organization: folders + source notes + PDFs (recommended workflow)

• Create folders:
  • nodes/ (concept/topic/argument notes)
  • sources/ (source notes: PDFs and raw-material notes)
  • support/ (images/embeds so they don’t clutter notes)
• When adding a paper:
  • Drag-and-drop the PDF into the vault
  • Move/store it under sources/ (and/or related folders as described)
  • Prefer keeping PDFs separate from main note scrolling:
    • Open PDFs in a split view while writing notes (rather than embedding PDFs in topic notes).

E) Use properties (metadata) for scalable browsing/filtering

• Add document properties using the “properties” section (opened with --- --- at top).
• Suggested properties:
  • author, journal, title, tags/categories (speaker notes you can add many)
• Make properties link to other nodes:
  • Example: if journal is [[PNAS]], Obsidian can create missing nodes on demand.

F) Use Dataview / “bases” (tables) instead of clunky research databases

• Create a “base” (table view) using the Obsidian command palette:
  • Filter displayed notes by properties (e.g., show only files from sources/)
• Example base:
  • Base name: “papers”
  • Rows: paper/source notes
  • Columns: selected properties like author/journal/title
• Benefits:
  • Rapid preview and drilling into the referenced paper/PDF
  • Sort/filter/rank by properties (e.g., year)
  • Speaker claims bases can effectively replace Zotero’s “clunky UI”

G) The core note types (“trinity”)—what to store where

You use three node types:

1. Source nodes (written by others; mostly immutable)

   • Contain raw material:
     • Usually the PDF (or web page text imported via clipper)
   • May also include:
     • Extracted figures closely tied to the source

2. Topic notes (your extracted claims; grounded in sources)

   • Contain claims extracted from papers
   • Each claim links back to the specific source note where it came from
   • Over time, these notes become “mini literature reviews”

3. Argument / thinking notes (your own thoughts/questions/speculation)

   • Contain:
     • Questions, interpretations, struggles, ideas, brainstorming
   • Separation is crucial:
     • Others’ claims (topic/source) vs your speculation (argument)

H) Extract claims from a paper into topic notes (claim-linked workflow)

• While reading a source:
  • Identify a sentence or passage that supports a specific claim
• Create/use the relevant topic note for that concept.
  • Example: a claim about biodiversity impacts becomes a topic note under biodiversity.
• Add the claim as an “atomic” bullet/sentence.
• Link the claim to the source node so verification is possible later.
• Keep topic notes as atomic sentences:
  • Minimalistic claim bullets that can later be assembled like puzzle pieces.

I) Link verification to the exact location inside the PDF

• Use Obsidian’s PDF link-to-selection:
  • Highlight a sentence in the PDF
  • Right-click → copy link to selection
• Paste that link into the topic/source context so you can jump directly to the exact highlighted sentence.
• Motivation:
  • Avoid accidentally attributing a claim to the wrong paper in a reference list.
  • The speaker discusses a convention:
    • Use anchor text like “in” plus a link to the actual source note, while maintaining verification at the PDF selection level.

J) Automate linking/annotation between notes and PDFs (optional)

• If the “in/link” convention is cumbersome, install PDF++:
  • Automates highlights and linking between notes and PDF evidence.

K) Import non-PDF sources (web pages)

• Use Obsidian Web Clipper to import web content:
  • Templates can import text/images/links
• In these cases:
  • The source note contains the raw material itself (rather than linking to a PDF).

L) Write papers faster using atomic sentences + linking

• Topic notes contain many atomic claim bullets.
• When drafting a paper:
  • Combine related atomic sentences into paragraphs
  • The claim bullets already include links to supporting references, speeding verification
• AI can help convert linked atomic sentences into paragraph drafts (speaker frames this as producing usable first drafts).

M) How idea generation happens (side effect)

• Idea generation occurs by navigating the knowledge graph:
  • From one topic note to related topic notes
  • Eventually prompting a new argument/question note
    • Example chain: fossil fuels → climate change impacts → penguins → new question
• Metaphor: a “garden” model
  • Plant notes over time, then harvest ideas/papers later.

---

Outcome / claimed benefits emphasized throughout

• Faster academic writing by reusing extracted, verifiable claims.
• Better organization that scales over years.
• Easier verification/double-checking via:
  • source notes
  • exact PDF selections
  • backlinks
• More reliable research rigor by explicitly tracking:
  • what others said vs what you inferred or speculated
• Graph-based navigation
  • topic nodes connect to relevant source nodes and other topics

---

Speakers / sources featured (as named in subtitles)

Speaker (primary)

• Unspecified individual (the video’s presenter/creator; personal “I” voice)

Referenced books / authors / systems

• “Smart Notes” (book)
• “Second Brain” (book)
• Zetle Custom Method (Zettelkasten-related method as referenced)
• Sansu’s “Art of War” (quoted: “tactics without strategy is the noise before defeat”; “Sansu” named in subtitles)
• EO Wilson
  • Referenced via biodiversity definition and book
• “The Diversity of Life” (EO Wilson’s book)
• Elizabeth Bo (referenced as an author in the demo article context)
• Bosi 2018 (appears as “Bes 2018” / “bokes 2018” in subtitles; described as a source for the biodiversity definition)

Specific academic papers / studies mentioned

• Nature study (about ~78% of students working >40 hours; cited generally as “Nature”)
• Vanevic 2020 (example source paper name used in multiple places)
• PNAS (journal referenced for metadata)
• Mentions of “paper number 24 and 25” in an example reference list

Platforms / tools / services

• Wikipedia
• Obsidian
• Notion
• Evernote
• Zotero
• Chrome / Arc (as browser analogy)
• AI (generic mention)
• PDF++ plugin
• Obsidian Web Clipper extension
• Dataview / “Bases” (referred to as “bases”)

Other referenced entities / examples

• John Campbell (via email thread; used to show argument notes growing)
• Email thread (with John Campbell; no further details)

Note: Exact speaker names beyond the presenter were not provided in the subtitles.