ea-connected-vault-setup

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

EA Connected Vault Setup

Create a light navigation layer, not a new taxonomy or a content rewrite. Preserve every note's text, existing properties, filenames, folders, templates, query blocks, and links unless the requested linking requires a small additive edit.

创建轻量导航层，而非新的分类体系或内容重写。保留所有笔记的原文、现有属性、文件名、文件夹、模板、查询块和链接，除非所需的链接操作需要进行少量补充性编辑。

Scope and safety

范围与安全原则

Work only on the user-designated corpus. Exclude configuration, templates, attachments, generated/cache folders, daily logs, and existing database/query files unless the user includes them.
Search filenames, aliases, frontmatter keys, links, and existing root/MOC notes before creating anything. Reuse a clearly matching root rather than duplicating it.
Use the exact, capitalized property names
```
Parents
```
and
```
Related
```
. Both are YAML/Markdown lists of wikilinks, even when they initially contain one item. Do not replace populated values; merge without changing their existing representation or casing.
In this initial setup, give each child exactly one
```
Parents
```
entry: its cluster root. Do not introduce multiple root assignments.
Do not infer a topical relationship from name similarity alone. Leave uncertain notes in a deliberately named holding root (for example,
```
Unsorted concepts
```
) and flag them.
This operation changes many files. First produce an inventory and proposed clustering; obtain confirmation before writing. After approval, apply only additive, minimal diffs and report every created/changed file.

仅处理用户指定的笔记集合。排除配置文件、模板、附件、生成/缓存文件夹、每日日志以及现有数据库/查询文件，除非用户明确包含这些内容。
创建任何内容前，先搜索文件名、别名、frontmatter 键、链接以及现有的根笔记/MOC 笔记。若存在明确匹配的根笔记，直接复用，避免重复创建。
使用精确的大写属性名
```
Parents
```
和
```
Related
```
。两者均为 YAML/Markdown 格式的 wikilink 列表，即使初始仅包含一个条目也需保持列表格式。不得替换已填充的属性值；合并时不得更改其原有格式或大小写。
在本次初始设置中，每个子笔记仅对应一个
```
Parents
```
条目：即其所属的聚类根笔记。不得为子笔记分配多个根节点。
不得仅根据名称相似性推断主题关联。将无法确定分类的笔记放入专门命名的暂存根笔记中（例如
```
Unsorted concepts
```
），并进行标记。
本操作会修改大量文件。请先生成文件清单和聚类方案，获得用户确认后再执行写入操作。获批后，仅进行补充性的最小差异修改，并上报所有创建/修改的文件。

1. Inventory and cluster proposal

1. 文件清点与聚类方案

Read each in-scope Markdown note's title, aliases, frontmatter, headings, outbound links, and enough body text to establish its subject. Read linked context when it resolves ambiguity.
Exclude the future root notes from the child count. Identify existing hubs, broad concepts, and duplicate/near-duplicate titles.
Propose topic clusters that are semantically coherent and navigable:
- Target 5–10 roots for a substantial collection.
- Target roughly 8–15 child notes per root. Use fewer roots for a small corpus; split an oversized coherent cluster only when it has a meaningful internal division.
- Give each root a specific, durable, plural-friendly name (for example,
```
Plant functional traits
```
  , not
```
Miscellaneous
```
  ).
- Assign every in-scope note exactly one proposed root, with a one-line reason for ambiguous assignments.
Present the proposal as a compact table: root name, intended scope, child count, and any uncertain notes. Do not write yet.

读取每篇范围内 Markdown 笔记的标题、别名、frontmatter、标题层级、出站链接，以及足够判断主题的正文内容。若存在歧义，可读取链接的上下文内容辅助判断。
子笔记计数不包含后续将创建的根笔记。识别现有的枢纽笔记、宽泛概念以及重复/近似重复的标题。
提出语义连贯、便于导航的主题聚类方案：
- 对于规模较大的笔记集合，目标设置5-10个根笔记。
- 每个根笔记下大致对应8-15个子笔记。小规模笔记集合可设置更少的根节点；仅当某个过大的连贯聚类存在明确的内部分界时，才对其进行拆分。
- 每个根笔记的名称需具体、稳定、适合复数形式（例如
```
Plant functional traits
```
  ，而非
```
Miscellaneous
```
  ）。
- 为每篇范围内的笔记分配唯一的拟议根节点，对于存在歧义的分配，需附上一行说明理由。
以简洁表格形式呈现方案，包含：根笔记名称、预期范围、子笔记数量、所有不确定的笔记。暂不执行写入操作。

2. Create roots and the child Base

2. 创建根笔记与子笔记 Base

After approval:

Create the shared Base at
```
__Support/Bases/Children by Parents.base
```
unless the user specifies another support location. Copy the bundled [
```
assets/Children by Parents.base
```
](assets/Children by Parents.base) verbatim.
Create a
```
Roots/
```
folder at the vault root if it does not already exist. Create every new root note in
```
Roots/
```
, using that vault's root/topic template when one exists. If there is no template, use this minimal structure:
md
```
---
---

# Root name

> [!note] AI-generated
> Created by EA Connected Vault Setup as a navigation root. Review the cluster boundary before treating it as a settled taxonomy.

![[__Support/Bases/Children by Parents.base]]
```
Keep the embed directly below the title/provenance. The Base resolves
```
this
```
to the root that embeds it, so the same file lists the correct children in every root. Its table displays the child Note first, followed by its Related list.
If a reused root already exists outside
```
Roots/
```
, leave it in place; do not rename or move it. Add the Base embed only if it has no equivalent child listing, and do not overwrite or rearrange its content.

The Base contents are:

yaml

filters: 'Parents.contains(this.file)'
properties:
  file.name:
    displayName: Note
  Parents:
    displayName: Parents
  Related:
    displayName: Related
views:
  - type: table
    name: Children
    order:
      - file.name
      - Related

获得批准后：

除非用户指定其他支持文件路径，否则在
```
__Support/Bases/Children by Parents.base
```
路径下创建共享 Base。原样复制随附的[
```
assets/Children by Parents.base
```
](assets/Children by Parents.base)文件。
若笔记库根目录下不存在
```
Roots/
```
文件夹，则创建该文件夹。所有新的根笔记均创建在
```
Roots/
```
目录下，若笔记库存在根笔记/主题模板，则使用该模板。若无模板，则使用以下最小结构：
md
```
---
---

# Root name

> [!note] AI-generated
> Created by EA Connected Vault Setup as a navigation root. Review the cluster boundary before treating it as a settled taxonomy.

![[__Support/Bases/Children by Parents.base]]
```
请将嵌入内容直接放在标题/来源说明下方。Base 会将
```
this
```
解析为嵌入它的根笔记，因此同一个文件可以在每个根笔记中列出正确的子笔记。其表格会先显示子笔记的Note列，随后是对应的Related列表。
若复用的根笔记已存在于
```
Roots/
```
目录之外，保持其原有位置不变，不得重命名或移动。仅当该笔记没有等效的子笔记列表时，才添加 Base 嵌入内容，且不得覆盖或重新排列其原有内容。

Base 文件内容如下：

yaml

filters: 'Parents.contains(this.file)'
properties:
  file.name:
    displayName: Note
  Parents:
    displayName: Parents
  Related:
    displayName: Related
views:
  - type: table
    name: Children
    order:
      - file.name
      - Related

3. Assign each child

3. 分配每个子笔记的父节点

For every approved in-scope, non-root note:

Add this list to the existing YAML frontmatter. Preserve ordering and formatting otherwise:
yaml
```
Parents:
  - "[[Root name]]"
```
If the note lacks YAML frontmatter, add a minimal block containing this
```
Parents
```
list.
Do not change an existing non-empty
```
Parents
```
list without flagging it in the review report. If it clearly points to an obsolete equivalent, ask before replacing it.
Verify every
```
Parents
```
target resolves to a root note and every root Base has at least one expected child.

对所有获批的范围内非根笔记执行以下操作：

将以下列表添加到现有的 YAML frontmatter 中。除此之外，保留原有顺序和格式不变：
yaml
```
Parents:
  - "[[Root name]]"
```
若笔记没有 YAML frontmatter，则添加一个包含该
```
Parents
```
列表的最小前置块。
不得修改已存在的非空
```
Parents
```
列表，除非在审查报告中进行标记。若该列表明确指向一个已废弃的等效根笔记，需先询问用户再进行替换。
验证每个
```
Parents
```
目标都能解析到一个根笔记，且每个根笔记的 Base 至少包含一个预期的子笔记。

4. Make each note alive with discourse-advancing body links

4. 添加推进论述的正文链接，提升笔记关联性

Make a separate pass after parent assignment. A frontmatter list is only a navigation aid: it must not be the sole connection between notes. Review every substantive paragraph rather than aiming for a quota.

For each candidate target, read the target note and score the prospective link. Add it only when its overall case is strong; the purpose is to deepen the note's line of thought, not to make its graph denser.

Criterion	0 points	1 point	2 points
1. Available target	No suitable existing note.	A broadly adjacent note exists.	A specific existing note directly covers the concept, mechanism, method, evidence, or implication.
2. Contribution to discourse	Merely interesting, decorative, or navigational.	Helpful context.	Advances the paragraph's reasoning: it defines a premise, supplies a mechanism, qualifies a claim, provides evidence, or opens a necessary next question.
3. Existing treatment	The target is already linked nearby and another link adds no value.	Mentioned/linked elsewhere in the note, but this paragraph needs a local entry point.	Not already linked in the relevant context, or a deliberate repeated link materially improves navigation.
4. Minimal integration	Requires new claims or rewriting.	Requires a short contextual line below the paragraph.	Can be integrated by linking an existing phrase or making only a word-level edit.
5. Semantic precision	The relationship is ambiguous or misleading.	Plausible but indirect.	The link label and target accurately express the exact relationship implied by the paragraph.
6. Reader utility	The reader gains little by opening it.	Useful background.	Opening the target is likely to resolve a real conceptual, methodological, or evidential need created by this paragraph.

Add inline links for candidates scoring 9–12, and normally reject candidates scoring 0–6. Treat 7–8 as editorial judgment: retain only when the link clearly improves the reader's path through the argument.
Prefer direct inline links. Convert a natural, unlinked mention to
```
[[Canonical note title|visible phrase]]
```
. Make only the smallest word-level edit necessary for a grammatical, precise anchor; never alter a source claim or manufacture a sentence.
When a candidate clears the threshold but lacks a natural anchor, add a compact contextual line immediately below the relevant existing paragraph, for example:
md
```
*Related: [[Concept A]] and [[Concept B]].*
```
This line must qualify or extend that paragraph without adding an unverified claim. Do not append detached link dumps or use these lines to satisfy a quota.
Add or merge the strongest body-level connections into a capitalized
```
Related
```
list in frontmatter. There is no fixed length: include only the compact set of links that remains useful as navigation.
```
Related
```
supplements body links rather than replacing them:
yaml
```
Related:
  - "[[Concept A]]"
  - "[[Concept B]]"
```
Preserve existing links and
```
Related
```
values. A second contextual link to the same note is valid only when it gives a later paragraph its own needed entry point. If no candidate clears the threshold, add none and list the note for human review.

父节点分配完成后，单独执行一轮链接添加操作。frontmatter 中的列表仅作为导航辅助，绝不能成为笔记之间的唯一关联。需逐段审查所有实质性段落，而非追求链接数量指标。

对于每个候选链接目标，先阅读目标笔记，再为该候选链接打分。仅当整体合理性较高时才添加链接；目的是深化笔记的思路脉络，而非增加知识图谱的密度。

评分标准	0分	1分	2分
1. 目标可用性	无合适的现有笔记。	存在主题大致相关的笔记。	存在专门的现有笔记，直接涵盖该概念、机制、方法、证据或影响。
2. 论述贡献度	仅具有趣味性、装饰性或导航作用。	可提供有用的上下文。	能够推进段落的论证：定义前提、提供机制、限定主张、补充证据，或引出必要的后续问题。
3. 现有链接情况	目标已在附近段落链接，再次添加无价值。	笔记的其他位置提及/链接过该目标，但本段落需要一个本地入口。	相关上下文中尚未链接，或刻意重复的链接能显著提升导航体验。
4. 整合成本	需要添加新论断或重写内容。	需要在段落后添加一行简短的上下文说明。	可通过链接现有短语或仅进行单词级编辑实现整合。
5. 语义精准度	关联关系模糊或具有误导性。	合理但间接。	链接文本和目标能准确表达段落所隐含的确切关系。
6. 读者价值	读者打开链接几乎没有收获。	可提供有用的背景信息。	打开目标链接很可能解决本段引发的实际概念、方法或证据层面的疑问。

得分9-12的候选链接可添加为内联链接，得分0-6的通常予以拒绝。7-8分的链接需进行编辑判断：仅当链接能明显优化读者的论证阅读路径时才保留。
优先使用直接内联链接。将自然的未链接提及转换为
```
[[Canonical note title|visible phrase]]
```
格式。仅进行必要的最小单词级编辑，以确保锚文本语法正确、表述精准；绝不得修改原始论断或编造句子。
若候选链接达到阈值但缺少自然的锚文本，可在相关段落的正下方添加一行简洁的上下文说明，例如：
md
```
*Related: [[Concept A]] and [[Concept B]].*
```
该行内容必须是对该段落的补充或延伸，不得添加未经证实的论断。不得附加零散的链接堆砌，也不得为了凑数而添加这些行。
将正文中最强的关联链接添加或合并到 frontmatter 中大写的
```
Related
```
列表里。该列表无固定长度：仅包含作为导航仍有价值的精简链接集合。
```
Related
```
是正文链接的补充，而非替代：
yaml
```
Related:
  - "[[Concept A]]"
  - "[[Concept B]]"
```
保留现有链接和
```
Related
```
值。仅当同一笔记的第二个上下文链接能为后续段落提供所需的独立入口时，才是合理的。若没有候选链接达到阈值，则不添加任何链接，并将该笔记标记为需人工审核。

5. Validate and report

5. 验证与报告

Confirm that each child has exactly one resolving
```
Parents
```
entry.
Confirm that every Base file is valid YAML and its filter is exactly
```
Parents.contains(this.file)
```
.
Check that every substantive paragraph was considered against the link score, that each added link meets the discourse/precision threshold, and that
```
Related
```
only supports rather than substitutes for those links.
Check for broken wikilinks introduced by this setup and for accidental links to the Base/template itself.
Report:
```
Roots/
```
folder created/reused, roots created/reused, Base location, number of children assigned, number of inline/contextual links and
```
Related
```
lists added, uncertain notes, and anything intentionally untouched.
Clearly label the root notes as AI-created; do not add AI-generated prose to existing notes beyond the requested structural properties and links.

确认每个子笔记仅有一个可正常解析的
```
Parents
```
条目。
确认每个 Base 文件都是有效的 YAML 格式，且其过滤器精确为
```
Parents.contains(this.file)
```
。
检查所有实质性段落都经过了链接评分考量，每个添加的链接都符合论述/精准度阈值，且
```
Related
```
仅作为这些链接的补充而非替代。
检查本次设置是否引入了失效的 wikilink，以及是否意外链接到了 Base/模板本身。
报告内容包括：创建/复用的
```
Roots/
```
文件夹、创建/复用的根笔记、Base 路径、分配的子笔记数量、添加的内联/上下文链接数量和
```
Related
```
列表数量、不确定的笔记，以及所有刻意未修改的内容。
明确标记根笔记为 AI 生成；除了要求的结构属性和链接外，不得向现有笔记添加 AI 生成的正文内容。