-
Notifications
You must be signed in to change notification settings - Fork 0
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
Ingest MOHC documents #2
Comments
Excellent, thank you! |
@piotr-florek-mohc This morning I processed the MOHC documents. Looks pretty good except for the 'meta' section - when creating the documents using the pyesdoc.create function can you please specify the following input parameters:
|
@piotr-florek-mohc I manually copied the files within the submission folder and made the above changes for testing purposes. I then published the documents to our TEST server - you can review: https://test-search.es-doc.org/?project=cmip6&documentType=cim.2.science.Model |
@momipsl Thank you, I just updated the metadata fields. There will be some minor tweaks and corrections coming once we've completed the review, so I'll just update the branch and let you know when it's done. Also, later this month I will prepare another submission for UKESM1 model. |
@davidhassell and I have been reviewing the MOHC documents. We note that the level of publishing granularity is: one CIM document per model per realm + one CIM document per model/top level. How easy would it be for you to alter the publication granularity to output simply a single (v. large) document per model ? |
@momipsl That's not a problem at all. I have just updated our submission branch. |
I have also commited our second model (UKESM1), plus did some small tweaks to the HadGEM3 document (amending the name of the orca grid version we use). |
@piotr-florek-mohc will look at this either later today or tomorrow morning |
@momipsl did you have a chance to check our submission? |
@piotr-florek-mohc Am creating this issue so that we can track progress. I want to publish the MOHC documents upon our TEST server in readiness for a deployment to our PROD server either next week or the week after.
The text was updated successfully, but these errors were encountered: