zotero-slr-dedup-archived

Documents the retired supersede-based Zotero deduplication workflow and its remaining library artifacts.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/thurlow-research/ResearchClaudeCodeSkills --skill zotero-slr-dedup-archived-thurlow-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zotero-slr-dedup-archived
Source: https://github.com/thurlow-research/ResearchClaudeCodeSkills/tree/main/archive/zotero-slr-dedup-archived
Command: npx skills add https://github.com/thurlow-research/ResearchClaudeCodeSkills --skill zotero-slr-dedup-archived-thurlow-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It explains why a Zotero library contains legacy 04-Superseded collections and ~71 unmerged duplicate items left behind by a retired cross-source dedup workflow, so advisors, committee members, or future readers can interpret the historical state without re-running anything. ## Core Features & Use Cases - Historical record: Preserves the rationale, collection keys, venue hierarchy, and Bucket A/B model of the retired supersede-based dedup workflow for a systematic literature review. - Data defect documentation: Records the 04-Superseded vs 04-Superceded spelling split that hides 15 items from naive queries, with per-source counts and keys. - Migration mapping: Maps every old concept (manual 00-Dups registry, Jaccard title clustering, supersede writes) to the current zotero-merge-prep practice. - Use Case: A committee member asks why duplicates were never merged before July 2026; read this document to answer accurately instead of executing anything. ## Quick Start Ask the assistant to explain why the library contains 04-Superseded collections and how duplicates were handled before the merge-based workflow replaced them.

Frequently Asked Questions about zotero-slr-dedup-archived

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Zotero library have 04-Superseded collections?

A retired dedup workflow placed duplicate items into per-source 04-Superseded collections instead of merging them, keeping both records for PRISMA accountability. That workflow was retired on 2026-07-16 in favour of merge-with-type-normalization, leaving 71 item-memberships behind.

How do I resolve Zotero duplicates now instead of superseding them?

Use the zotero-merge-prep skill, which unions metadata and normalizes item types so Zotero's native Duplicate Items merge loses nothing. Run merge_prep.py scan on any collection key to find groups, then merge in the Zotero client.

Why does searching 04-Superseded miss some superseded items?

Five of eleven sources spell the collection 04-Superceded, and the old script matched names exactly, so 15 items across wos, cao, and ssrn are invisible to a single-spelling query. Count both spellings; do not rename the collections.

Does merging Zotero duplicates break PRISMA source counts?

No. Zotero's merge unions collection memberships, so the surviving record keeps every import collection and per-source counts stay invariant. The library already demonstrates this with a single record carrying acm, arxiv, and wos source memberships.

Can I still run the old dedup scripts from this archived skill?

No. All executable scripts were deleted at retirement, including apply_dedup.py whose writes contradict the merge philosophy. This directory is documentation only; use zotero-merge-prep for any actual duplicate resolution.