@martinjuckes , thanks for raising this point. I think it is a good idea to 
have a description associated with the DOI. To clarify, Zenodo is quite 
convenient and I've been a happy user but the price is that we must conform 
with their resources. A direct DOI registration provides more fields and more 
flexibility for us.

The DOI handle that we see is like a primary key in a database. When we use a 
DOI we are usually interested in the fields associated with that primary key. 
Although one of the DOI fields is the URL for the landing page, the goal is not 
to replace our use of URLs with DOIs. There are several possible fields, but 
the required ones are:

- Location (URL)
- Creators
- Title
- Publisher
- Publication Year
- Resource Type

As suggested by @martinjuckes I strongly recommend adding 'Description' of type 
'abstract'. I also suggest starting with these fields and once we get an 
agreement on those we might consider the rest of the possible list.

Since DOI is meant for machine-to-machine communication, the landing page URL 
is usually a page with human-readable information. I usually use a dedicated 
landing page, brief but with more space than the abstract field, pointing what 
are the resources and where to find them. My suggestion is to use the 
cf-conventions.org as the associated URL for now, and once we concluded the 
requirements we can consider improvements.

-- 
Reply to this email directly or view it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/127*issuecomment-1006690235__;Iw!!G2kpM7uM-TzIFchu!ibY5wKZST_-l8VD9mzfbo8cjV40dWYrPCpsjVgiqbgouwi6tk8loKEg1WbCWvo8IaxzHdNIXad4$
 
You are receiving this because you commented.

Message ID: <cf-convention/cf-conventions/issues/127/[email protected]>
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].

Reply via email to