It's great to hear that there is interest! My understanding from the comments is that we agree that CF conventions should have a DOI and the standard names should also have a DOI. It sounds like a good idea since the standard names table will probably be updated more frequently than the CF-convention itself. Also, it is expected that both will keep backward cross-compatible.
@ngalbraith, most of the agencies that register DOIs already take care of copying and making that available. So we most probably won't need to deal with that. Independent of that, GitHub also provides that frozen version once we create tags. Yes @ethanrd , Zenodo has an overarching DOI which can be used when someone wants to mention CF in a generic way. That DOI always points to the latest version. Another case is when a specific version is required, thus the specific version DOI is used. If the idea was to use an overarching DOI for the conventions and the standard names, I don't think that will be straightforward with Zenodo, but I don't think that would be a problem. I suggest two possible paths to record the DOI, which will determine a little the dynamic and maintenance. In summary, Zenodo is the least effort since we are already using GitHub. It would be pretty much automatic once we set up everything. The other alternative is through the University of California Library, which would require some manual steps but we would have more freedom to do as we want (potentially taking more advantage of the flexibility of the DOI standard). I use the UC Library to handle datasets at Scripps Institution of Oceanography, and use Zenodo for my open source projects. I don't have a clear opinion on what would be best for CF. I guess that if the standard Zenodo is fine for you all, it would be the easiest to maintain. There are some tricks to control Zenodo. Check this [https://urldefense.us/v3/__https://github.com/castelao/inception*(https:/*github.com/castelao/inception)__;XS8!!G2kpM7uM-TzIFchu!iC35vlQDr-XmhW_2cL8ahAATT94Msp56Z9Qt5AW062_f1ehWPsk3wzmKHVdQCsKmA5TdG4QFaaI$ . By using this .zenodo.json we can, for instance, cross-link the conventions with the standard name, plus any other relevant publication. Zenodo takes some information from the repository automatically, but it is limited, which can be resolved by defining a .zenodo.json . Note that: - The version DOI: https://urldefense.us/v3/__https://zenodo.org/record/3986146__;!!G2kpM7uM-TzIFchu!iC35vlQDr-XmhW_2cL8ahAATT94Msp56Z9Qt5AW062_f1ehWPsk3wzmKHVdQCsKmA5TdyLKSeao$ - A previous version DOI: https://urldefense.us/v3/__https://zenodo.org/record/3986145__;!!G2kpM7uM-TzIFchu!iC35vlQDr-XmhW_2cL8ahAATT94Msp56Z9Qt5AW062_f1ehWPsk3wzmKHVdQCsKmA5TdwWXEVFw$ - The overarching DOI (points to the latest version. Useful to aggregate citations): https://urldefense.us/v3/__https://doi.org/10.5281/zenodo.3981501__;!!G2kpM7uM-TzIFchu!iC35vlQDr-XmhW_2cL8ahAATT94Msp56Z9Qt5AW062_f1ehWPsk3wzmKHVdQCsKmA5Tdi3WF1vY$ Whatever path is decided, we will need some information in anyways, such as the list at [https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/127*issuecomment-432292340__;Iw!!G2kpM7uM-TzIFchu!iC35vlQDr-XmhW_2cL8ahAATT94Msp56Z9Qt5AW062_f1ehWPsk3wzmKHVdQCsKmA5TdcrGtFUs$ ](https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/127*issuecomment-432292340__;Iw!!G2kpM7uM-TzIFchu!iC35vlQDr-XmhW_2cL8ahAATT94Msp56Z9Qt5AW062_f1ehWPsk3wzmKHVdQCsKmA5TdcrGtFUs$ ). Is the list of authors correct and complete? It's missing some ORCIDs. What would be the list of contributors? Not only people, but also institutions and agencies. A note, all this metadata can be edited, expanded, and fixed later. Let me know your questions. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/127*issuecomment-914626649__;Iw!!G2kpM7uM-TzIFchu!iC35vlQDr-XmhW_2cL8ahAATT94Msp56Z9Qt5AW062_f1ehWPsk3wzmKHVdQCsKmA5TdD6_1aGQ$ This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
