Merge license information in CMIP6Plus_license.json in license information in source_id

[MartinaSt]

The license information is currently spread over two CVs, the CMIP6Plus_license.json (for CMOR?) and the source_id. I suggest to merge the remaining line in the license.json into the source_id information and remove CMIP6Plus_license.json. This will make it easier to maintain the license information. The source_id CV gets even longer but in my view the advantage in maintaining the license information is higher.

license section in source_id would become:

 "license_info": {
        "exceptions_contact": "@metoffice.gov.uk <- cmip6.hadgem3",
        "history": "2017-09-21: initially published under CC BY-SA 4.0; 2021-11-15: relaxed to CC BY 4.0",
        "id": "CC BY 4.0",
        "license": "Creative Commons Attribution 4.0 International License (CC BY 4.0; https://creativecommons.org/licenses/by/4.0/)",
        "source_specific_info": "https://ukesm.ac.uk/licensing-of-met-office-nerc-and-niwa-cmip6-data/",
        "url": "https://creativecommons.org/licenses/by/4.0/",
        "terms_of_use":"^CMIP6Plus model data produced by Met Office Hadley Centre is licensed under a Creative Commons Attribution 4.0 International License (CC BY 4.0; https://creativecommons.org/licenses/by/4.0/)\\. *Consult https://pcmdi\\.llnl\\.gov/CMIP6Plus/TermsOfUse for terms of use governing CMIP6Plus output, including citation requirements and proper acknowledgment\\. *Further information about this data, including some limitations, can be found via the further_info_url (recorded as a global attribute in this file).*\\. *The data producers and data providers make no warranty, either express 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\\.$"
      },

[durack1]

@MartinaSt the intention here is to have a list of acceptable licenses, and the project to specify which can be used, and then these are noted for each source_id entry. In CMIP6 we have CCO (NASA-GISS) and CC BY 4.0 (everyone else). So we recommend CC BY 4.0, and have flexibility to allow other non-standard cases, with these limited

[taylor13]

In here the so-called CMIP6Plus_license.json file contains a template for the "terms of use", not the license. This is confusing.