[Scope] General reference-manager mode (PDF library, DOI/Zotero import, paper annotation) #132

Open
opened 2026-07-15 20:35:39 +00:00 by claude-bot · 0 comments
Contributor

Scope-expanding idea - PARKED, needs a product decision (Fable ideation) · Category: architecture/scope

Pitch
Add a literature-management layer: import papers by DOI or from Zotero, store PDFs, and annotate academic sources alongside media observations.

What it would add
A PDF store and viewer, DOI/Zotero import adapters, and a new "source = paper" entity distinct from the social/media provenance the import pipeline was built for.

Why it redefines scope
It moves the domain from media-theme observation to academic literature management - a different product with its own mature competitors (Zotero, Mendeley). The entry model, import pipeline, and AI enrichment are all shaped around short social/media observations, not long academic PDFs.

The honest case for
If her research increasingly cites academic sources, keeping them in the same graph as her media observations has real value, and the citation-export idea (pinned revisions / "cite this") is adjacent.

The honest case against (recommended default)
This is a domain pivot, not a feature. The lighter-weight adjacent wins - full-export round-trip (#120), citation blocks (pinned revisions issue), and additional import adapters (#121) - cover the realistic near-term need (get sources in, get citations out) without becoming a reference manager.

Decision needed

  • Is literature management actually part of this researcher's workflow, or an adjacent tool she already has?
  • If yes, is a lightweight "cite external source" entry type enough, short of a full PDF library?

From the 2026-07-15 codebase audit - Fable feature-ideation pass. Companion report: docs/.internal/report-2026-07-15.md (gitignored).

**Scope-expanding idea - PARKED, needs a product decision** (Fable ideation) · Category: architecture/scope **Pitch** Add a literature-management layer: import papers by DOI or from Zotero, store PDFs, and annotate academic sources alongside media observations. **What it would add** A PDF store and viewer, DOI/Zotero import adapters, and a new "source = paper" entity distinct from the social/media provenance the import pipeline was built for. **Why it redefines scope** It moves the domain from *media-theme observation* to *academic literature management* - a different product with its own mature competitors (Zotero, Mendeley). The entry model, import pipeline, and AI enrichment are all shaped around short social/media observations, not long academic PDFs. **The honest case for** If her research increasingly cites academic sources, keeping them in the same graph as her media observations has real value, and the citation-export idea (pinned revisions / "cite this") is adjacent. **The honest case against (recommended default)** This is a domain pivot, not a feature. The lighter-weight adjacent wins - **full-export round-trip (#120)**, **citation blocks (pinned revisions issue)**, and **additional import adapters (#121)** - cover the realistic near-term need (get sources in, get citations out) without becoming a reference manager. **Decision needed** - [ ] Is literature management actually part of this researcher's workflow, or an adjacent tool she already has? - [ ] If yes, is a lightweight "cite external source" entry type enough, short of a full PDF library? --- _From the 2026-07-15 codebase audit - Fable feature-ideation pass. Companion report: `docs/.internal/report-2026-07-15.md` (gitignored)._
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rbrooks/TeaLeaves#132
No description provided.