Research to Notes to Stories feat. Eleanor Konik (Obsidian App)

TL;DR

Quick Add plus a Zettalyzer macro can convert Zotero quote imports into embedded atomic Zettles while keeping the original source note readable and intact.

Briefing Cornell Notes

Briefing

Eleanor Konik’s Obsidian workflow centers on a practical fix for a long-standing tension in personal knowledge management: how to keep source material “chronological and beautiful” while still turning it into atomic, reusable notes. Her answer is Quick Add—specifically a Zettalyzer-based macro that converts Zotero “empty notes” dumps into embedded atomic notes under the original source note, so the source stays intact while the extracted pieces become easy to search, link, and reuse.

Konik starts with a real-world problem from her day-to-day research: she often pulls quotes and page numbers from Zotero, then needs to move quickly—especially when writing newsletters or articles—without re-annotating everything by hand. In her vault, raw imports land in a “Zotodumps” folder for later processing. Once she’s ready, she runs Quick Add and points it at a JavaScript file Christian helped create. The result is an “explosion” of the source note’s header sections into many new Zettles that remain embedded and linked back to the original source. She emphasizes that the source note isn’t split into separate files (which would lose the chronological reading experience); instead, the atomic notes are embedded sections that inherit the source’s structure.

A key detail is how she preserves stable linking. Rather than linking to headings that can break if renamed, she links to the generated Zettles—so renaming headings doesn’t shatter her network of connections. She also uses a “Koenig method” shorthand: a short title on each Zettle that summarizes the core point, followed by commentary on why it matters. That structure turns extracted quotes into something closer to reusable claims—useful when she later drafts analysis, newsletters, or story ideas.

Konik then connects the workflow to storytelling and publishing. Research becomes “fodder in the brain,” and she tracks which notes feed which stories using the Breadcrumbs plugin, assigning parent/child relationships via YAML metadata. For her newsletter, she’s experimenting with “behind the scenes” analysis—treating the research iceberg as part of the reader experience rather than hiding it under the finished narrative. A chestnut-tree story becomes a case study: she ties together agricultural history, regional economic devastation, and folklore, then publishes an additional analysis layer that documents the research choices.

The session also surfaces how she organizes the rest of her system around this extraction pipeline. She describes a “Johnny Decimal” filing approach that keeps folders shallow (no more than two levels) so she always knows where something goes. She flattens her vault over time when she realizes folder uncertainty is a sign the structure needs refactoring. And she keeps her public Obsidian Publish version “as close to working as legally possible,” removing private conversations, sensitive personal data, and copyrighted materials.

By the end, the workflow isn’t just about note-taking mechanics. It’s about maintaining momentum—turning raw sources into atomic claims without losing context, then using that network to write faster, link more intentionally, and share research in ways that spark conversation.

Cornell Notes

Eleanor Konik’s Obsidian system solves a common PKM tradeoff: extracting atomic notes without destroying the usefulness of the original source. Using Quick Add plus a Zettalyzer macro, she converts Zotero “empty notes” imports into many embedded Zettles that link back to the source note while keeping the source intact for chronological reading. Her “Koenig method” adds a short, claim-like title to each Zettle, followed by why it matters—making later writing (newsletters, articles, story analysis) faster and more searchable. She then tracks which research feeds which stories using Breadcrumbs (parent/child YAML metadata) and publishes “behind the scenes” analysis to share the research iceberg, not just the tip.

How does Quick Add let Konik keep source notes intact while still getting atomic notes?

She imports Zotero quotes into a single source note (often via Zotero “empty notes” dumps). When she runs Quick Add, the Zettalyzer macro turns header sections inside that source into many new Zettles, but it does so as embedded sections rather than splitting the source into separate files. That preserves the “beauty” of reading the source chronologically while still producing atomic, linkable units for later writing.

Why does Konik prefer linking to generated Zettles instead of headings?

Headings can be fragile: if a heading title changes, links to that heading can break. By linking to the generated Zettles (created by the macro), she avoids breakage when she edits titles. The embedded Zettles still reference the original source, but the links she relies on are more stable.

What is the “Koenig method” in her workflow?

Each extracted Zettle gets a short title that summarizes the key point (a claim-like label), followed by additional commentary on why it matters to her. She uses this structure to turn quotes into reusable reasoning—e.g., connecting a historical example (Romans banning skywatching) to a modern political analogy (filibuster dynamics).

How does she connect research notes to specific stories or newsletter pieces?

She uses the Breadcrumbs plugin to assign structured relationships in YAML—marking notes as parent/sibling/child (she notes it can show as “implied” connections). After writing a story, she creates a child note for it and links the relevant research notes to that story via the plugin’s metadata, so she can later trace which research fed which narrative.

What does “Johnny Decimal” mean in her vault organization?

It’s a shallow folder system (typically no more than two levels deep) using clearly defined buckets so she always knows where a file belongs. She treats uncertainty as a signal to refactor: if she can’t tell which folder something should go in, she changes the folder structure. She also flattens her vault over time to reduce confusion.

How does she handle privacy and rights when publishing her vault?

In Obsidian Publish, she removes or avoids sharing sensitive personal data (like private conversations and family identifiers) and copyrighted materials she doesn’t have rights to redistribute. She keeps a “working vault” for others to poke at while excluding items that would be unethical or legally risky to share publicly.

Review Questions

What problem does Konik’s Quick Add + Zettalyzer macro solve, and what does it preserve compared with splitting sources into separate notes?
How do embedded atomic notes and stable Zettle links change the way she edits and reuses information later?
Describe how Breadcrumbs (YAML parent/child metadata) helps her move from research to story-specific drafting and analysis.

Key Points

1
Quick Add plus a Zettalyzer macro can convert Zotero quote imports into embedded atomic Zettles while keeping the original source note readable and intact.
2
Link to generated Zettles rather than headings to reduce link breakage when headings are renamed.
3
Konik’s “Koenig method” uses short claim-like titles plus “why it matters” commentary to make extracted notes reusable for writing.
4
Breadcrumbs with YAML parent/child metadata helps track which research notes feed which stories and newsletter analysis pieces.
5
A shallow “Johnny Decimal” folder structure (about two levels deep) reduces uncertainty and keeps filing friction low.
6
Vault refactoring is driven by folder ambiguity: if she can’t quickly decide where something goes, she reorganizes.
7
When publishing, she strips private conversations and sensitive data and avoids redistributing copyrighted materials she lacks rights to share.

Highlights

Quick Add turns Zotero-imported source notes into many embedded Zettles without splitting the source file—atomic notes with preserved context.

Stable linking comes from linking to generated Zettles, not headings that can break when renamed.

Her newsletter experiment reframes “behind the scenes” research as part of the reader experience—an iceberg approach rather than a hidden process.

Breadcrumbs + YAML metadata lets her trace research-to-story relationships with more structure than backlinks alone.

Johnny Decimal organization stays shallow so she never has to guess where a note belongs.

Topics

Mentioned

Eleanor Konik
PKM
DNS
MOC
YAML
PDF
CSS
MOC

Research to Notes to Stories feat. Eleanor Konik (Obsidian App) | LYT House Episode 1