Understand source qualification

Stage 0 pilot, reviewed 23 September 2026. In Workspace, open Data, filter by source or scientific type, and inspect an upstream dataset. For Wells, choose Datasets to inspect the collection rather than an individual record.

The Checks on this source section shows:

• Not yet checked, Checked: no known losses, or Checked: some detail is lost. Always read the scope; preserving bytes is not scientific approval.
• Data type: the reader’s registered name. Technical details contains the scientific profile, source schema and mapping version; these are separate versions.
• Historical reads: whether the reader can request exact upstream versions or only the current source. Replaced SQL/file content may no longer be retrievable.
• Saved copy: a recorded retention claim, not permission to share data.

Expand Technical details to copy the original report, method and exact identifiers. An unknown assessment shows Check result not recognised. A missing schema/version shows Not recorded; the interface does not guess.

Reading a source does not authorize retaining or redistributing it. Existing project and source authorization still apply. An expired sign-in or denied source must be restored before inspection; a cached report does not bypass the check.

Unknown units or depth references remain visible. A missing reference record can allow inspection while preventing an operation or destination publication that needs resolved context. No conversion is inferred from the label shown in a form.

Stage 0 source qualification alone does not grant sharing or approval. The separate Stage 1 reviewed release workflow now supports explicitly authorized file/SQL retained packages. General OSDU publication and native application telemetry remain unqualified. See availability. Try the synthetic independent-reading demo and read the developer contract.

To configure a connection yourself, start with manual source setup.