Review and exchange scientific contributions

The current-backend development pilot supports project creation by explicitly provisioned creators, project administrators, members and viewers. A private browser inspector signs in with a provisioned credential through a local SSH connection. This is not yet a publicly hosted OIDC browser application.

Exact revisions and review

A contribution has a stable asset identity; updates produce immutable revisions. Inspect a contribution and deliberately select its revision. Save selected exact references as a review scene, then reopen that scene independently of later source updates. Previews remain separate: displaying two grids does not prove they align.

Comments attach to an exact asset revision. Project viewers can inspect and comment, but cannot publish or administer access. The pilot displays the newest 100 comments per revision. Project membership is checked again when reading data. Revocation prevents future service reads; it cannot erase previously downloaded customer-owned copies.

QGIS proposals

The configured QGIS adapter can explicitly publish a selected, saved, single-band Float32/Float64 GeoTIFF as a separate scalar-map contribution. Choose the physical unit and whether to create a contribution or update its saved binding. A background worker reads the file independently, captures values and validity masks, verifies its hash, and publishes an exact snapshot. Saving a file does not automatically publish it. The source raster stays unchanged.

The qualified subset is a north-up regular grid, known two-dimensional horizontal CRS, at most 100,000 cells and a 16 MiB source file. Unsupported scaling, rotation and CRS assumptions are refused. Horizontal coordinates, WKT, coordinate units, value units, nulls and conversion notes travel with the snapshot. A supplied parent reference is user-declared lineage, not an instrumented history of every QGIS edit. The GeoTIFF’s original bytes remain local in this publisher.

A receiving profile follows one configured contribution. It may also pin an exact revision. Background work downloads and prepares the raster and contours; the GUI thread applies the prepared layers. Rapid updates can coalesce to the latest revision. Rescale live colors changes only the local display range.

Taking data out

The browser exports an exact scientific snapshot as JSON, with null samples represented as null. When an original LAS was explicitly retained, the browser can download and verify those exact bytes.

The developer export tool tools/export_project.py writes selected qualified asset kinds, exact dependencies, latest saved scene references, comments, run provenance and available originals into a checksummed directory. Its manifest states omitted kinds and scope. Other historical revisions are not automatically included. Unsupported payloads fail unless metadata-only export is explicitly requested. This is not yet a complete all-types, all-history backup.

python3 -I tests/collaboration_independent_read.py EXPORT_DIRECTORY verifies and reads this representation using only Python’s standard library, without connecting to ArrayBridge. These workflows use the current project backend; they do not yet qualify normal workbench publication and execution against OSDU.