clippings-adapter

To ingest Obsidian Web Clipper markdown clippings, drop the files into the raw/clippings/ directory. The adapter processes them, uses the frontmatter niche tag to route entries to the corresponding knowledge base, and moves ingested files to an audit trail.

Niche routing works by reading the frontmatter niche tag from each clipping file. The adapter uses this tag to map and route the markdown entry into the matching <niche>.knowledge_items collection, ensuring clips are organized into the correct knowledge base.

Yes, you can deduplicate Obsidian clippings during ingestion. The adapter computes a content hash for each markdown file to identify and prevent duplicate entries from being routed into your knowledge base.

Yes, you need specific frontmatter fields to route Obsidian clippings. The adapter validates required fields within the markdown frontmatter, specifically relying on the niche tag to successfully map entries into the corresponding <niche>.knowledge_items schema.

The best way to maintain an audit trail for ingested markdown clippings is to let the adapter move successfully processed files from raw/clippings/ into a dedicated audit trail directory, preserving traceability and compliance for every routed knowledge base entry.

Yes, the clippings adapter works with a custom knowledge base schema. It normalizes frontmatter and emits standard knowledge-base fields according to your project's schema when routing Obsidian clippings into the <niche>.knowledge_items structure.