Reference managers and collaboration: choose the record you need to preserve

1. Separate the publication record from the files and notes

A citation record identifies a publication. An attachment holds a file; a note records interpretation; a screening decision explains eligibility. Keep those roles explicit even when one application stores them together. A downloaded PDF may belong to a different version from the selected citation, and a polished reference can still contain a wrong author, year or identifier.

For each imported batch, preserve its source, search or export date and a local batch label. Check important fields against the publication itself. Retain the original-language title where appropriate and distinguish a supplied translation from the published title. Do not create a new publication merely because an Arabic rendering differs from the English text.

On small screens, scroll the table horizontally, or focus it and use the arrow keys.

2. Check the exact scope of “sharing”

Zotero group libraries are separate from personal libraries. Copying a record between them does not keep the two copies continuously linked. Its group types also differ: public open groups do not support file sharing. Select the membership and editing settings that fit the project, then confirm what an invited user can actually see.

EndNote’s 2025 documentation distinguishes sharing an entire library, including attachments and annotations, from sharing selected groups. Its group-sharing documentation says attachments are not shared through that route. This is a concrete reason to ask what a collaborator receives rather than accept “collaboration supported” as a complete answer.

These are documented distinctions, not findings from a comparative trial. Check the installed version, account and intended access route before making a decision. Record rights to share full texts independently from the software’s ability to transfer them.

Reference: Zotero: groups, permissions and library ownership · EndNote 2025 documentation: shared libraries · EndNote 2025 documentation: sharing selected groups

3. Reconcile duplicates without erasing related publications

Treat duplicate detection as a shortlist for examination. Compare publication type, authors, title, date, identifier and the source document. Two records may describe one article, or two reports from one study. Those are different problems: record deduplication should not silently remove a conference abstract, correction or later full report that needs a separate relationship.

Zotero documents detection within a library and recommends merging confirmed duplicates rather than deleting one copy; merging preserves links used by its word processor integration. Choose the correct conflicting fields before the merge. A matching suggestion is not evidence that the underlying publications are identical.

• Keep a short reconciliation note for consequential or uncertain changes.
• Preserve distinct correction and retraction notices as identifiable records and check the article’s current status.
• Leave an unresolved candidate separate until a person checks the source; do not reward a smaller library count.

Reference: Zotero: duplicate detection and merging

4. Worked example: five records are not five independent studies

The following records and checks are invented for training. No real article, identifier or study result is being reported. A team reviews five imported records. In this example the reviewer has inspected the source documents for R01–R04; the source needed to resolve R05 is unavailable.

On small screens, scroll the table horizontally, or focus it and use the arrow keys.

5. Test the connection to the manuscript

Zotero documents dynamic citations and bibliographies in supported word processors, including Word, LibreOffice and Google Docs. That capability helps update bibliographic presentation; it does not establish that a sentence is supported by the cited paper. Keep the source-to-claim check as a separate author responsibility.

Rehearse a small manuscript with the team’s actual software combination. Have one collaborator insert a citation, another update a checked field, and a third open the received file. Record whether the intended record and formatting survive. Include Arabic names, an institutional author and a source with an article number if they represent the team’s work.

Preserve an editable master before preparing any static submission copy. Do not remove citation fields from the working manuscript as a routine cleanup step. Follow the destination’s instructions for its required file while retaining the team’s version that can still be revised.

Reference: Zotero: word processor integration

6. Distinguish syncing, interchange and recovery

Zotero distinguishes data synchronization from attachment synchronization. A record appearing on a second device does not by itself establish that its PDF arrived. It also warns against placing the active Zotero data directory in an ordinary cloud-synchronized folder. Follow the application’s supported configuration rather than treating every folder as safe to synchronize.

Its export guidance states that exporting is not a proper backup and that reimported items can lose their links to existing manuscript citations. Keep a native recovery plan alongside any RIS, BibTeX or other interchange export. Test each for its intended purpose instead of promising that one file reconstructs the whole working library.

For a team rehearsal, check the restored records, attachments, annotations and citation links separately. Record what was excluded or lost. A successful transfer of titles and identifiers is useful evidence, but it should not conceal missing notes or a broken manuscript connection.

Reference: Zotero: data syncing versus file syncing · Zotero: export is not a native backup

7. Make library stewardship a defined role

Appoint a library steward and a successor who can understand the arrangement. Write rules for importing batches, reviewing duplicates, correcting metadata and editing shared notes. Give collaborators the permissions they need and rehearse access removal with a synthetic account or other approved test arrangement. Do not use a real collaborator’s access as an experiment.

Agree where the authoritative record lives when someone keeps a personal copy. If an important correction is made, identify which manuscripts and exports need rechecking. Keep disagreements about interpretation in attributed notes; changing a citation record should not make an unresolved scientific judgment look settled.

Include the institution’s license, support and accessibility requirements in selection. Use a dated quote and a realistic handoff exercise for each candidate. The relevant result is whether the chosen configuration supports the team’s work, not a generic claim of superiority.

8. A worksheet for choosing and handing over a library

Fill this in before expanding the library to a larger team. For each question, add an evidence link or a pending action, the responsible person and the date. Revisit it before a manuscript handoff, an account transfer or a change of reference manager.

On small screens, scroll the table horizontally, or focus it and use the arrow keys.

Questions for a practical final check

• Records, attachments, notes and eligibility decisions have clear roles.
• Sharing was checked for the intended account and recipient.
• Confirmed duplicates were distinguished from related publications.
• Uncertain matches remain visible and unresolved.
• Citation links and native recovery were checked separately from export.