Zotero 101 - Part 1: basics
Based on Obsidian Community Talks's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Use Zotero to connect every idea to its source so attribution, error-checking, and “where this came from” tracing stay possible as your library grows.
Briefing
Zotero’s real value isn’t just storing PDFs—it’s building a traceable, searchable citation system that keeps ideas tied to their sources and formats references automatically for whatever writing workflow comes next. The session frames reference management as an ethics-and-accuracy tool: citations let people attribute properly, reconstruct how an idea evolved, and detect whether an error came from a misunderstanding of the original author or from a mistake in the source itself.
After a quick live poll using Slido, the talk pivots from “why bother” to “what you can do immediately.” Starting from a clean Zotero library, the walkthrough demonstrates how Zotero can generate citations and bibliographies in different citation styles (with examples like Chicago and IEEE). It also shows the practical friction that reference managers remove: instead of manually numbering and reordering references, Zotero can keep citation order consistent as new sources are added. The session then extends beyond plain Markdown note-taking by showing how Zotero integrates with document production tools.
For writing in LaTeX, Zotero can produce a bibliography that LaTeX uses to generate properly ordered references and even flag missing citations with a question mark when something hasn’t been added to the library. For Word, the workflow can use an installed plugin to insert citations and automatically build the bibliography in the correct style. The talk also highlights a command-line route using Pandoc: citations can be processed into a final PDF output, and changing citation style becomes a matter of adjusting a single argument rather than reformatting everything by hand.
A key decision point is why choose Zotero over other reference managers. The session emphasizes Zotero’s open-source ecosystem—especially the ability to write plugins and build integrations with Obsidian. It also notes built-in OCR support, which improves search across the contents of PDFs, not just their metadata.
The second half shifts into Zotero’s “lingo” and data model: Zotero items (with fields like author, title, abstract, and item type), collections for organizing those items, and notes stored inside Zotero (rendered with an HTML-style editor rather than native Markdown). It recommends adding your own tags instead of relying on automatically scraped keywords, and it demonstrates multi-collection membership (an item can belong to multiple collections, similar to tags).
Finally, the walkthrough addresses how PDFs get into Zotero (via a browser connector like the Zotero Connector/Clipper, open-access sources, or metadata extraction that depends on whether sites expose parseable information). It also covers where Zotero stores data on disk—inside a database with a “data directory”—and why managing that location matters for backups and long-term organization. The session ends by installing Obsidian-focused plugins (via .xpi files) and taking Q&A about syncing, proxy limitations for paywalled sources, and how Zotero can extract metadata from different web pages (including IMDb and likely YouTube via available translators).
Cornell Notes
Zotero is positioned as a system for more than file storage: it ties every claim and note to a source so ideas can be traced, corrected, and properly attributed. The talk highlights three practical benefits—unique IDs for reliable searching, database-driven indexing, and citation/bibliography automation that keeps formatting consistent across styles. It demonstrates workflows that generate formatted outputs for LaTeX, Word, and Pandoc (including style changes via a single setting). It then explains Zotero’s core concepts (items, collections, fields, and Zotero notes) and how PDFs and metadata enter the library through connectors, open-access sources, or manual attachment. The payoff is a scalable workflow that reduces manual citation errors as the number of sources grows.
Why does the talk treat citations as more than a publishing requirement?
What three capabilities make reference managers worth using even for personal notes?
How does Zotero reduce the “manual citation” workload in practice?
What does Zotero integration look like outside Markdown-only workflows?
How are Zotero’s core objects organized—items, collections, and notes?
Why do PDF and metadata imports sometimes fail?
Review Questions
- What traceability problems arise when notes are kept without a reference manager, and how do citations help solve them?
- Compare how Zotero handles citation formatting in LaTeX versus Pandoc versus Word.
- What are the differences between Zotero items, collections, and Zotero notes, and why does item type matter?
Key Points
- 1
Use Zotero to connect every idea to its source so attribution, error-checking, and “where this came from” tracing stay possible as your library grows.
- 2
Reference managers add value through unique IDs, fast database search/indexing, and automated citation/bibliography formatting in required styles (e.g., IEEE).
- 3
Citation automation prevents manual renumbering and reordering when new sources are added, reducing formatting mistakes.
- 4
Zotero can feed multiple writing workflows: LaTeX, Word (via plugin), and Pandoc (via command-line processing), with style changes handled by configuration rather than rewriting citations.
- 5
Zotero’s core structure is items (with fields and item types), collections (including multi-collection membership), and item-linked notes (HTML-style editor in this setup).
- 6
PDF/metadata capture depends on site accessibility and parseable metadata; paywalled sources may require different approaches or may not be extractable by the connector.
- 7
Zotero stores data in a local database and a data directory; managing that location and syncing strategy matters for backups and storage limits.