E3SM-Project / E3SM-Project/datasm

Warehouse State-Machine Does Not Accommodate CMIP6 Dataset Versioning

Open
#89 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
0
Forks
2
PR merge metrics
No merged PRs in 30d

Description

The existing warehouse state-machine codes enforce "automatic publication versioning" (initial publication is "v1", subsequent publications are automatically incremented) which is inappropriate for CMIP6-style "version-dates", and likewise cannot accommodate forcing a version for a publication. CMIP6 datasets are "born with" author-supplied versions, whereas E3SM datasets are not.

Presently, most all CMIP6 publication actions must be handled "Out Of Warehouse" (state-machine).

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.