How to Build a Teaching Resource Library with a Knowledge
How to build a teaching resource library with a knowledge system — a practical guide for teachers and educators to organize lesson materials, curate
Use-Case Workflows
How to organize a PhD literature base with a knowledge system — a practical guide for PhD students to structure their academic literature, connect papers
A PhD literature base grows over 4-7 years and may eventually contain 200-800 papers, depending on the field. Unlike a project literature review (which covers one focused topic for one deliverable), a PhD literature base:
The common approach — Zotero for citation management, a growing folder of PDFs, perhaps Obsidian or Notion for some notes — works at the beginning but breaks down as the library grows. Papers become unsearchable by concept; connections between papers in different sub-fields aren't captured; annotations written early in the PhD aren't connected to how those papers were later used.
A knowledge system designed for PhD literature management solves the organization problem for the full arc of doctoral research: from early broad reading through dissertation chapters to post-defense use.
A PhD literature knowledge system must serve four distinct purposes:
1. Literature review: Comprehensively mapping what's known in your research area. You need to find papers by topic, by theoretical approach, by methodology, by finding.
2. Argument building: Supporting specific claims in your papers and chapters. You need to find papers by what they argue and how they relate to your argument.
3. Citation management: Generating properly formatted references for your writing. Zotero or similar handles this — the knowledge system integrates with it.
4. Synthesis: Developing new understanding from the literature. The system needs to support seeing connections across papers, not just storing them individually.
The most effective PhD literature management uses two complementary tools:
Zotero: Primary academic citation manager. Captures citation metadata from databases (Google Scholar, PubMed, JSTOR, arXiv), stores PDFs, enables in-PDF annotation and highlighting, generates formatted citations and bibliographies for Word/Google Docs. Free for the core functionality.
WebSnips (or a note-based PKM like Obsidian): Captures web-based sources (preprints, blog posts, project websites, news coverage of research), stores concept-level notes and synthesis, enables connection-mapping across papers, and supports drafting from organized research.
The two tools connect: Zotero handles academic database sources; WebSnips handles web-based sources and concept-level synthesis; both export in compatible formats (BibTeX, RIS) that can be combined in a reference list.
Create a primary Collection: "PhD: [Research Area]" — e.g., "PhD: Computational Neuroscience" or "PhD: Urban Inequality"
Sub-Collections organized by research thread:
For your research area, create collections by:
Theoretical threads: The major theoretical frameworks or paradigms in your field:
Methodological threads: If methodology is a significant part of your work:
Empirical domains: The substantive areas your research touches:
Your own research:
Supporting:
By engagement level:
core-text — foundational; deeply read and annotated; frequently referencedkey-paper — important to your area; read carefully; cited in your workfamiliar — read, understand the contribution; may or may not citebackground — skimmed; know the argument; may or may not need to revisitto-read — in queue; not yet readBy theoretical/methodological position:
supports-my-approach — aligns with your frameworkalternative-approach — a different but credible way of approaching the problemcritical — critical of the dominant approach you use (important to know)foundational — work that the field builds on; establishes key conceptsBy use in your writing:
cited-in-ch1, cited-in-ch2, etc. — tracks where you've cited thisto-cite-ch2 — planning to cite in a chapter in progresssynthesis-candidate — strong candidate for synthesis discussionsThe annotation you write at capture time is what makes the literature useful years later when you've forgotten the details. For each paper, write:
Paper: [Author(s), Year, Title]
Zotero key: [Zotero citation key for cross-reference]
Core argument: [one sentence — what is this paper's central claim?]
Methodology: [what data, methods, or approach do they use?]
Key finding: [what do they conclude?]
Theoretical positioning: [what framework or tradition does this fit in?]
Contribution to my work: [specifically, why this paper matters for my research]
Thread(s): [which research thread(s) this belongs to]
Relates to: [2-3 other papers this connects to — agreement/disagreement/builds on]
Key quote(s): ["verbatim, with page number"]
Limitations (as noted by authors or known to me): [what this paper doesn't show]
Criticisms from others: [if there's significant critique of this work in the literature]
Where I've cited this: [chapter/paper if cited]
How my view has changed: [if I read this early and now see it differently]
The "how my view has changed" field matters for papers you read early in the PhD. A paper that seemed central in Year 1 may be marginal by Year 4, or vice versa. Noting when your assessment shifts maintains an honest record of your intellectual development.
Not every paper deserves the same depth of reading, and not every paper you read deserves a full annotation. Develop three reading modes:
Deep reading (for core and key papers, ~20-30 minutes + annotation time):
Standard reading (for papers in your domain, ~10-15 minutes + annotation):
Reconnaissance (for background papers and citation-chasing, ~3-5 minutes):
Citation chaining is the most efficient way to build a literature base quickly:
Capture each paper at discovery time, even before reading, so you don't lose track of what you've identified vs. what you've read.
Individual paper captures support understanding individual papers. Synthesis notes support understanding the field.
A synthesis note is a note you write (not about one paper, but about a topic or debate) that draws on multiple papers. Examples:
Synthesis note structure:
SYNTHESIS: [Topic]
Papers involved: [list with Zotero keys]
Last updated: [date]
THE STATE OF THE DEBATE:
[Narrative synthesis in your own words]
POSITION 1: [Representative claim]
Supporting papers: [list]
Key evidence: [summary of the evidence]
POSITION 2: [Alternative claim]
Supporting papers: [list]
Key evidence: [summary]
DISAGREEMENTS AND TENSIONS:
[What the papers don't agree on, and why]
GAPS AND OPEN QUESTIONS:
[What remains unknown]
MY POSITION:
[Where your own work fits in this debate]
Synthesis notes are the closest thing to writing your literature review. By the time you draft a chapter, each major synthesis note can become a section.
The Connections graph in WebSnips reveals relationships between captures that aren't visible in a linear list. For PhD literature:
Theoretical lineage: Connect each theoretical paper to the papers it builds on and the papers that build on it. This reveals the intellectual genealogy of your field.
Methodological clusters: Connect papers using the same or comparable methods. Useful for defending your own methodological choices ("following [Author A], [Author B], and [Author C] who all use this approach").
Argument chains: When Paper A responds to Paper B, or when Papers A, B, and C all argue against Paper D, the connections graph makes the structure of the debate visible.
Your work's position: Connect your own papers and chapters to the literature they engage with. When everything is connected, you can see your work's place in the field.
The scenario: A third-year PhD student in comparative politics is organizing her literature base on democratic backsliding. She has 180 papers in Zotero and has been using WebSnips for about 8 months.
Collections structure:
Annotation example (key paper):
V-Dem Institute Annual Report 2024 (web capture):
Core argument: Autocratization continues at accelerating pace in 2023; civil society restrictions now precede rather than follow electoral manipulation in most recent cases.
Contribution to my work: Directly supports my argument in Ch. 1 that civil society targeting is a leading rather than lagging indicator of democratic decline. The sequence matters for my causal argument.
Relates to: Connects to Lührmann & Lindberg (2019) who first identified this trend; updates their findings with 2023 data. Partially contradicts Levitsky & Ziblatt (2018) who emphasize electoral manipulation as the first indicator.
Key quote: "In 67% of cases since 2018, restrictions on civil society organizations preceded measurable deterioration of electoral integrity by 18-24 months." (p. 14)
Synthesis notes created:
Result: When writing Chapter 1, each section of the literature review was largely already written in the synthesis notes. Chapter drafting time was 40% faster than expected because the synthesis work had already been done.
A PhD literature base is one of the largest knowledge management projects a person undertakes — hundreds of papers accumulated over years, spanning multiple research threads, ranging from foundational classics to last week's preprint. A knowledge system that organizes by research thread, maintains annotations that capture significance (not just content), builds synthesis notes that accumulate toward the literature review, and connects papers to make debates and lineages visible transforms the literature base from an archive into a research tool. The students who exit their PhD with an organized, annotated, connected literature base have an asset that serves them in job talks, publications, and teaching for decades. The ones who don't spend their careers re-searching for papers they've already read.
Related reading: Best Web Clipper Extensions.
More WebSnips articles that pair well with this topic.
How to build a teaching resource library with a knowledge system — a practical guide for teachers and educators to organize lesson materials, curate
How to organize sources for a documentary with a knowledge system — a practical guide for documentary filmmakers and journalists to manage research
How to analyze customer feedback with a knowledge system — a practical guide for product managers to collect, organize, tag, synthesize, and act on
How to assemble evidence for due diligence with a knowledge system — a practical guide for investors and acquirers to organize research, document
How to build a competitive landscape map with a knowledge system — a practical guide for product managers and founders to research, organize, and maintain
How to build a course with a knowledge system — a practical guide to organizing research, developing curriculum, managing content assets, and creating