Registering CMIP7 prelim solar historical forcing

[berndfunke]

Datasets have the following filenames: solarforcing-ref-day_input4MIPs_solar_CMIP_SOLARIS-HEPPA-4-1_gn_18500101-20231231.nc solarforcing-ref-mon_input4MIPs_solar_CMIP_SOLARIS-HEPPA-4-1_gn_18500101-20231231.nc solarforcing-picontrol-fx_input4MIPs_solar_CMIP_SOLARIS-HEPPA-4-1_gn_18500101-18730128.nc There will also be an alternative SSI dataset which we shall call solarforcing-alternative-ssi-day_input4MIPs_solar_CMIP_SOLARIS-HEPPA-4-1_gn_18500101-20231231.nc

Current global attributes (for solarforcing-ref-day_input4MIPs_solar_CMIP_SOLARIS-HEPPA-4-1_gn_18500101-20231231.nc):

:title = "CMIP7 solar forcing historic (1850-2023)"; :institution_id = "SOLARIS-HEPPA"; :institution = "APARC SOLARIS-HEPPA"; :activity_id = "input4MIPs"; :comment = "SSI data are taken from NRL v03r00_preliminary. Sub-annual variability has been added for the period before 1874; m. TSI in this file is from source data as integral over SSI between 0 and 10,000nm"; :time_coverage_start = "1850-01-01"; :time_coverage_end = "2023-12-31"; :frequency = "day"; :source = "nrlssi_v03r00_preliminary (Odele Coddington et al., pers. comm.); Ap, Kp, F10.7 from ftp.ngdc.noaa.gov until 2014, afterwards from GFZ Potsdam (https://kp.gfz-potsdam.de), P-IPR from SEP-II (Ilya Usoskin et al., pers. comm.), MEE-IPR from APEEP apeep_v2024b_cmip7 (Max van de Kamp et al., pers. comm.), GCR-IPR from CRII v2024-02 (Ilya Usoskin et al., pers. comm.)"; :source_id = "SOLARIS-HEPPA-CMIP-4-1"; :realm = "atmos"; :further_info_url = "http://solarisheppa.geomar.de/cmip7"; :metadata_url = "see http://solarisheppa.geomar.de/solarisheppa/sites/default/files/data/cmip7/CMIP7_metadata_description_4.1.pdf"; :contributor_name = "Bernd Funke, Timo Asikainen, Stefan Bender, Thierry Dudok de Wit, Illaria Ermolli, Margit Haberreiter, Doug Kinnison, Sergey Koldoboskiy, Daniel R. Marsh, Hilde Nesse, Annika Seppaelae, Miriam Sinnhuber, Ilya Usoskin, Max van de Kamp, Pekka T. Verronen"; :references = "Funke et al., Geosci. Model Dev., 17, 1217–1227, https://doi.org/10.5194/gmd-17-1217-2024, 2024"; :contact = "bernd@iaa.es"; :dataset_category = "solar"; :dataset_version_number = "4.1"; :grid_label = "gn"; :mip_era = "CMIP7"; :target_mip = "CMIP"; :variable_id = "multiple"; :license = "Solar forcing data produced by SOLARIS-HEPPA is licensed under a Creative Commons Attribution \"Share Alike\" 4.0 International License (http://creativecommons.org/licenses/by/4.0/). The data producers and data providers make no warranty, either expressed or implied, including but not limited to, warranties of merchantability and fitness for a particular purpose. All liabilities arising from the supply of the information (including any liability arising in negligence) are excluded to the fullest extent permitted by law."; :Conventions = "CF-1.6"; :creation_date = "2024-05-06T14:57:54Z";

[durack1]

@berndfunke great, thanks for starting this issue. You've provided a great start above, so we can tweak these to bring info inline across new contributed datasets. Also excellent, data coverage until 31 December 2023, nice!

We'll have a catch a couple of tweaks.

"SOLARIS-HEPPA" appears to be a project hosted by GEOMAR (https://solarisheppa.geomar.de/) if I am not mistaken? We might need to toggle this to an actual institution just to clean things up - we are trying to more tightly define what a contributing institution is, and align these with the ror.org identifiers (e.g. https://ror.org/041nk4h53)

We are catching new datasets in the "CMIP6Plus" mip_era with an aim to learning by doing before we get to CMIP7 toward the end of this, or early next year. To that goal, the latest prototype forcing data are being published into this subproject (see here) which enables data to be delineated from their CMIP6 precursors.

@wolfiex @taylor13 ping - may need engagement to figure this SOLARIS-HEPPA "institution" out.

[durack1]

@znichollscr @vnaik60 pinging you both on this thread, another new dataset

[vnaik60]

Thanks @durack1 for bringing this to my attention. Indeed, thank you @berndfunke for getting this in the pipeline.

This caught my eye - solarforcing-picontrol-fx_input4MIPs_solar_CMIP_SOLARIS-HEPPA-4-1_gn_18500101-18730128.nc. Why does the climatology include data only to Jan 28? Or perhaps this is a typo.

[berndfunke]

"SOLARIS-HEPPA" appears to be a project hosted by GEOMAR (https://solarisheppa.geomar.de/) if I am not mistaken? We might need to toggle this to an actual institution just to clean things up - we are trying to more tightly define what a contributing institution is, and align these with the ror.org identifiers (e.g. https://ror.org/041nk4h53)

GEOMAR is hosting only the website of the project, not the project itself (which is part of the SOLARIS-HEPPA activity within the APARC project, thus hosted by WCRP).

If an actual institution is required, probably the best would be to put my institution here (as the coordinator of the CMIP solar forcing activity): IAA-CSIC (Instituto de Astrofisica de Andalucia - Consejo Superior de Investigaciones Cientificas, Spain, https://ror.org/04ka0vh05), though at the end it is a multi-institutional effort.

[berndfunke]

We are catching new datasets in the "CMIP6Plus" mip_era with an aim to learning by doing before we get to CMIP7 toward the end of this, or early next year. To that goal, the latest prototype forcing data are being published into this subproject (see here) which enables data to be delineated from their CMIP6 precursors.

Shall we thus change mip_era = "CMIP6plus"?

[berndfunke]

Thanks @durack1 for bringing this to my attention. Indeed, thank you @berndfunke for getting this in the pipeline.

This caught my eye - solarforcing-picontrol-fx_input4MIPs_solar_CMIP_SOLARIS-HEPPA-4-1_gn_18500101-18730128.nc. Why does the climatology include data only to Jan 28? Or perhaps this is a typo.

No, it is not a typo. The same averaging period has been used in CMIP6. It is just a full 2 solar cycle period (solar cycle start phase = solar cycle end phase).

[durack1]

@berndfunke thanks again for raising this issue. Now that this is all a bit clearer, I suggest we learn by doing to correctly identify SOLARIS-HEPPA as a consortium, which has several institutions (and contributors based at institutions, like yourself at IIA-CSIC) that need to be identified as consortium members. Is it right to assume that all co-authors of the Funke et al., 2023 paper, with the 12 identified affiliations members?

To that question a second question, over the life of "SOLARIS-HEPPA" has institutional membership remained constant throughout time? And if yes, would this consortium be identified as a contributor to CMIP6 (previous data), CMIP6Plus/CMIP7 current data, and potentially backward in time (e.g., CMIP5) and forward in time (e.g., CMIP8)?

I ask these questions, so we can use SOLARIS-HEPPA as a template by which to define a structure that enables us to keep track of contributions through time

[berndfunke]

@durack1, this is a great suggestion, though not straight forward to implement. (1) The number of contributors is larger than reflected in the Funke et al., 2023 paper (this is not really an issue). (2) Institutional membership has changed from CMIP5 to CMIP7, and it might change in the future as new datasets are coming up and might be incorporated in future data versions. (3) SOLARIS-HEPPA (as APARC/WCRP) activity does more than providing forcing, so actually it is a only subset of SOLARIS-HEPPA membership. One solution would be to name the consortium SOLARIS-HEPPA-CMIP7-consortium and we include all contributors to this specific dataset.

[durack1]

@berndfunke I had a feeling this was going to get a little complicated. It might be worthwhile using the identification and registration of "SOLARIS-HEPPA" as a relatively complex case study that needs to be captured - this will provide a great template for other cases. I'll circle with @wolfiex who has been leading this process and come back to you with questions - maybe even a telco to gather information most efficiently

[berndfunke]

Hi @durack1, any news on the institution_id case? I have now a (preliminary) list of institutions and rois involved in SOLARIS-HEPPA-CMIP7: Astronomical Observatory of Rome https://ror.org/02hnp4676 FMI https://ror.org/05hppb561 IAA-CSIC https://ror.org/009nnap37 ISSI https://ror.org/01xm30661 KIT https://ror.org/04t3en479 LASP https://ror.org/01fcjzv38 LPC2E https://ror.org/049k66y27 MPS https://ror.org/02j6gm739 NCAR https://ror.org/05cvfcr44 PMOD https://ror.org/02gtrqv93 University of Bergen https://ror.org/03zga2b32 University of Leeds https://ror.org/024mrxd33 University of Otago https://ror.org/01jmxt844 University of Oulu https://ror.org/03yj89h83

Meanwhile the preliminary forcing datasets are on the SOLARIS-HEPPA webpage https://solarisheppa.geomar.de/solarisheppa/cmip7 Direct access: picontrol: https://cloud.iaa.es/index.php/s/XaSb85EpGNYqkEw hist ref day: https://cloud.iaa.es/index.php/s/nJFTPcnFwZ3smTo hist ref month: https://cloud.iaa.es/index.php/s/n7cacmRBjk5Gb8f

Please let me know if anything needs to be changed (note that :mip_era is still "CMIP7" and :institution_id still "SOLARIS-HEPPA").

[durack1]

@berndfunke this is great! Just the kind of information we needed to get this process of learning by doing started.

Just pinging @wolfiex on this thread as he has been harmonizing all the information across projects into a centralized format, we'll likely require a little iteration on this.

So to start we can work with "SOLARIS-HEPPA-CMIP7" as the next-generation consortium for the new dataset contribution, while also having the existing CMIP6 data identified by institution_id=SOLARIS-HEPPA, and source_id=SOLARIS-HEPPA-3-2. Just thinking aloud, this might look like the below, does that seem like a reasonable path to you?

MIP era	institution_id	source_id	notes
CMIP6	SOLARIS-HEPPA	SOLARIS-HEPPA-3-2	finalized no change
CMIP6Plus	SOLARIS-HEPPA-CMIP7	SOLARIS-HEPPA-4-0?	working prototype published June 2024
CMIP7	SOLARIS-HEPPA-CMIP7	SOLARIS-HEPPA-4-2?	finalized datasets published ~Jan, ~Mar 2025 historical/piControl

[durack1]

@berndfunke just circling around on this, I was talking to @wolfiex (Dan Ellis, CMIP-IPO) about how best to implement this consortium registration, without having multiple duplicates. He suggested that we define "SOLARIS-HEPPA" as a consortium, and then indicate partner institutions start and end dates. So logically, this would be for the CMIP7 contribution (2023-) and for the CMIP6 contribution (~2014 to ~2017). Does this make sense?

To flesh out the idea, how different is the CMIP6 contribution consortium from the above https://github.com/PCMDI/input4MIPs_CVs/issues/17#issuecomment-2145687143? I am guessing considerable overlap.

I was also wondering aloud whether rather than start/end dates for each member, having these tied to a MIP era (CMIP5, CMIP6, CMIP7, CMIP8, ...) would make more sense and reduce the metadata overhead of having to identify when folks became engaged and then disengaged?

[berndfunke]

@durack1, something like this?

Aristotle University of Thessaloniki https://ror.org/02j61yw88 CMIP6 Astronomical Observatory of Rome https://ror.org/02hnp4676 CMIP7 BAS https://ror.org/01rhff309 CMIP6 EAWAG https://ror.org/00pc48d59 CMIP6 FMI https://ror.org/05hppb561 CMIP6 CMIP7 FU Berlin https://ror.org/046ak2485 CMIP6 GEOMAR https://ror.org/02h2x0161 CMIP6 GSFC https://ror.org/0171mag52 CMIP6 IAA-CSIC https://ror.org/009nnap37 CMIP6 CMI7 ISSI https://ror.org/01xm30661 CMIP6 CMIP7 KIT https://ror.org/04t3en479 CMIP6 CMIP7 LASP https://ror.org/01fcjzv38 CMIP6 CMIP7 LPC2E https://ror.org/049k66y27 CMIP6 CMIP7 Met Office https://ror.org/01ch2yn61 CMIP6 MPS https://ror.org/02j6gm739 CMIP6 CMIP7 NCAR https://ror.org/05cvfcr44 CMIP6 CMIP7 PMOD https://ror.org/02gtrqv93 CMIP6 CMIP7 University of Bergen https://ror.org/03zga2b32 CMIP7 University of Leeds https://ror.org/024mrxd33 CMIP6 CMIP7 University of Montreal https://ror.org/0161xgx34 CMIP6 University of Otago https://ror.org/01jmxt844 CMIP6 CMIP7 University of Oulu https://ror.org/03yj89h83 CMIP6 CMIP7 University of Reading https://ror.org/05v62cm79 CMIP6

[durack1]

Yep, I think that is exactly what we needed to figure this out. @wolfiex had planned to take a peek at this tomorrow, so hopefully we have a solution soon which will enable the registration to be finalized, and these data to also be finalized as their v1.0 prototypes!

[durack1]

@berndfunke just a point of reference, as https://solarisheppa.geomar.de (website) exists today, presumably GEOMAR is a CMIP7 partner/consortium member, right?

If yes, this is likely the partitioning we have across CMIP6 and CMIP7/new data is:

MIP era	consortium_id	member institution_id
CMIP6	SOLARIS-HEPPA	Aristotle University of Thessaloniki, BAS, EAWAG, FMI, FU Berlin, GEOMAR, NASA-GFSC, IAA-CSIC, ISSI, KIT, LASP, LPC2E, MOHC/MetOffice, MPS, NCAR, PMOD, University of Leeds, University of Montreal, University of Otago, University of Oulu, University of Reading
CMIP7	SOLARIS-HEPPA	Astronomical Observatory of Rome, FMI, GEOMAR, IAA-CSIC, ISSI, KIT, LASP, LPC2E, MPS, NCAR, PMOD, University of Bergen, University of Leeds, University of Otago, University of Oulu

[berndfunke]

@durack1, this looks very good to me! Yes, GEOMAR should be in.

[durack1]

Ok great, this is enough to get started. This will enable us to reuse institution_id = SOLARIS-HEPPA, in the dataset generation and publication.

If you want to take a pass at updating the existing prototypes to reflect this, then I'll pull these down and provide any additional nit suggestions before we can get these finalized and in the queue for ESGF/input4MIPs publication - yay..

[vnaik60]

Yay! Solar will be the second CMIP6Plus dataset show up in input4mips. Thank you!

[durack1]

It could be the second or the fourth^1, depending on when these all land.. Progress is happening!

1 we have OMIP/JRA55-do-1-6-0 being downloaded, and CMIP-DECK/CR-hist-ghg-concs-0.1.0, CMIP-DECK/DRES-CMIP-BB4CMIP7-1-0, plus this dataset SOLARIS-HEPPA-4-0 all being worked on for the initial release. These wil all be published into the input4MIPs CMIP6Plus MIP era

[wolfiex]

Hi @berndfunke,

I have been rewriting how we store the consortium entries. Based of the information above, I have generated an entry:

https://github.com/PCMDI/mip-cmor-tables/blob/jsonld/JSONLD/organisations/consortia/solaris-heppa.json

When compiled this will generate something along the lines of:

https://github.com/PCMDI/mip-cmor-tables/blob/jsonld/JSONLD/scripts/output/consortia.json#L440-L513

With the name of each institution substituted in.

@durack1 To continue we just need to think of an acronym for the longer institution names.

I am in the process of rewriting the github action used to submit individual institution and will create an entry for them once this is done.

Dan

[taylor13]

Not sure this is relevant, but in CMIP5 and CMIP6 we defined 2 global attributes related to institution which in CMIP6 were named: institution and institution_id. institution_id was short (an acronym) and suitable for inclusion in faceted searches, directory structures, and dataset unique identifiers (e.g., further_info_url). In contrast, institution was the full name of the institution (and could include spaces and other characters forbidden in institution_id).

[wolfiex]

Yes, It is the institution_id that I am after for some of the entries. The name is extracted directly from ROR. @taylor13

[berndfunke]

@durack1, just noticed that the ror of IAA-CSIC is wrong, should be https://ror.org/04ka0vh05

[durack1]

Great, thanks for checking. It's likely we'll have to iterate a little to get this all correct, but the info that you've provided above is good enough to get us started

[wolfiex]

@berndfunke As you might have been made aware (with several commits in your name), the consortium and institutions you have provided have been added to the development branch for the mip-cmor-tables.

A cleaned up version is available to preview at https://github.com/PCMDI/mip-cmor-tables/tree/jsonld/JSONLD/scripts/output

[berndfunke]

@wolfiex thanks for updating. I spotted the following:

IAA-CSIC "Institute of Astrophysics of Andalusia” is missing (https://ror.org/04ka0vh05 https://ror.org/04ka0vh05)

LASP (https://ror.org/01fcjzv38 https://ror.org/01fcjzv38) is missing (or has it been substituted by UColorado)?

AoR -> please change to OAR-INAF "Astronomical Observatory of Rome - National Institute for Astrophysics”

El 11 jun 2024, a las 21:28, Dan Ellis @.***> escribió:

@berndfunke https://github.com/berndfunke As you might have been made aware (with several commits in your name), the consortium and institutions you have provided have been added to the development branch for the mip-cmor-tables.

A cleaned up version is available to preview at https://github.com/PCMDI/mip-cmor-tables/tree/jsonld/JSONLD/scripts/output https://github.com/PCMDI/mip-cmor-tables/tree/jsonld/JSONLD/scripts/output — Reply to this email directly, view it on GitHub https://github.com/PCMDI/input4MIPs_CVs/issues/17#issuecomment-2161465347, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGR2OME5YOJKF6MIDIWIIQLZG5FXFAVCNFSM6AAAAABH7TX2NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRRGQ3DKMZUG4. You are receiving this because you were mentioned.

——————————————————————————— Dr. Bernd Funke (mailto: @.***) Instituto de Astrofísica de Andalucía (CSIC) Glorieta de la Astronomía s/n, 18008 Granada, Spain Phone: +34 958 230522 / Fax: +34 958 814530 ———————————————————————————

[berndfunke]

@wolfiex, a new request from NCAR: they want the name to be NSF NCAR (not NCAR) for the institutional id.

[wolfiex]

@durack1 where do we stand on changing existing ids at this stage? Do we have dual entries?

[durack1]

@berndfunke we'll need to catch that with a hyphen, NSF-NCAR, much like we have with other institutions, NASA-GISS, NOAA-GFDL etc.

@wolfiex I presume we can catch their existing CMIP6 and earlier "NCAR" as an alias? I just checked, there is no other identity that I can find in the ESGF index, but I do recall a hyphenated "*-NCAR" has existed before

[durack1]

@berndfunke just circling on this, who at NCAR wanted the identifier toggled to "NSF-NCAR". We'll need to be a little careful to make sure that any changes meet the needs of the broad community this identifier represents, and it would surprise me a little if the existing "NCAR" identifier used in CMIP3, 5, and 6 wasn't preferred to the "NSF-NCAR" update.

[berndfunke]

I received the attached email from Doug Kinnison:

Inicio del mensaje reenviado:

De: Douglas Kinnison @.> Asunto: Fwd: Fwd: institution_id for CMIP7 solar forcing datasets Fecha: 14 de junio de 2024, 17:31:56 CEST Para: Daniel Marsh @.>, Bernd Funke @.***>

Hi Gents...

I just got this email from the CMIP7 person at "NSF NCAR".

It seems that they want the name to be NSF NCAR (not NCAR) for the institutional id.

If this can be changed - please do.

Thanks,

Doug

-------- Forwarded Message -------- Subject: Re: Fwd: institution_id for CMIP7 solar forcing datasets Date: Thu, 13 Jun 2024 10:26:13 -0600 From: Gary Strand @.> @.> To: Douglas Kinnison @.> @.>

Correction - CESM will be using "NSF NCAR" for the institition_id.

On Tue, May 28, 2024 at 10:32 AM Douglas Kinnison @. @.>> wrote: Thanks Gary!!

On 5/28/24 8:04 AM, Douglas Kinnison wrote:

Hi Gary...

I hope you are doing well?

Are you still working on the CMIP effort for NCAR? If so, could you advise on the questions below (i.e., related to ror.org http://ror.org/ id for NCAR)?

Thanks,

Doug

-------- Forwarded Message -------- Subject: institution_id for CMIP7 solar forcing datasets Date: Thu, 23 May 2024 17:55:54 +0200 From: Bernd Funke @.> @.> To: Thierry DUDOK DE WIT @.> @.>, Margit Haberreiter @.> @.>, Daniel Marsh @.> @.>, Ilya Usoskin @.> @.>, Annika Seppälä @.> @.>, Doug Kinnison @.> @.>, Hilde Nesse Tyssøy @.> @.>, Ilaria Ermolli @.> @.>, Miriam Sinnhuber @.> @.>, Odele Coddington @.> @.>, Natalie Krivova @.> @.>, Chatzistergos, Theodosios @.> @.>, Sergey Koldobskiy @.> @.>, Stefan Bender @.> @.>, van de Kamp Max (FMI) @.> @.>, Pekka Verronen @.> @.>, timo.asikainen @.> @.>

Dear all,

while for the CMIP6 forcing datasets on input4MIPs we were able to use “SOLARIS-HEPPA” as institution_id, this is not possible anymore for CMIP7, because the institution_id has now to be associated to a (or several) roi and there is none for SOLARIS-HEPPA (nor APARC). For CMIP model datasets from multi-institutional consortia this seems to be solved by introducing an institution_id for a consortium, e.g., “MESSy-Consortium”. Within the CMIP climate forcing task team it is now under discussion to use a similar construction for our case, although it is even a bit more difficult because the consortium might change from e.g. CMIP7 to CMIP8 (in fact it has changed from CMIP5 to CMIP7). My suggestions would therefore be to define “SOLARIS-HEPPA-CMIP7-Consortium” as institution_id which could include the following institutions (in alphabetical order):

Astronomical Observatory of Rome https://ror.org/02hnp4676 https://ror.org/02hnp4676 FMI https://ror.org/05hppb561 https://ror.org/05hppb561 IAA-CSIC https://ror.org/009nnap37 https://ror.org/009nnap37 KIT https://ror.org/04t3en479 https://ror.org/04t3en479 LASP https://ror.org/01fcjzv38 https://ror.org/01fcjzv38 LPC2E https://ror.org/049k66y27 https://ror.org/049k66y27 MPS https://ror.org/02j6gm739 https://ror.org/02j6gm739 NCAR https://ror.org/05cvfcr44 https://ror.org/05cvfcr44 PMOD https://ror.org/02gtrqv93 https://ror.org/02gtrqv93 University of Bergen https://ror.org/03zga2b32 https://ror.org/03zga2b32 University of Leeds https://ror.org/024mrxd33 https://ror.org/024mrxd33 University of Otago https://ror.org/01jmxt844 https://ror.org/01jmxt844 University of Oulo https://ror.org/03yj89h83 https://ror.org/03yj89h83

This all is still under discussion, but in order to be prepared, let me know (possible by end of this week) if

1) the associated roi is incorrect 2) you are aware of other institutions which should be listed 3) you don’t want your institution to be listed.

The idea would be to use this institution_id for all CMIP7 solar forcing datasets to be uploaded to input4MIPs.

Best, Bernd.

-- Gary Strand, CESM Data Manager ORCID 0000-0001-9740-0104 @. @.>

El 17 jun 2024, a las 16:41, Paul J. Durack @.***> escribió:

@berndfunke https://github.com/berndfunke just circling on this, who at NCAR wanted the identifier toggled to "NSF-NCAR". We'll need to be a little careful to make sure that any changes meet the needs of the broad community this identifier represents, and it would surprise me a little if the existing "NCAR" identifier used in CMIP3, 5, and 6 wasn't preferred to the "NSF-NCAR" update.

— Reply to this email directly, view it on GitHub https://github.com/PCMDI/input4MIPs_CVs/issues/17#issuecomment-2173605657, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGR2OMHG4YOEARSPOGVGMCLZH3YTBAVCNFSM6AAAAABH7TX2NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZTGYYDKNRVG4. You are receiving this because you were mentioned.

[durack1]

@berndfunke thanks, Gary is the contact for the CMIP data generation (CMIP3, 5, 6, and presumably 7), so this closes the loop. A wrinkle, the ROR registered acronym is "NCAR", so we'll have to manage our own acronyms in addition to the ROR official one. I think this is one of numerous cases we'll have to manage (and ROR identifier different from what is used in CMIP)

[durack1]

Note to self, the datasets available from https://solarisheppa.geomar.de/cmip7 are identified as SOLARIS-HEPPA-4-1, so this will need to be the source_id registered not SOLARIS-HEPPA-4-0 as noted https://github.com/PCMDI/input4MIPs_CVs/issues/17#issuecomment-2146223824