Skip to content

Handling of optional global attributes #988

Description

@taylor13

I'm moving here the part of the discussion In WCRP-CMIP/cmip7-cmor-tables#129 regarding handling of the source attribute, which is optional in CMIP7 (with its value uncontrolled).

As I understand it, CMOR gets its value for source from the cmor-cvs.json file, and the user can't override the value in the cmor-cvs.json file (if I correctly understand WCRP-CMIP/cmip7-cmor-tables#129 (comment)). I suggest that CMOR should treat source as follows:

  • by default, extract for source whatever is recorded as source in cmor-cvs.json and write it as the source global attribute. (I think that is what happens now.).
  • Enable users to override the source value found in cmor-cvs.json by specifying a different value in the *_input.json file. More specifically, if in the user's input file (e.g., https://github.com/PCMDI/cmor/blob/main/Test/CMOR_input_example.json) the user specified a value (other than "") for source, then CMOR would override the value provided by the cmor-cvs.json file.

We might want to do something similar for institution and experiment.

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