Bag Dragon

Review Mobile Changes with Dragon Sync

Understand incoming Mobile proposals, decide what becomes authoritative on Desktop, then publish the reconciled collection back to Mobile.

Dragon Sync Review

📥

Mobile proposes. Desktop decides.

Dragon Sync is intentionally review-based. Mobile can create supported collector changes, but those proposals do not silently overwrite the Desktop collection. Desktop reviews the incoming operation and decides which value should become authoritative.

Normal flow: Mobile change → Sync Now → Dragon Web → Dragon Sync Review → choose a decision → Apply Selected Decisions → Publish Fresh Snapshot.

Desktop Review Workflow

💻

Step-by-step

1

Start on the Dragon Sync Review overview

Open Dragon Sync Review for the matching active collection. The Overview shows how many proposals are ready, whether conflicts or orphans exist, and what each review decision means.

What to know
  • Confirm the Active Collection before making any decisions.
  • Incoming Changes Ready tells you how many Mobile proposals can be reviewed.
  • The proposal meanings panel is a quick reminder of what Accept Phone, Keep Desktop, Discard Proposal, and Decide Later do.
  • Mobile remains independent: rejecting a proposal does not delete the collector's Mobile bag.
2

Open Incoming and review each proposal

The Incoming tab shows each Mobile proposal separately. Compare Phone Previous, Desktop Current, and Phone Proposal before choosing what should happen on Desktop.

What to know
  • A proposal for a bag that is not yet in Desktop can offer Add to Desktop Collection.
  • Catalog-linked Mobile records keep their permanent sync identity when accepted into Desktop.
  • You can review several proposals before applying the selected decisions.
  • Use the Include this proposal checkbox when applying decisions in a batch.
3

Choose the correct decision

For each proposal, choose one explicit action. The correct choice depends on whether the Mobile change should become part of the authoritative Desktop collection.

What to know
  • Add to Desktop Collection / Accept Phone applies the Mobile proposal to Desktop.
  • Keep Desktop rejects the proposed value and preserves the existing Desktop state.
  • Discard Phone Proposal removes that synchronization request only; it does not delete or alter the Mobile collector record.
  • Decide Later leaves the proposal pending so you can revisit it.
  • Desktop collection backups are created before accepted value changes.
4

Apply decisions and publish the fresh snapshot

After you apply the selected decisions, Dragon Sync reports what was accepted, kept, or discarded and sends acknowledgements for the reviewed proposals. Publish a fresh snapshot so Mobile can download the updated authoritative Desktop collection.

What to know
  • The review summary confirms how many proposals were accepted, kept on Desktop, or discarded.
  • Acknowledgements tell Dragon Web that Desktop finished reviewing those proposals.
  • Publish Fresh Snapshot makes the latest Desktop collection state available to Mobile.
  • After publishing, Mobile can refresh the collection and continue from the reconciled state.

Learn More

🧭

Understand each review option

Expand any item below for a deeper explanation of the Review Manager and why each option exists.

Accept Phone / Add to Desktop Collection

Apply the Mobile proposal to the authoritative Desktop collection.

Learn More

Use this when the Mobile change is correct and you want Desktop to adopt it. For a Mobile-created catalog bag that does not yet exist in the Desktop collection, the action can appear as Add to Desktop Collection. Bag Dragon creates a catalog-linked Desktop record with the same permanent sync identity.

Keep Desktop

Reject the Mobile proposal and keep the existing Desktop value.

Learn More

Use this when the Desktop collection already contains the value you want to preserve. The Mobile proposal is resolved without replacing the authoritative Desktop value.

Discard Phone Proposal

Remove only the incoming synchronization request.

Learn More

Discarding a proposal does not delete the bag on Mobile and does not alter the collector's independent Mobile record. It simply tells Dragon Sync that this particular proposal should not be applied to Desktop.

Decide Later

Leave the proposal pending for a future review.

Learn More

Use this when you need more information before choosing between the Mobile and Desktop states. The proposal stays available in Dragon Sync Review rather than being accepted or dismissed.

Orphans

Operations that cannot be matched cleanly to the expected Desktop record.

Learn More

An orphan can occur when a Mobile operation refers to a record or sync identity that the active Desktop collection can no longer resolve normally. The Orphans tab keeps these cases separate so they can be investigated rather than applied automatically.

Other Collections

Proposals that belong to a different Dragon Hoard.

Learn More

Dragon Sync is collection-aware. If a proposal belongs to another collection, it should not be applied to the currently active Hoard. Switch to the matching Desktop collection before reviewing that collection's proposals.

Why the Active Collection matters

Dragon Sync decisions are collection-scoped.

Learn More

Each Dragon Hoard has its own stable Collection ID. Review incoming changes only while the matching collection is active so Bag Dragon can compare the proposal with the correct Desktop records and publish the correct collection snapshot afterward.

Publish Fresh Snapshot

Make the reconciled Desktop state available to Mobile.

Learn More

After Desktop finishes reviewing changes, publishing a fresh snapshot creates the latest Mobile-ready view of that collection. Mobile can then refresh and download the authoritative state that includes the accepted decisions.

What stays private

Dragon Sync only transports supported structured synchronization data.

Learn More

Desktop and Mobile never communicate directly. Supported Dragon Sync operations travel through Dragon Web. Desktop-only information such as personal photos and other unsupported local data is not turned into authoritative Mobile data simply because a proposal is reviewed.

Core Dragon Sync Rule

🛡️

Desktop remains authoritative

Mobile is a connected collector client, not a direct editor of the Desktop database. Dragon Sync preserves that boundary by sending supported Mobile changes as proposals. Desktop explicitly reviews them, applies the decisions locally, and publishes a fresh collection snapshot afterward.