Skip to content

Registering issues with informational character and/or affecting a lot of datasets #3

@sol1105

Description

@sol1105

I hope I found the right place for the following suggestion(s) 😃

As far as I know there are the severity options critical, high, medium and low. Do you think it would be beneficial to add a new severity (and potentially status) with informational character only (eg. info)? Something that isn't a problem but more of a "please take a note of that when working with the data" or potentially adding further papers as reference some time after the publication of the data. Or would you recommend to use the low severity and eg. Won't fix status in such cases?

In our case, so far issues often affected a lot of datasets, and there is a limit to how many datasets a normal user can reference in an issue. Do you think it may be possible to make it easier to reference an entire simulation in an issue or even all runs with a certain source_id (eg. allow wildcards for certain facets of the Dataset-ID, eg CMIP6.C4MIP.NOAA-GFDL.GFDL-ESM4.1pctCO2-bgc.*.Amon.*.*#v20190101)? If it was feasible to implement, it should reduce the maintenance effort for more widespread issues quite a bit.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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