In r-ioga, Export project compares the project’s SHARE instances with the packaged shared-resource projects from which they were copied. These shared instances are not included in the project archive: editing their copy does not update its source package.

The dialog groups added, deleted and modified nodes and relations by their shared project. It shows property values, status and geographic changes. Missing source projects are listed separately: their instances could not be compared. Cancel to preserve and reconcile the changes in the appropriate source project, or choose Export anyway knowing those shared edits will not be carried by this archive. There is no automatic merge back into the shared package.

If comparison itself fails, the current interface falls back to the usual export confirmation. The absence of a warning is therefore not proof that all dependencies and shared changes are preserved. The time-series export option is offered to administrators.

Project instance ── local models + resources + scenarios ──→ ZIP
Shared packages ── references remain dependencies ───────→ load separately
Shared edits ───── warning; not merged into that ZIP

Resource URLs in model and scenario XML are normalised to remove the source collaboration segment, including relation icons, so importing into another collaboration does not point back to the old one. Scenario folders retain their datasets and media with relative references; see Scenario timelines. Imported solutions remain deduced, not deployed or supervised.

Implementation: RIOGAFunctions, ExportProjectComponent, ProjectResource.sharedModifications and SharedInstancesDiff. SharedInstancesDiffTest covers default/runtime exclusions, status, geometry, additions/removals and relations; ProjectResourceExportTest covers URL portability. Consult the API reference.