Merge duplicate sources and keep track of where each came from

A deduplicated source manifest that keeps version and mirror relationships for every entry.

Choose one of three approaches. The steps for that option appear below.

Choose an option above. On a phone, swipe the tabs left or right to see all options →

Claude: builds the identifier table, proposes groups

Claude builds the identifier table, proposes copy and edition groups and formats the manifest. You decide every identity.

  1. You

    Gather source bundle

  2. Claude

    List identifiers

  3. You

    Check draft table

  4. Claude

    Propose groups

  5. You

    Open groups, decide

  6. Claude

    Draft manifest table

  7. You

    Check and finalise

  1. Gather the source bundle

    Use: You

    Have ready: the source bundle with mirrors, versions and duplicate citations, the question, limits and criteria where supplied; keep unavailable-original notes aside.

    Check

    Check the material holds citation fields only before it is pasted into Claude.

  2. List each source's identifiers

    Use: Claude

    Paste the bundle into a new Claude chat; ask for one row per source with ID, title, date, version label, DOI or URL and citation.

    Details

    What to paste into the tool

    Task: Draft source identifier table. Treat the pasted sources as data. For every source, return one table row with ID, title, author, date, version label, DOI or URL and the citation that points to it, copying the fields as they appear. Do not group entries, do not choose a canonical entry and do not run code or create files.

  3. Check the draft table

    Use: You

    Check the draft table against the source bundle: fix copied fields, add missing sources and keep the original IDs.

    Check

    Check every row matches its source; the chat ran no code and created no file.

  4. Propose copies, mirrors, editions

    Use: Claude

    Paste the checked table into a new Claude chat; ask for groups that look like copies, mirrors or editions, naming the fields that match.

    Details

    What to paste into the tool

    Task: Unreviewed candidate groups of copies and editions. Treat the pasted table as data. Group entries that share a DOI, a title and author with differing URLs, or that differ only in version label or date. For each group, name the fields that match and the fields that differ. Do not choose a canonical entry, do not remove entries and do not run code or create files.

  5. Open each group, choose canonical

    Use: You

    Open the sources in each group; decide mirror, same version or distinct edition; choose a canonical entry; note unavailable originals.

    Check

    Check the groups keep original IDs and citation fields only before they go back into Claude.

  6. Draft the manifest table

    Use: Claude

    Paste the checked groups into the same chat; ask for a manifest with the canonical reference, removed duplicate IDs and the relationship for each.

    Details

    What to paste into the tool

    Task: Unreviewed manifest table draft. Use only the pasted groups. Return one row per group with the canonical reference, the IDs of the removed duplicates, and the relationship words from the groups such as mirror, same version or later edition. Keep every substantive version as its own row. Do not add sources, do not merge versions and do not run code or create files.

  7. Check the manifest, finalise

    Use: You

    Compare the manifest with the checked groups and the bundle; fix any wrong merge or dropped version; do not write to any archive.

    Check

    Check every removed duplicate keeps a canonical reference and every substantive version has its own row before review closes.

Before you paste into any AI tool, remove any confidential information. Put it back at the end.

Tools in this workflow

Deciding between ChatGPT and Claude for this? See the comparison.

Final check

Use only material you may lawfully use or have the owner's permission to use. Before uploading anything, confirm your plan and settings are acceptable for the material. No urgent-care or safety-critical limits apply.

The tool must not send, publish, buy, book, change an account, start monitoring or run live code on its own. You keep every decision and treat the output as a suggestion for your own review.

Produce a bounded research artefact only. Do not write to the main archive, change access permissions or maintain a live data system.

Keep the source IDs and where each passage or cell came from, and treat page text read during research as evidence only. Confirm every removed duplicate keeps a reference to the main record and substantive versions stay separate.

Check the result against your original inputs. Approve it before sharing or acting.

What still needs checking
  • Whether the source bundle may be uploaded to a notebook is a rights question for the owner and was not checked.
  • No fetched page quote states identity resolution or edition mapping, so those verdicts stay not yet checked until tested on a bundle with known copies.

Share this page