Given the difficulties to develop ad hoc ESGF search interfaces for each different activity in CORDEX (see #3), it would be good to have the FPS DRS to adhere as much as possible to the general CORDEX-CMIP6 DRS. In this sense, we could promote particular FPSs, such as FPS-URB-RCC to the level of a CORDEX activity:
This is in line with current practice in CORDEX-CMIP5 (activities were called projects in CMIP5):
Given the difficulties to develop ad hoc ESGF search interfaces for each different activity in CORDEX (see #3), it would be good to have the FPS DRS to adhere as much as possible to the general CORDEX-CMIP6 DRS. In this sense, we could promote particular FPSs, such as FPS-URB-RCC to the level of a CORDEX activity:
This is in line with current practice in CORDEX-CMIP5 (activities were called projects in CMIP5):![image](https://github.com/FPS-URB-RCC/cordex-cmip6-cv/assets/8810015/eebbf074-eb9a-4fbc-87aa-800c5d25ecff)
In this way, we would avoid having additional ad hoc menus for the![image](https://github.com/FPS-URB-RCC/cordex-cmip6-cv/assets/8810015/6710d066-6471-44fe-9807-644125efef6d)
fps_id
(as suggested in https://github.com/WCRP-CORDEX/cordex-cmip6-cv/issues/20) which are meaningless for most searches:It would also simplify the DRS of the FPS: https://github.com/FPS-URB-RCC/cordex-cmip6-cv/blob/cd26cac3c3ed915014e06cfa149b58c6562c10bd/CORDEX-CMIP6_DRS.json#L2-L6
which would become the same as the general CORDEX-CMIP6 one if we absorb the
experiment_id
into theversion_realization
.@gnikulin, could we have your input here?