Local-first paper pipeline orchestrator between Zotero and Obsidian: detect, note, fetch PDF, queue AI analysis, index.
Project description
ZotVault
Local-first paper pipeline orchestrator between Zotero and Obsidian.
Works with just Zotero — add Obsidian and/or Ollama whenever you like and more switches on (see Requirements). ZotVault watches your Zotero library and, for every new paper, automatically: creates an Obsidian note, secures a PDF (open-access first, politely rate-limited), puts the paper on an AI-analysis queue, and keeps your vault's index current. Around that core loop it adds one-shot DOI/arXiv adding, paper search, a local dashboard, arXiv keyword alerts, an in-library citation graph, embedding-based related-paper suggestions, and synthesis-cluster proposals.
Everything runs on your machine. No cloud accounts required, no API keys required for the core loop, zero runtime dependencies (Python ≥ 3.9 standard library only).
[search] [collect] [archive] [wiki]
arXiv / S2 / Crossref ──▶ dashboard / CLI / agent ──▶ Zotero (BBT) ──▶ Obsidian vault
▲ │ you approve │ sqlite poll │
└── arXiv alert inbox ───┘ ▼ ▼
daemon: note → PDF (OA→proxy) → queue → index
+ citation graph · related · synthesis
Features
- One-shot add —
zotvault add 10.1103/PhysRevB.1.1 arXiv:2405.01234: metadata via Crossref/DataCite/arXiv → straight into Zotero through the same local channel the browser connector uses — including the OA PDF when one exists (Zotero downloads it itself, like the browser connector). Duplicates are detected before saving; a pipeline cycle runs immediately after the add. Optional translation-server support for arbitrary URL imports. - Automatic wiki-fication — new Zotero items become Obsidian notes (template-compatible, atomic writes). Existing notes are never rewritten; your manual sections are structurally safe.
- Edit-safe highlight sync — Zotero PDF highlights land in ONE marker-delimited block per note (grouped by color, deep links back to the exact annotation), kept in sync incl. deletions. Figure/area annotations are embedded as images (copied from Zotero's cache). Color groups can be renamed to your semantics (
label_red = "Core Claims"). Everything outside the block is untouchable; unmarked legacy notes are opt-in ([annotations] adopt_existing). See docs/MIGRATION.md. - PDF resolution, politely — Zotero attachment → cache → arXiv → Unpaywall → (opt-in) institutional proxy with browser-session cookies. Sequential, delayed, daily-capped: designed to not get your campus blocked. See docs/PROXY.md.
- AI-analysis queue — ZotVault doesn't run an LLM; it feeds yours.
zotvault queue --jsonlists unanalyzed papers with readable PDF paths; when your agent (e.g. Claude batch) writes*_analysis.md, completion is auto-detected. - Dashboard —
zotvault web→ http://127.0.0.1:8377 : search → tick → add, queue, alerts inbox, suggestions, audit trail. Localhost only. - arXiv alerts — daily keyword digest into a review inbox. Nothing enters Zotero without your click (propose, don't execute).
- Alert triage (assist) — optionally, a small local Ollama model scores inbox candidates 0–10 for relevance under a strict JSON contract (constrained decoding + validation + one retry); the dashboard sorts by score. Advisory only, off by default.
- Citation graph — Semantic Scholar citation counts + who-cites-whom within your library, regenerated into
Citation_Graph.md. - Related papers — local Ollama embeddings over your analysis notes →
Related_Suggestions.mdlink candidates. Free, offline. - Synthesis suggestions — clusters analyzed-but-unsynthesized papers into proposed review topics.
- Reconciliation, on your terms — deletions are detected on both sides but never acted on silently: a vault note you deleted is marked missing (dashboard: Recreate / Ignore), a paper deleted from Zotero shows up as vault-only (Re-add / Dismiss), and dismissed papers live on a reviewable ignore list that also guards
add. - Auditable — every automatic action lands in a SQLite trace (
zotvault trace).
Requirements — tiered
ZotVault works with just Zotero; every further tool you already use unlocks a layer.
| you have | you get |
|---|---|
| Zotero + Better BibTeX (required) | search across arXiv/S2/Crossref with in-library marks, one-shot add with OA PDF, arXiv alert inbox (approve → Zotero), proxy PDF fallback, dashboard, audit trace — Zotero-only mode |
+ a markdown folder (Obsidian vault or any directory — set [vault] dir) |
automatic per-paper notes, edit-safe highlight/figure sync, AI-analysis queue, citation graph / related / synthesis notes, index & log upkeep |
| + Ollama (optional, local & free) | related-paper suggestions (embeddings), alert triage scoring, local analysis engine |
Python ≥ 3.9; CLI is cross-platform (double-click app + launchd autostart are macOS today). Also optional: pdftotext (poppler) for full-text analysis, an institutional web proxy for licensed PDFs. Better BibTeX is genuinely required — it is the citekey source; without it items are marked blocked.
Quick start
pip install zotvault # or: pipx install zotvault / uv tool install zotvault
# (from source: git clone https://github.com/jbaek-dev/ZotVault && pip install ./ZotVault)
zotvault init # interactive setup: paths, email, vault scaffolding + doctor
# (--yes for the non-interactive template; add [alerts] keywords later if you want digests)
zotvault run-once --dry-run
zotvault run-once
Run it continuously. Two options on every platform:
- System tray (recommended):
pip install "zotvault[tray]"thenzotvault tray— daemon + tray icon with Open Dashboard / Run now / Pause / Quit. The only third-party packages ZotVault can use, and only if you opt in. - OS service:
zotvault install-daemon— macOS writes a launchd plist, Linux writes a systemd user unit, Windows prints the Task Scheduler command. Never auto-loads; it tells you the enable command.
macOS extra: double-click ZotVault.app (bash scripts/build_app.sh).
Every command also works without installing, via python3 -m zotvault.cli <cmd>.
Commands
| command | what it does |
|---|---|
init / doctor |
config file / environment health check |
run-once [--dry-run] / daemon |
one cycle / poll loop (+dashboard thread) |
install-daemon |
autostart: launchd plist (macOS) / systemd unit (Linux) / schtasks cmd (Windows) |
tray |
daemon + system-tray icon (needs pip install "zotvault[tray]") |
add <ids…> [--dry-run] |
resolve DOI/arXiv/URL → save to Zotero |
search <query> [--source arxiv|s2|crossref] |
search with in-library marks |
web |
dashboard server in the foreground |
queue [--json] |
papers awaiting AI analysis |
alerts [--fetch|--approve N|--dismiss N] |
arXiv digest inbox |
enrich [--limit N] |
citation graph + embeddings + suggestion notes |
assist [--limit N] |
score pending alerts with the small local model |
related <citekey> / synthesis [--write] |
similarity / cluster proposals |
status / trace [--limit N] |
state summary / audit trail |
Design guarantees
- Read-only toward Zotero's data. Library reads use a temp snapshot of
zotero.sqlite; adds go through Zotero's own connector endpoint (Zotero writes its DB itself). ZotVault never touchesstorage/; downloaded PDFs live in~/.zotvault/pdfs/. - Vault safety. Existing notes are never rewritten; auto-notes (
Citation_Graph.md,Related_Suggestions.md,_Synthesis_Suggestions.md) are clearly marked and ZotVault-owned; index.md is only patched via a strict counter regex; log.md is append-only;--dry-runpreviews; no delete code path exists. - Polite networking. OA-first, sequential fetches, delays, hard daily caps (separate, stricter cap for the proxy), honest User-Agent, backs off on HTTP 429.
- Nothing personal in code. All user-specific values live in
~/.zotvault/config.toml.
Agent integration
Any agent can drive ZotVault through the localhost API (/api/search, /api/add, /api/queue, /api/status). A ready-made tool module for the Polaris local agent (not yet public) lives in that repo (polaris/tools/zotvault_tools.py): search results show up with in-library marks, and adding requires the user to have explicitly picked papers.
Tests
python3 -m unittest discover -s tests -v # 101 tests, no network needed
License
MIT — see LICENSE. Changelog in CHANGELOG.md.
Project details
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file zotvault-0.9.4.tar.gz.
File metadata
- Download URL: zotvault-0.9.4.tar.gz
- Upload date:
- Size: 98.1 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
f262908da7f8aa2980fa91d99e012f96e8711290b25563c132166a85f9fc892a
|
|
| MD5 |
4cc33d2aae07fb4f11413884d9ee418e
|
|
| BLAKE2b-256 |
9a736884872b7b6ab42f5f0c217180c24738011dcfd97d9788644a785e2b2309
|
Provenance
The following attestation bundles were made for zotvault-0.9.4.tar.gz:
Publisher:
publish.yml on jbaek-dev/ZotVault
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
zotvault-0.9.4.tar.gz -
Subject digest:
f262908da7f8aa2980fa91d99e012f96e8711290b25563c132166a85f9fc892a - Sigstore transparency entry: 2135059355
- Sigstore integration time:
-
Permalink:
jbaek-dev/ZotVault@96f782528cec5526d3a80d304decddd9c436a686 -
Branch / Tag:
refs/tags/v0.9.4 - Owner: https://github.com/jbaek-dev
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish.yml@96f782528cec5526d3a80d304decddd9c436a686 -
Trigger Event:
release
-
Statement type:
File details
Details for the file zotvault-0.9.4-py3-none-any.whl.
File metadata
- Download URL: zotvault-0.9.4-py3-none-any.whl
- Upload date:
- Size: 89.6 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
bc5cfef2a0aa1c3589b810f88cbe11dd3cd8226e3a4332d6f1da20706f9d0bfd
|
|
| MD5 |
af95dc3d30997fbe7b72f4f3fd2c37f6
|
|
| BLAKE2b-256 |
ac1d0c15c6109e83a8a6f4ad9c72e99da788b54a8852c652b0503c96932dc1ef
|
Provenance
The following attestation bundles were made for zotvault-0.9.4-py3-none-any.whl:
Publisher:
publish.yml on jbaek-dev/ZotVault
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
zotvault-0.9.4-py3-none-any.whl -
Subject digest:
bc5cfef2a0aa1c3589b810f88cbe11dd3cd8226e3a4332d6f1da20706f9d0bfd - Sigstore transparency entry: 2135059472
- Sigstore integration time:
-
Permalink:
jbaek-dev/ZotVault@96f782528cec5526d3a80d304decddd9c436a686 -
Branch / Tag:
refs/tags/v0.9.4 - Owner: https://github.com/jbaek-dev
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish.yml@96f782528cec5526d3a80d304decddd9c436a686 -
Trigger Event:
release
-
Statement type: