You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the GCMD database mention indicators not valriable as the WMO. Maybe it could worth a clarification about what name to use. Can the user use one or the other? Are there instructions about one or the other? A: Note added that the user may use EarthCODE search to discover the variables.
corrected typos in the description in the comments and markdown cells
Removed mentioning of workflow/code but just referring to workflow to be more specific
property: consortium members: Is the tuple provided within round brackets? Shall it be separated by coma or simply multiple round brackets? Eg: [("", ""),("", "")] or [("", "")("", "")]. I would also remove the email as a mandatory element in the tuple, since then that email will remain in the PR without consensus of being publicly available.. . We should specify in the comments or inside the how to add multiple institutions as consortium members.
think of removing the Licence property from the Project entry, since we have it specified for Product and workflows / experiments etc. Then it is duplication. This way we would avoid having "various licenses" for the project since it will be clear for Product and the code.
not clear property of urls for the projects now explained in the comments of new version of the notebook
The instruction in the markdown cells are updated with clearer description of the process
Variables are defined in OSC as geophysical, climate and environmental variables selected from WMO OSCAR Database, complemented by the GCMD Keywords Database
the GCMD database mention indicators not valriable as the WMO. Maybe it could worth a clarification about what name to use. Can the user use one or the other? Are there instructions about one or the other?
A: Note added that the user may use EarthCODE search to discover the variables.
corrected typos in the description in the comments and markdown cells
Removed mentioning of workflow/code but just referring to workflow to be more specific
property: consortium members: Is the tuple provided within round brackets? Shall it be separated by coma or simply multiple round brackets? Eg: [("", ""),("", "")] or [("", "")("", "")]. I would also remove the email as a mandatory element in the tuple, since then that email will remain in the PR without consensus of being publicly available.. . We should specify in the comments or inside the how to add multiple institutions as consortium members.
think of removing the Licence property from the Project entry, since we have it specified for Product and workflows / experiments etc. Then it is duplication. This way we would avoid having "various licenses" for the project since it will be clear for Product and the code.