New data and who can see it

A project’s New data settings say what a file starts with when someone adds it: who can see it, the depth reference for wells, the coordinate system, the unit system and the source attribution. They are suggestions, shown as “Project default” when a file is added; the person adding the file can keep them or change them. Changing the settings never changes files already in the project.

Who can see an uploaded file, and who can build on it, is changed in one place on the file: Who can see this.

In Workspace

1. Settings > New data (an administrator; everyone else sees the settings and cannot change them). Under Who can see new files, choose Everyone in this project or Only the person who adds it. Until someone chooses, the page says new files behave as “Only the person who adds it”. The coordinate system is chosen by its name; its code is under Technical details. Save new-data settings says “Saved. New files will start with these settings. Files already in the project did not change.”
2. Add data: the file starts with the project’s settings, each marked “Project default”. Change any of them for this file and it says “You said”. The report says “Added. Everyone in this project can see it.” and “Project default, accepted by you” when you kept them.
3. Who can see this, on a file you added: Only me, Me and people I choose (tick Can see for each person, and Can build on for those who may use it in their own results) or Me and everyone in this project. Save who can see this first says who will be told and who will lose access. When the change is narrower, say why: your reason is kept with the change, and people who lose access also lose it to results built on this file. Adding them back later does not restore those.
4. Activity > Project settings lists every change to the New data settings, with who made it.

The project overview shows the current setting under New files.

In Python

Bring a file and the id of a colleague in the project. The examples use a LAS file of the geothermal well HON-GT-01:

file = "HON-GT-01.las"
colleague = "bob"

Read the settings and, as an administrator, change them. The change is made on the settings you read: if someone changed them since, it is refused and you read them again.

from ophiolite.new_data import lines

settings = client.new_data_defaults()
settings = client.set_new_data_defaults(settings, visible_to="project", attribution="NLOG well files")
print("\n".join(lines(settings)))

Add the file without naming who can see it or where it comes from: it starts with the project’s settings, and the report says so.

report = client.upload(file, rights_confirmed=True)
print(report.text())
asset = report.items[0]["asset_id"]

See who can see it, and make it narrower: only you, for now. First ask what the change would do; nothing is saved.

from ophiolite.new_data import change, preview, preview_line

who = client.audience(asset)
print(preview_line(preview(client, change(who, state="me"))))
who = client.set_audience(who, state="me", reason="Only the interpretation team for now")

Give your colleague access again, and let them build on it:

who = client.set_audience(who, people=[colleague], build_on=[colleague])
print(who["state"], who["people"])

A narrower change without a reason is refused with “Say why you are making this narrower. Your reason is kept with the change.” Every change is made on the snapshot you read (who): if someone changed who can see the file since, it is refused and you read it again with client.audience(asset). upload(..., audience="me") or a list of people overrides the project’s setting for that upload; audience="project" is accepted only when that is the project’s setting.

On the command line

ophiolite new-data
ophiolite new-data --set visible_to=project --set attribution="NLOG well files"
ophiolite upload HON-GT-01.las --rights-confirmed
ophiolite upload HON-GT-01.las --rights-confirmed --use-project-defaults
ophiolite audience --asset ASSET
ophiolite audience --asset ASSET --set me --dry-run
ophiolite audience --asset ASSET --set me --reason "Only the interpretation team for now"
ophiolite audience --asset ASSET --set bob --build-on bob

ophiolite upload without --attribution or --audience takes the project’s settings; --use-project-defaults also keeps the project’s default for every field a file leaves open. ophiolite audience --show --json prints a snapshot that --snapshot changes later, refused if it changed in between.

When it is refused

You see	What to do
Only a project administrator can change what new files start with. Ask one of this project’s administrators.	Ask an administrator.
These settings changed after you opened them. Reload to see the current ones, then make your change again.	Read the settings again and make your change.
That coordinate system is not one this project can use. Pick one from the list.	Choose a coordinate system from the list.
This deployment cannot tell who is in the project, so new files cannot be made visible to everyone in it. Choose ‘Only the person who adds it’.	Choose “Only the person who adds it”.
Say why you are making this narrower. Your reason is kept with the change.	Give a reason.