Hand off a citation library without handing over a puzzle

Choose collaboration, transfer, or snapshot

“Send the Zotero library” can mean three different jobs. Ongoing collaboration calls for a group library. Moving one person’s complete working library to another computer calls for sync or a data-directory transfer. A bounded project handoff may call for an export plus a human-readable manifest. Pick the job first because the formats do not preserve the same things.

Zotero’s export guidance says Zotero RDF with files and notes is the most complete export for another Zotero user, but also warns that export is not a proper backup or a replacement for collaboration. Reimport can change dates, break links to existing word-processor citations, and lose fields depending on format. That makes an export a snapshot, not an invisible continuation of the sender’s library.

Resolve attachment behavior before packaging

Open the collection and inspect attachment types. Zotero’s file documentation distinguishes stored files, which Zotero manages and can sync, from linked files, which point to a path on one computer. Linked files are not synced and cannot be used in group libraries. A metadata export can therefore look complete while the receiver gets broken attachment links.

For each item used in the project, require a parent bibliographic record and label the attachment state: stored and present, linked and converted, web-only, intentionally omitted, or unavailable. Avoid a pile of standalone PDFs with no title, author, or publication metadata. If permissions prevent sharing a file, retain the citation and add a note explaining how an authorized teammate can retrieve it; do not smuggle the attachment into the package.

Make a small manifest for humans

The receiver should not need to reverse-engineer collection names. Include a short README beside the export with the question the library served, inclusion boundary, last review date, key tags, and known gaps. Add a table that can be read without Zotero.

Keep status tags few and defined. Zotero collections behave more like playlists than folders, and items can appear in multiple collections. That flexibility is useful to the sender but can make a copied hierarchy misleading. If a tag drives workflow, explain it in the README. The related evidence-table guide can hold the claim-level decisions that a citation manager is not designed to express.

Test the handoff from the receiver’s side

Use a fresh profile, separate account, or teammate’s device. Ask the receiver to locate one key source, open its attachment, identify why it was included, and generate one citation in the target style. For an ongoing team library, verify the receiver’s role in the group settings. Zotero’s group documentation separates library reading, library editing, and file editing permissions; grant only what the work requires.

A hypothetical handoff might include 42 records, but the count proves little. The meaningful acceptance check is that the teammate can answer: What is in scope? Which files are missing? Which sources were actually used? Where are unresolved disagreements recorded? No invented completeness percentage is needed.

1. State whether this is collaboration, full transfer, or a frozen snapshot.
2. Convert or explain linked attachments before sharing.
3. Export the bounded collection with notes and files where permitted.
4. Add a plain-language manifest and tag legend.
5. Have the receiver retrieve, open, understand, and cite a sample item.

For long-term portability, compare this process with the archive’s cross-app search record: search can locate material, but a durable handoff still needs explicit ownership and understandable structure.