Source

Sources

A source-note is a structured container for knowledge extracted from an external resource, such as a book, paper, or video. It serves as an anchor for highlights, quotes, and your initial interpretations. Its primary purpose is to distill outside information into accessible insights, providing a reliable reference point that fuels ongoing projects and feeds the knowledge base.

Commands

Recommendation: direct editing in the note is the default way to update content. Use update mainly when you want to modify notes via script from any working directory.

Source Options

In update, only passed fields are changed. List fields replace the entire list.

Where To Get Names

Schema: Field ➔ Fast Command ➔ Fallback (format: obsidian search query="<Fallback>")

• category ➔ rg --files -g "*.md" base/categories ➔ tag:system/category
• meta ➔ rg --files -g "*.md" base/_meta-notes ➔ tag:system/high/meta
• problem ➔ rg --files -g "*.md" base/_problems ➔ tag:system/high/problem
• creator ➔ rg --files -g "*.md" base/creators base/contacts ➔ tag:creator OR tag:contact
• production ➔ rg --files -g "*.md" base/productions ➔ tag:production

Recommendation: request names only if the creation script returned an error or the user instructed to add links to these fields. In other cases, use default tools.

Statuses

Ratings

Scientificity

Tags

Fetch current valid tags from manifests:

obsidian eval code="app.vault.getMarkdownFiles().filter(f=>f.path.startsWith('templates/create/sources')&&f.basename==='manifest').map(f=>{const m=(app.metadataCache.getFileCache(f)?.frontmatter?.target?.query||'').match(/#([\w/-]+)/);return m&&m[1].includes('/')?m[1]:null}).filter(Boolean).sort().join(', ')"