Closed gothub closed 4 years ago
Same or similar to deployed check: check.temporal.coverage.1.
What about dates provided in standard format?
I would argue that is a separate check, especially as there is no universal format that all countries and disciplines use. For datasets in modern times, an ISO 8601-compatible date might be preferred. This is typically enforced in some XML schemas. For geologic-scale temporal coverages, there are many more valid formats in widespread use, including various estimates of years before present and various named stratigraphic systems, among others.
Yes, it makes sense to be a separate interoperability check.
On Wed, Jul 31, 2019 at 4:30 PM Matt Jones notifications@github.com wrote:
I would argue that is a separate check, especially as there is no universal format that all countries and disciplines use. For datasets in modern times, an ISO 8601-compatible date might be preferred. This is typically enforced in some XML schemas. For geologic-scale temporal coverages, there are many more valid formats in widespread use, including various estimates of years before present and various named stratigraphic systems, among others.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/NCEAS/metadig-checks/issues/94?email_source=notifications&email_token=ALKVICSEQIN6PACVBVRG3PDQCIOBJA5CNFSM4H2U6MK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3I3IVQ#issuecomment-517059670, or mute the thread https://github.com/notifications/unsubscribe-auth/ALKVICVK763VY5XJJ2ACAPDQCIOBJANCNFSM4H2U6MKQ .
The target for this check exists in the DataCite Dialect: data.attributes.dates[?(@.dateType="Collected")].date
A date range is specified as YYY-MM-DD/YYYY-MM-DD, i.e. 2012-03-01/2012-03-05
Description
Check if a temporal extent is present
Priority
Issues
Procedure