New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ENH: data.geometry tag is a file path, makes it difficult to find data #710

Open

perolavsvendsen opened this issue Jun 26, 2024 · 0 comments

Member

perolavsvendsen commented Jun 26, 2024

Ref #635

Quick discussion 26/6-2024

Current implementation is using file paths as identifier of a grid geometry. Should rather be an uuid or similar?

Next step from current implementation
Does this expand to all other data (that have some sort of parent)?
OK/confusing to have more than one uuid per data object, or strive to have only one (the Sumo-generated uuid)?
- Is it OK to "predict" which uuid this will get in Sumo?
- Can Sumo use a pre-existing uuid if need be?

data:
  geometry:
    filepath: /etc/etc/etc
  uuid: <uuid4>

fmu:
  case
  iteration
  realization
  aggregation
  model
  object: # option?
    uuid: <uuid4> # option?

_sumo:
  id: <uuid4>   # fmu.case.uuid + file.relative_path = uuid

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment