Capture version deprecation information in CVs about input4mips_cvs

[znichollscr]

Hi both, I'd suggest capturing this in the following way:

1. we add a post-publication comment to the SOLARIS-HEPPA-4-2 data which explains why it was deprecated. That is added in #91
2. we add a source ID level view to our docs, so it's easier for people to see what is going on at a higher level than what is provided by the files and dataset views (which have other benefits, so we should keep them, but no single view will serve all purposes). That is added in #92

The end result is a view like the following (note the search field in the top-right, which is why you only see solaris data in the screenshot), which I think looks pretty clear. If you want to play around with this view yourself, the preview is here

[vnaik60]

Excellent point @durack1! It would be important to keep track of the updates and reasons for deprecation of the previous version of the data just as was done manually in input4MIPs summary doc.
No, we dont use the proton ionization data for simulations.

@znichollscr this seems like a sensible approach to me, though, @durack1 would have more thoughts. By the way, did you lose the "latest" column in this version?

[durack1]

@znichollscr you are a wizard!

A couple of nits

• for the abandoned datasets, as the SOLARIS-HEPPA v4.1 was made available, but not through ESGF we need to be careful with details so how about "registered but never published to ESGF". This will also be the case with some of the alpha-prototype data that Tom has been handing about. As CR-CMIP-0-2-0 never saw the light of day (no external party ever got their hands on it, no?) this comment is accurate
• The the "latest" point of @vnaik60. This is buried in the "publication_status" key, with "published" = latest, "retracted" = not latest, "registered" = we know about it and it's imminent, and "abandoned" - I think this is perfect, @vnaik60 is that ok with you?

Otherwise this looks like just the ticket.

I was hoping we could add the "source_id view, datasets view, files view" links across the HTML header - much like we have with the links on the https://wcrp-cmip.github.io/CMIP6_CVs/docs/CMIP6_source_id.html page(s). If you have the bandwidth, then I think that is all, and solves all our discussed HTML ponderings

[durack1]

Resolved by #91