obsidian-literature-workflow

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Obsidian Literature Workflow

Obsidian文献工作流

Handle the literature sub-workflow inside the filesystem-first Obsidian project knowledge base.

处理以文件系统为优先的Obsidian项目知识库中的文献子工作流。

Role in the workflow

工作流中的角色

This is a supporting skill under

obsidian-project-memory

Use it when the user says things like:

“My papers are in Obsidian”
“Read papers from Zotero and create notes in the vault”
“Review the notes under
```
Papers/
```
”
“Generate literature knowledge notes from this project vault”
“Connect paper notes to project knowledge”
“Show me the literature structure as a map/graph”
“Check whether all papers already have detailed notes”

这是

obsidian-project-memory

下的辅助技能。

当用户提出如下需求时可使用该技能：

“我的论文都存在Obsidian里”
“从Zotero读取论文并在库中创建笔记”
“查看
```
Papers/
```
目录下的笔记”
“基于这个项目库生成文献知识笔记”
“将论文笔记和项目知识关联起来”
“以思维导图/关系图的形式展示文献结构”
“检查是否所有论文都有详细笔记”

Assumptions

前提假设

The project is already bound through

.claude/project-memory/registry.yaml

, or can be imported with

obsidian-project-bootstrap

Durable paper notes live under
```
Papers/
```
inside
```
Research/{project-slug}/
```
Obsidian note writing is done through the filesystem; no Obsidian MCP is required
Zotero may still be used as the source of metadata/full text; use
```
$zotero-obsidian-bridge
```
when the source corpus is in Zotero

项目已经通过

.claude/project-memory/registry.yaml

绑定，或可以通过

obsidian-project-bootstrap

导入

持久化的论文笔记存储在
```
Research/{project-slug}/
```
下的
```
Papers/
```
目录中
Obsidian笔记通过文件系统编写，无需使用Obsidian MCP
Zotero仍可作为元数据/全文的来源；如果源语料库在Zotero中，使用
```
$zotero-obsidian-bridge
```
处理

Default workflow

默认工作流

Read bound project memory and locate the vault root.
If the source papers are in Zotero, explicitly use
```
$zotero-obsidian-bridge
```
to pull them into canonical
```
Papers/*.md
```
notes.
Scan
```
Papers/
```
and adjacent synthesis notes using filesystem tools.

Normalize note metadata and structure using

$obsidian-markdown

Prefer the standardized review schema:

```
Claim
```
```
Method
```
```
Evidence
```
```
Limitation
```
```
Direct relevance to repo
```
```
Relation to other papers
```

Query narrowly first:
- read the relevant paper notes,
- then the linked
```
Knowledge/
```
  notes,
- and only then open
```
Writing/
```
  if the user asked for a review or comparison deliverable.
Prefer updating existing paper notes and literature synthesis notes over creating sibling notes.
Default literature synthesis should land in
```
Knowledge/
```
, not
```
Experiments/
```
or
```
Results/
```
:
- update
```
Knowledge/Literature-Overview.md
```
- update
```
Knowledge/Method-Families.md
```
- update
```
Knowledge/Research-Gaps.md
```
  when the synthesis is stable enough to deserve canonical notes.
If the source is a named collection and the user cares about completeness, maintain a collection inventory note with explicit coverage mapping.
Refresh
```
Maps/literature.canvas
```
after major paper-note changes or batch note creation.
- Prefer argument-map structure over dense all-to-all links.
- Prefer semantic filtering and edge thinning.
- Create
```
Maps/literature-main.canvas
```
  only when a lightweight presentation graph is needed.
Update the daily note and project memory with what changed.

读取绑定的项目内存，定位库根目录。
如果源论文存储在Zotero中，明确使用
```
$zotero-obsidian-bridge
```
将其拉取为规范的
```
Papers/*.md
```
笔记。
使用文件系统工具扫描
```
Papers/
```
目录及相邻的整合笔记。

使用

$obsidian-markdown

规范化笔记元数据和结构。

优先使用标准化的综述 schema：

```
Claim
```
```
Method
```
```
Evidence
```
```
Limitation
```
```
Direct relevance to repo
```
```
Relation to other papers
```

优先进行窄范围查询：
- 先读取相关的论文笔记，
- 再读取关联的
```
Knowledge/
```
  笔记，
- 仅当用户要求生成综述或对比交付物时才打开
```
Writing/
```
  目录。
优先更新现有论文笔记和文献整合笔记，而非创建同级笔记。
默认的文献整合内容应当存入
```
Knowledge/
```
目录，而非
```
Experiments/
```
或
```
Results/
```
：
- 更新
```
Knowledge/Literature-Overview.md
```
- 更新
```
Knowledge/Method-Families.md
```
- 更新
```
Knowledge/Research-Gaps.md
```
  当整合内容足够稳定，值得生成规范笔记时执行上述操作。
如果来源是指定集合且用户关心完整性，维护一份集合清单笔记，附带明确的覆盖范围映射。
在论文笔记发生重大变更或批量创建笔记后，刷新
```
Maps/literature.canvas
```
。
- 优先使用论点图结构，而非密集的全连接链路。
- 优先进行语义过滤和边精简。
- 仅当需要轻量化展示图谱时才创建
```
Maps/literature-main.canvas
```
  。
更新每日笔记和项目内存，记录变更内容。

Default outputs

默认输出

```
Papers/
```
remains first-class: one durable paper note per paper whenever possible
```
Knowledge/
```
holds durable literature synthesis notes
```
Maps/literature.canvas
```
is the default visual graph surface
literature work should usually produce at least one of:
- new or updated paper notes,
- new or updated knowledge notes,
- literature-canvas refresh,
- optional writing synthesis when requested

```
Papers/
```
始终为第一优先级：尽可能为每篇论文生成一份持久化的论文笔记
```
Knowledge/
```
存储持久化的文献整合笔记
```
Maps/literature.canvas
```
为默认的可视化图谱载体
文献工作通常至少应当产出以下成果之一：
- 新增或更新的论文笔记，
- 新增或更新的知识笔记，
- 文献画布刷新，
- 按需可选的写作整合内容

Default stance

默认原则

Do not assume by default:

```
Concepts/
```
```
Datasets/
```
```
.base
```
views

The literature workflow may create

Maps/literature.canvas

by default. Other artifacts still require explicit justification.

默认情况下不要假设存在：

```
Concepts/
```
```
Datasets/
```
```
.base
```
视图

文献工作流可以默认创建

Maps/literature.canvas

，其他产物仍需要明确的使用理由。

References

参考资料

Load only what is needed:

```
references/PAPER-NOTE-SCHEMA.md
```
- detailed paper-note frontmatter and sections

references/CANVAS-WORKFLOW.md

- how and when to refresh

Maps/literature.canvas

仅加载所需内容：

```
references/PAPER-NOTE-SCHEMA.md
```
- 详细的论文笔记前置元数据和章节说明

references/CANVAS-WORKFLOW.md

- 如何以及何时刷新

Maps/literature.canvas