Quality Report Check: Existing DOI and Alternate Identifier
emilyarobles opened this issue · 5 comments
Description
Check that existing DOIs and alternate identifiers in the "Alternate Identifier" field resolve to a dataset landing page.
Priority
- FAIR: Optional
Issues
- May only be able to check certain types of identifiers (eg. DOIs)
Procedure
Check that any identifier included in the Alternate Identifiers field resolves correctly to a dataset landing page.
Response for Fail
Warning. The entered DOI is invalid. Enter a valid one or check that it has been reserved.
@emilyarobles is this the same as #60?
Also, is it acceptable to have one check for the metadata id and one for the alternate id?
For ESS-DIVE metadata, i've seen different namespaces such as osti and cdiac. How should these be resolved/checked?
Here is an example:
- osti:139493432
@gothub Yes, I believe that we imagined two separate checks (one for the metadata id and one for the alternate id) which is why I created this issue in addition to #60, which would then be the check for the metadata id.
Are the osti and cdiac examples you are referring to found in the alternate identifier field?
Note that this issue references three other issues that might all be used to fulfill the requirements stated in this current issue:
After reviewing the current ESS-DIVE suite, i see that their is a check to verify that a metadata identifier is specified.
So, I will of course keep that check, but will add an additional check to verity that the identifier resolves.
existing check is 'check.identifier.is.present' (there is no issue for this check).
check to add is metadata.identifier.resolvable