terraphim / terraphim/terraphim-ai

Obsidian format parser: aliases, wikilinks, and tags extraction

Aperta
#604 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

architecture enhancement
Lingua principale
Rust
Stelle
62
Fork
5
Merge medio
2h 27m
PR unite (30g)
1

Descrizione

Summary

Extend parse_markdown_directives_content() in terraphim_automata/src/markdown_directives.rs to parse Obsidian-native patterns alongside the existing Logseq synonyms:: syntax.

Current Parser

The parser handles 4 directives:

  • synonyms:: -> synonyms (Logseq property syntax)
  • type::: -> document type
  • route:: -> LLM routing config
  • priority:: -> priority score

New Patterns to Parse

1. YAML Frontmatter
---
aliases: [context management, semantic scope]
tags: [engineering, knowledge-graph]
---
  • aliases: -> treated as synonyms (same semantics as synonyms::)
  • tags: -> stored as concept categories (new field in MarkdownDirectives)
  • Supports both YAML list syntax ([a, b]) and multi-line (- a\n- b)
2. Wikilinks
Related to [[knowledge graph]] and [[ontology]] concepts.
  • Extract all [[target]] and [[target|display text]] patterns
  • Store as related concepts (new Vec<String> field in MarkdownDirectives)
  • These become edges in the rolegraph, not synonyms
3. Inline Tags
This concept is important for #engineering and #search.
  • Extract #tag patterns (excluding headings ## heading)
  • Store as categories alongside YAML frontmatter tags
  • Deduplicate with YAML tags

Parser Mode Configuration

Add a format field to haystack config:

[[roles.engineer.haystacks]]
location = "~/.config/terraphim/kg"
format = "terraphim"  # synonyms:: + type::: + route:: + priority:: (default)

[[roles.engineer.haystacks]]
location = "~/synced/pages"
format = "logseq"     # synonyms:: only

[[roles.engineer.haystacks]]
location = "~/synced/ObsidianVault"
format = "obsidian"   # aliases: + [[wikilinks]] + #tags + synonyms::

All formats output the same MarkdownDirectives struct. The obsidian format is a superset that also accepts synonyms:: (for Dataview users).

Extended Struct

pub struct MarkdownDirectives {
    pub doc_type: DocumentType,
    pub synonyms: Vec<String>,           // existing
    pub route: Option<RouteDirective>,    // existing
    pub priority: Option<u8>,            // existing
    pub categories: Vec<String>,         // NEW: from tags:/\#tag
    pub related_concepts: Vec<String>,   // NEW: from [[wikilinks]]
}

Test Plan

  • Fixture: real Obsidian vault files with YAML frontmatter, wikilinks, and tags
  • Test: aliases parsed as synonyms alongside existing synonyms:: support
  • Test: wikilinks extracted as related concepts
  • Test: tags extracted from both YAML frontmatter and inline #tags, deduplicated
  • Test: mixed format (file has both synonyms:: and aliases:) merges correctly
  • Test: obsidian format config flag routes to extended parser

Affected Crates

  • terraphim_automata (primary -- extend markdown_directives.rs)
  • terraphim_types (add categories + related_concepts to MarkdownDirectives)
  • terraphim_config (add format field to haystack config)

Estimated Effort

~4 hours

Part of

Epic #603

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Start by reading terraphim_automata/src/markdown_directives.rs and the MarkdownDirectives definition in terraphim_types, then inspect haystack configuration in terraphim_config. Use real Obsidian vault fixtures and add tests for frontmatter aliases and tags, wikilinks, inline tags, mixed syntax, and format routing. Done means all listed patterns merge into the shared struct and the obsidian configuration is accepted.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
rust
Ambito
backend
Tipo di issue
Funzionalità
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
42/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.