obsidian-literature-workflow

The workflow ingests Zotero metadata to generate literature notes within a bound Obsidian project. It automatically organizes the ingested papers into Papers/ and Knowledge/ directories using a filesystem-first approach.

Yes, you can generate a knowledge map for academic research papers in Obsidian. The workflow synthesizes literature into canvas maps by utilizing frontmatter fields like subfield and canvas_visibility to structure the visual relationships.

Yes, the Obsidian literature workflow requires a filesystem-first project structure bound to a memory registry at .claude/project-memory/registry.yaml. It expects literature notes to be organized under Papers/ and Knowledge/ directories with specific frontmatter fields.

The best way to synthesize academic research notes is to use an automated workflow that ingests Zotero metadata and updates daily notes with the synthesis results. This leverages a bound project memory registry to maintain a cohesive knowledge base.

You manage literature notes by storing papers in Obsidian and utilizing Zotero metadata for ingestion. The workflow automatically updates project memory and daily notes based on changes and synthesis results within the bound project.

Literature notes may not appear in the knowledge graph canvas if the frontmatter field canvas_visibility is not configured correctly. The workflow relies on specific frontmatter fields like subfield and canvas_visibility to generate and organize canvas maps.