id
without url?
#1077
-
In the mindset of maximizing compatibility with datacite, Would it make sense to also make this the recomendation for |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
The difference is that DataCite can indicate the identityType, while Data Package cannot: <identifier identifierType="DOI">10.21384/foo</identifier> Vs: "id": "10.21384/foo" So parsers of DataCite metadata know that the identifier is a DOI, while Data Package parsers don’t (and guessing is tricky). I therefore prefer the full resolved DOI, which is also the recommended format by CrossRef: "id": "https://doi.org/10.21384/foo" Now parsers can recognize this as a doi (and URl) and conversion to and from DataCite is easy. |
Beta Was this translation helpful? Give feedback.
The difference is that DataCite can indicate the identityType, while Data Package cannot:
Vs:
So parsers of DataCite metadata know that the identifier is a DOI, while Data Package parsers don’t (and guessing is tricky). I therefore prefer the full resolved DOI, which is also the recommended format by CrossRef:
Now parsers can recognize this as a doi (and URl) and conversion to and from DataCite is easy.