Comments (4)
Hi both, I'd suggest capturing this in the following way:
- we add a post-publication comment to the SOLARIS-HEPPA-4-2 data which explains why it was deprecated. That is added in #91
- 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
![Screenshot 2024-08-16 at 7 45 25 am](https://private-user-images.githubusercontent.com/114576287/358481688-0789c513-b877-4ded-bea8-b7344d7b3a81.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQxNDk1MzYsIm5iZiI6MTcyNDE0OTIzNiwicGF0aCI6Ii8xMTQ1NzYyODcvMzU4NDgxNjg4LTA3ODljNTEzLWI4NzctNGRlZC1iZWE4LWI3MzQ0ZDdiM2E4MS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODIwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgyMFQxMDIwMzZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0zZmNmYzdmNzQ5ZTM4ZTAzODYxMGY4MmVlOTMyNzYwY2I1NzIxMDhkMTZmNjU2OWYyMDRjMDYyODkwMmYwNzkzJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.nDO2xiT7T3dIjJBc1RpCo0jbhU4CeWB1ywk_UzDMJPo)
from input4mips_cvs.
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?
from input4mips_cvs.
@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
from input4mips_cvs.
Resolved by #91
from input4mips_cvs.
Related Issues (20)
- Consistent repo versioning HOT 3
- Create CMOR input file HOT 3
- Solar data tiny tweak - targeting SOLARIS-HEPPA-CMIP-4-4 HOT 8
- CR-CMIP-0-3-0 HOT 2
- Automate scrape from ESGF HOT 11
- GitHub pages HOT 7
- Add CI step which checks that web pages are up to date before merging
- Add CI to check that the CVs can be parsed with input4mips validation
- Test stratospheric aerosol file (extinction) being uploaded on input4mips FTP HOT 19
- SOLARIS-HEPPA-4-3 HOT 12
- Add CR logo to README
- Add links to HTML table views to GitHub pages
- Emissions (CEDS) sample data validation HOT 2
- Add links to CMOR definitions
- Add source_id/overview view for HTML pages HOT 1
- Fix MRI-JRA55-do-1-6-0 license omission - CC BY 4.0 HOT 4
- Deploying website for each version HOT 2
- Add workaround for automated comment generation when there are lots of changes
- HTML page links need update in the README HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from input4mips_cvs.