Skip to content

Document the Standard Results #1632

Description

@perolavsvendsen

Note

Bigger discussion: Where should FMU results be documented? fmu-dataio, Sumo, elsewhere?

Current documentation of standard results is focused on the export. Information for consumers will also be necessary.

Representative user story:
As a data consumer, I would like to know what standard results exists, how I identify them and how I should consume them, so that I can use these data in my context.

  • Document the standard result identifier, e.g. "structure_depth_surface" so that consumers can know how to identify this standard result.
  • Document what it takes to make a standard result unique #1572 so that consumers can know how to filter down to this standard result.
  • Document default information classification.
  • ...

We currently document how to use the functions that create the standard results, but I am here referring to documentation of the standard results definition which is slightly different - although obviously related.

Could be an option to structure the documentation a bit differently, but a quick fix could be to add this information as an info box or something to the existing docs 🤷‍♂️

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions