You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The EML schema clearly specifies the alternate identifier, but it's not clear (to me) what this is for ISO, schema.org, DataCite, so these have to be determined before this check can be included in the FAIR suite.
ESS-DIVE may use this check, possibly in a suite version after 1.1.0. They may have other criteria for the validity of the content that the alternate identifier resolves to, which has yet to be determined, and may warrant an additional check.
@JEDamerow@emilyarobles - you had mentioned that for ESS-DIVE, you manually check '/eml/dataset/alternativeIdentifier' to see if it is resolvable, and then manually check if the web page that is linked to correctly describes the metadata document that is referencing it.
Can any part of this check be automated? This could be split into multiple checks:
this check (metadata.alternateIdentifier.resolvable) verifies the alternateIdentifier is resolvable (this could be used by other repos as well)
another check something about the web page being referred to. I don't know what this would be or what the check would be called.
@gothub We decided that due to variation in how people use this field, and other issues. that we will not include this in the updated suite of checks at this time.
Description
Verify that an alternate identifier associated with the metadata is resolvable.
This check is similar to metadata.identifier.resolvable but for an alternate identifier, not the primary one.
Priority
Issues
Procedure
check if a metadata alternate identifier is present and resolves, and if not then the check fails
The text was updated successfully, but these errors were encountered: