search

PCMDI / input4MIPs_CVs

Controlled Vocabularies (CVs) for use in input4MIPs
https://input4mips-controlled-vocabularies-cvs.readthedocs.io/en/latest/
Creative Commons Attribution 4.0 International
1 stars 1 forks source link

Generate version history json file - for use by ES-DOCS #2

Open durack1 opened 7 years ago

durack1 commented 7 years ago

@eguil @davidhassell this issue has been generated following the email correspondence regarding https://es-doc.org/cmip6-ensembles-conformance/

It will be useful to iterate over the format of the json version info within this issue

durack1 commented 4 years ago

I was hoping that this information would be stored alongside the version info. There is no current github based index, rather I would need to generate this for inclusion alongside the versioning info

mauzey1 commented 4 years ago

@durack1 Is there a file with this information you can post here? I would like to rewrite my program that created the input4MIPs version info file to include that information. That way if changes were to happen to the status of the datasets, we can update the deprecation info and rebuild the version info file.

durack1 commented 4 years ago

@mauzey1 that will be something that I need to go through notes (not digital) to generate - so a job for me. Do you have a list of the datasets that have been identified as deprecated? That will simplify my job, and I should be able to post text within this thread for simplicity.

We will obviously have to figure out where to put this going forward, but get up-to-date first

mauzey1 commented 4 years ago

@durack1 Here is a list of datasets listed as "deprecated" from input4MIPs. deprecated_list.txt

durack1 commented 1 year ago

Migrating this issue from https://github.com/PCMDI/input4MIPs-cmor-tables to this repo

durack1 commented 1 month ago

@davidhassell @charliepascoe just pinging you guys on this thread. We've (for years) had an aspiration to bring the forcing datasets used for simulations into the documentation list, so this will be our best way to achieve this - we now have a live repo with the latest data identity and status, we just need to wrap this up for documentation purposes