Conversation
|
@znicholls i presume the failing CI are not related, but just to be sure,i ll wait for your confirmation to merge in esgvoc_dev |
Let's remove all the CI files in the |
| { | ||
| "@context": "000_context.jsonld", | ||
| "id": "ceds-cmip-2025-04-18-supplemental", | ||
| "type": "source", |
There was a problem hiding this comment.
These input4MIPs CVs are not like any of the data models in esgvoc. I'm not 100% sure about what to do about this, but I think we might need a new pydantic model, ForcingProvider? It's a mess though, because what input4MIPs calls a source is actually the combination of an organisation and a version (and a whole bunch of other attributes that either need their own CV or esgvoc should just ignore entirely). Maybe that's the best way to represent this?
Categorising these as what esgvoc calls a source is definitely wrong.
No description provided.