Run Zotero's duplicate detection, compare the paired items' DOIs, titles, and years, and merge only when the identifiers agree, keeping a record of the pre-merge item so a mis-merge can be reversed. Zotero identifies potential duplicate items and provides a merge interface that preserves collections and tags while combining item records.
- Open the duplicate view. Zotero groups the items it flags as potential duplicates into pairs for review. Treat each pair as a candidate, not a confirmed match.
- Compare the DOI first. A DOI name resolves through the Handle System to current information supplied for the identified object, commonly a landing page maintained by the registrant. If both records carry a DOI, check that the two strings match exactly. A DOI lookup through the Crossref REST API returns the metadata deposited for that DOI, which you can use to confirm the title and year attached to the identifier.
- Compare title and year. Confirm that the titles describe the same work and that the years are consistent. A matching title with a conflicting year or DOI is a signal to stop and verify before merging.
- Merge only when the identifiers agree. When the DOIs match and title and year are consistent, use the merge interface. Zotero preserves collections and tags while combining the records, so your organizational work carries into the merged item.
- Record the pre-merge state. Before merging, note which item you intend to keep and what the other record contained, so you can identify and reverse a mis-merge if the combined record turns out wrong.
If the identifiers disagree or one record lacks a DOI, leave the pair unmerged and resolve the question through the DOI landing page or the deposited metadata before deciding. A missing or mismatched field leaves the match unresolved; it does not by itself prove the records are different articles.