Sharing & Collaboration

Sharing starts with deliberate access settings and enough context for someone else to understand the data. openJII separates those concerns:

• Visibility & embargo controls whether an experiment is public now or private until a publish-on date.
• Project transfers requests migration of a PhotosynQ project into openJII. It is not a general ownership-transfer button for an existing openJII experiment.
• Open & FAIR data is a practical checklist for metadata, identifiers, standard exports, provenance, and licensing decisions.
• Choosing the owning workspace explains the picker on every create form, and what each choice commits you to.
• Moving a resource changes which workspace owns something you already made.

Experiments, macros, protocols, workbooks and devices share one access model with two levels: Can view and Can edit. Can edit covers settings, publishing and managing access; Can view covers reading — and, on an experiment, contributing measurements and annotations. A device is the exception: it is shareable but never publishable, so Can edit there means deleting it and issuing, rotating or revoking its certificate. Each resource has a Collaborators tab where a user, a team, or a whole organization is given one of the two levels. See Collaborators & access levels for the full behaviour on experiments.

Before publishing or exporting

1. Review the experiment description and structured metadata.
2. Confirm collaborator access levels and whether contributor anonymization is appropriate.
3. Check protocol and workbook versions.
4. Inspect data quality annotations and known exclusions.
5. Choose a license and citation practice for any external release.

Public visibility makes the experiment readable; it does not by itself provide complete metadata, a license, quality assurance, or a FAIR assessment.