obsidian-literature-workflow

To synchronize Zotero literature notes with an Obsidian vault, this workflow imports your literature notes and normalizes them using standardized YAML frontmatter. It organizes the notes into Papers and Knowledge sections to maintain a canonical project memory.

A literature canvas in Obsidian is a visual map of your knowledge and papers. This workflow generates it automatically by linking normalized notes and producing a Maps/literature.canvas file, allowing you to visualize literature relationships across your project memory.

Yes, you can use this workflow without the Obsidian MCP. It relies on a filesystem-first approach to read vault context, update daily notes, and produce the literature canvas, ensuring traceability and reproducibility without requiring the MCP.

You organize project memory by applying standardized YAML frontmatter like title, project, and updated to your notes. The workflow aligns papers and knowledge sections, updates daily notes, and maintains a canonical literature canvas for traceable reviews.

Yes, the workflow requires specific YAML frontmatter fields. It relies on standardized frontmatter containing title, project, and updated fields to normalize literature notes, link knowledge sections, and update project memory accurately.

The best way to map research papers visually is by generating a Knowledge/Literature canvas. This workflow normalizes your imported papers and knowledge notes, then automatically produces a visual literature canvas to map relationships within your project memory.