Hi all - I was wrong about the ability to change the URL resolved to by a Zenodo DOI. It always points to the corresponding Zenodo archive page. Which makes sense given Zenodo is a repository and not just a DOI minting service.
Hi @castelao - I agree, using the Zenodo/GitHub integration would be much easier in terms of the effort involved in minting and maintaining CF DOIs. On the other hand, using a separate DOI registry service would allow the DOIs to resolve directly to CF pages rather than to the Zenodo archive of the GitHub repository. So the main CF DOI could resolve to the main CF web site (https://urldefense.us/v3/__https://cfconventions.org/__;!!G2kpM7uM-TzIFchu!l_DiLZgFHnLFdjFcrmbdMSgvEvqSsCsy2g8IQNG1Guy3-tAyLWRG0GR5T58ubFkhyMwTnJO5Ga8$ ) and the version DOIs could resolve to the individual CF version pages (e.g., https://urldefense.us/v3/__https://cfconventions.org/Data/cf-conventions/cf-conventions-1.8/cf-conventions.html__;!!G2kpM7uM-TzIFchu!l_DiLZgFHnLFdjFcrmbdMSgvEvqSsCsy2g8IQNG1Guy3-tAyLWRG0GR5T58ubFkhyMwTzYLBUFM$ ). The Zenodo DOI metadata can contain related identifiers/URLs which could reference the appropriate CF website page(s). So, with either method, dereferencing DOIs from a citation will lead to the CF content, it will just be an extra step or two with a Zenodo generated DOI. Perhaps a conversation for the CF Workshop? -- 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-914668372__;Iw!!G2kpM7uM-TzIFchu!l_DiLZgFHnLFdjFcrmbdMSgvEvqSsCsy2g8IQNG1Guy3-tAyLWRG0GR5T58ubFkhyMwT4WaIRhw$ 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].
