"The literature is a conversation. Your job is to join it with evidence." — Paraphrasing common guidance from research-methods faculty
Duration: 6–8 hours · Difficulty: Intermediate · Prerequisites: Web search, basic academic writing, library VPN and Zotero (or similar) strongly suggested.
Learning Objectives
By the end of this module, you will be able to:
- Design a literature workflow: discovery → screening → extraction → synthesis → citation, with human checkpoints.
- Use Semantic Scholar, Connected Papers, OpenAlex, and assistants like Elicit without confusing retrieval with having read the paper.
- Apply PRISMA-style transparency (search strings, counts, exclusions) even outside medicine.
- Verify every bibliographic fact before it enters Zotero—ghost citations are routine LLM failures.
- Integrate citation managers with AI-assisted cleanup you still audit.
- Disclose AI steps where your syllabus requires it.
Concept 1: Why Workflows Matter When AI Is Fast
Generative models compress text quickly; scholarship is an argument on evidence. AI cannot close the access gap (paywalls), design judgment (confounds), or integrity (fabricated refs).
| Gap | Why AI alone fails |
|---|---|
| Access | Licensing and VPN decide what you may read |
| Lineage | Who argued what, in response to whom, is historical |
| Integrity | Hallucinated citations are your error if submitted |
Concept: Treat the model like a junior RA who never visits the stacks—you are the PI.
Comparison table: Discovery tools
| Tool | Good at | Limitation | Pair with |
|---|---|---|---|
| Semantic Scholar | Search, citation signals | Coverage gaps | Library resolver, OpenAlex |
| Connected Papers | Graph from a seed paper | Garbage in → garbage graph | 2–3 landmark reviews |
| OpenAlex | Open metadata | Incomplete vs all knowledge | DOI checks |
| Generic LLM | Synonyms, outlines | Invents refs | Strict verification |
Concept 2: Discovery vs Understanding
Discovery finds candidates; understanding requires reading. Responsible AI uses: synonym expansion, Boolean strings you run, table templates you fill, summaries of text you paste (policy permitting).
Workflow map
| Stage | Human core | Tools |
|---|---|---|
| Discovery | Sharpen RQ | Scholar, OpenAlex, databases |
| Screening | Inclusion rules | Spreadsheet, tags |
| Extraction | Methods, limits | Notes, tables |
| Synthesis | Your argument | Writing + bounded AI for outline |
| Citation hygiene | Accurate metadata | Zotero, Crossref |
Concept 3: Summarization and Integrity
Use structured prompts on text you have rights to paste; tag numeric claims [VERIFY IN PDF]. Never accept a bibliography from a model without Crossref/library checks.
Data and methodology
| Legitimate assist | High-risk |
|---|---|
| Draft survey items you pilot | Invented “results” |
| Inclusion criteria language | Fabricated statistics |
Concept 4: Writing workflow
You thesis + outline from your notes → AI rough expansion → you rewrite with real citations → reverse outline to catch “AI soup.”
Concept 5: PRISMA spirit and Zotero
Prespecify databases and dates; log queries; report screen-out reasons. Hallucination flavors: ghost papers, wrong DOI, merged citations, misquoted stats—delete or verify.
Fun Fact: Abstract-only pasting into cloud tools is often safer than full PDFs when policy is strict—still read the full text yourself for graded claims.
Try This! In Semantic Scholar or OpenAlex, run your own query for one paper title the model suggested—see how often reality matches memory.
Try This! Email a librarian with one saved Boolean string and ask which database field it should target.
Hands-On: Python — Fetch Metadata by DOI (Crossref)
Key Example: Calling Crossref is the fastest way to kill a suspicious reference before it pollutes your bibliography. Use a polite
User-Agentwith your email per Crossref etiquette.pip install requests.
[object Object], requests
HEADERS = {,[object Object],: ,[object Object],}
,[object Object], ,[object Object],(,[object Object],) -> ,[object Object],:
url = ,[object Object],
r = requests.get(url, headers=HEADERS, timeout=,[object Object],)
r.raise_for_status()
msg = r.json()[,[object Object],]
authors = [,[object Object],.strip()
,[object Object], a ,[object Object], msg.get(,[object Object],, [])]
,[object Object], {
,[object Object],: (msg.get(,[object Object],) ,[object Object], [,[object Object],])[,[object Object],],
,[object Object],: (msg.get(,[object Object],, {}).get(,[object Object],) ,[object Object], [[,[object Object],]])[,[object Object],][,[object Object],],
,[object Object],: authors,
,[object Object],: (msg.get(,[object Object],) ,[object Object], [,[object Object],])[,[object Object],],
}
,[object Object], __name__ == ,[object Object],:
,[object Object],(fetch_crossref(,[object Object],))Batch verification, OpenAlex search, and CSV loops follow the same pattern: polite headers, timeouts, small delays—describe those steps in words if you skip extra code.
Try This Now
- Synonym burst — AI suggests 15 terms; you dedupe and map to database fields.
- Abstract discipline — Compare AI summary to the abstract; mark added claims.
- Integrity rehearsal — Write your school’s AI policy in your own words in ~100 words.
Practice Exercises
Exercise 1 — Narrow a broad topic; pre-register what evidence would prove the question too big.
Exercise 2 — Seed paper + five neighbors; justify reading order.
Exercise 3 — Five LLM citations on a niche topic: verify each; classify misses (fabricated / merged / wrong year).
Exercise 4 — Three papers → extraction table with “threat to my claim” column.
Exercise 5 — Messy bibliography → clean export via verified metadata.
Mini-Project
Annotated bibliography + synthesis memo (1500–2000 words): 12–15 sources, ≥8 peer-reviewed; PRISMA-style paragraph; AI disclosure with verification steps.
Key Takeaways
- Discovery tools reduce friction; you own rigor and ethical access.
- Verify or delete references—hallucinations are common.
- AI helps structure after you know the field, not as a substitute for reading.
Key Takeaway
- Build workflows where every citation is opened (or accessible via library) before it ships.
- Pair Semantic Scholar / OpenAlex / Connected Papers with DOI verification, not blind trust.
- Use AI for synonyms, screening tables, and outlines—not for unchecked bibliographies.
- Disclose assistance and respect copyright and FERPA-like boundaries on uploads.
- PRISMA-style transparency makes your mini-reviews defensible to a skeptical grader.