paolap
commented
1 year ago If we find a good way to define that yes we can definitely add it, otherwise this can still be targeted as a "dataset" with no further specification or a "dataset-collection" which is not specific of what the collection is, i.e. if it's homogeneous or not.
Probably, if you want to really add something to a query you could have a category dataset/model output & reanalysis dataset/observation&reanalysis dataset/satellite& reanalysis etc for all possible combination. The from user point of view you could select dataset/satellite dataset/satellite &reanalysis if you want all satellite data Right now you would have to select dataset/satellite dataset/collection but the second possibly returns records with no satellite data
I guess the issue with this is that you cannot add two categories to a record, they are mutually exclusive, as you can add two or more options for the other tags, like regions, frequencies etc.
There are several products that merge station, satellite and reanalysis information together to create e.g. temperature or precipitation datasets. It might be useful to have a "merged" category for datasets, although I realise by itself it's not very descriptive at all. I just think picking one category (station, satellite or reanalysis) in these situations might mislead people into thinking they aren't also getting products dependent on other data types.