memex/notes/project-zotero-org-import-tool.org

PROJECT: Zotero Org Import Tool (Universal Literate Note)

• Overview
• Phase A: Demand (PRD)
  • 1. Purpose
  • 2. User Needs
  • 3. Success Criteria
    • Successful parsing of Zotero JSON export
    • Verification of direct PDF file links in Org headlines
    • Snapshot generation for at least one web bookmark
    • Automated :CREATED: property injection based on Zotero "Date Added"
• Phase B: Blueprint (PROTOCOL)
  • 1. Architectural Intent
  • 2. Semantic Interfaces
• Phase D: Build (Implementation)
• Phase E: Chaos (Verification)

Overview

The Zotero Org Import Tool is a "makeshift" utility designed to bridge the gap between academic research management (Zotero) and the personal knowledge base (Org-mode). It focuses on two critical priorities: accurate linking to academic PDFs and creating persistent web snapshots for bookmarks.

Phase A: Demand (PRD)

1. Purpose

Define the requirements for a high-fidelity import of research artifacts from Zotero to Org-mode.

2. User Needs

• BibTeX/JSON Parsing: Ingest Zotero libraries via standard export formats.
• Attachment Linking: Maintain durable links to local PDF attachments.
• Web Persistence: Generate local or service-based snapshots of imported URLs.
• Org-Native Schema: Map Zotero metadata fields to appropriate Org properties.

3. Success Criteria

TODO Successful parsing of Zotero JSON export

TODO Verification of direct PDF file links in Org headlines

TODO Snapshot generation for at least one web bookmark

TODO Automated :CREATED: property injection based on Zotero "Date Added"

Phase B: Blueprint (PROTOCOL)

1. Architectural Intent

Interfaces for data transformation and snapshot retrieval. Source of truth is the Zotero SQLite database/export and the local filesystem.

2. Semantic Interfaces

(defun zotero-import-library (export-path)
  "Parses the export and appends new entries to library.org.")

(defun zotero-resolve-attachment (zotero-key)
  "Locates the physical PDF associated with a Zotero record.")

Phase D: Build (Implementation)

Current implementation status is "Demand Phase." Placeholder for future Lisp/Python logic.

Phase E: Chaos (Verification)

Verification involves importing a test collection and ensuring all PDFs are openable and all web links have valid snapshots.