-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CMIP guide/CMIP6 license updates #464
Comments
The domain http://www.earthsystemcog.org/ is now redirecting to legacy-escog.github.io. There are other earthsystemcog.org links on the Data Users and Modelers pages. These links don't work with HTTPS. Some links will redirect, such as www.earthsystemcog.org/projects/wip. However, most are 404. |
Sorry, if I should understand, but I'm not sure what you're saying. Are you saying we can't fix the broken links, or we need to fix more links than the ones I noticed? Or ??? |
thanks @mauzey1, if we can identify these "dead" links, we can make sure to locate the information they were pointing to, and either reproduce this in our repo (and switch links), or add to the https://github.com/WCRP-CMIP/WGCM_Infrastructure_Panel repo and link to it from there - how many http://www.earthsystemcog.org/ links do we need to correct Ref WCRP-CMIP/WGCM_Infrastructure_Panel#7 |
@taylor13 the guidance on time averaging content can be found via the waybackmachine - so we have the content we can harvest. @mauzey1 is the dataUsers.html page we need the following changed: The additional link on the modelers.html page that needs changing is |
Relabelling this issue to capture a number of changes, including the CMIP6 license updates - https://github.com/orgs/WCRP-CMIP/projects/2 |
To do's - Fix www.earthsystemcog.org dead links
CMIP6 licenses updates - HTML rendering to be linked off
|
The following links are broken on both Accessing model output and Model output requirements:
The first link should be to: https://cmip6dr.github.io/Data_Request_Home/Documents/CMIP6_pressure_levels.pdf
I don't know where the second document is.
The text was updated successfully, but these errors were encountered: