@sethmcg , to be fair, what I suggested was the DOI way of doing it. But even without the version level DOI, it is possible to have reproducibility if in the bibliography list the tag version (tagged commit on git) is included. This is a common solution for datasets, but the downloading date is used instead of a tag. In summary, it is not perfect but reproducibility is still possible without the third level - a DOI per version.
Thanks @zklaus . To clarify, if using Zenodo, the DOIs (B) and (C) would be the automatic "DOI representing all of the versions on your record", that you mentioned. It is nice that we now can choose Zenodo to archive only the PDF or something else. I didn't know that. I think that is an important information for the decision on which path to go. Thanks! -- 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-934523533__;Iw!!G2kpM7uM-TzIFchu!hbdes1diqhwQ1wq7B4d7CJ70bmQGP_Yhh4EZuN4uv1rE58jrzdnWpTm0e8THNh5QqvaCpSG96eE$ 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].
