Tasilee
commented
9 months ago | TestField | Value |
|---|---|
| GUID | aaebbde6-a101-4665-ba1e-6d4d8c561a31 |
| Label | VALIDATION_EVENTTIME_NOTEMPTY |
| Description | Is there a value in dwc:eventTime? |
| TestType | Validation |
| Darwin Core Class | Time |
| Information Elements ActedUpon | dwc:eventTime |
| Information Elements Consulted | |
| Expected Response | COMPLIANT if dwc:eventTime is bdq:NotEmpty; otherwise NOT_COMPLIANT |
| Data Quality Dimension | Completeness |
| Term-Actions | EVENTTIME_NOTEMPTY |
| Parameter(s) | |
| Source Authority | |
| Specification Last Updated | 2024-02-07 |
| Examples | [dwc:eventTime="13:00:00Z/15:30:00Z": Response.status=RUN_HAS_RESULT, Response.result=COMPLIANT, Response.comment="dwc:eventTime is bdq:NotEmpty"] |
| [dwc:eventTime="": Response.status=RUN_HAS_RESULT, Response.result=NOT_COMPLIANT, Response.comment="dwc:eventTime is bdq:Empty"] | |
| Source | TG2 |
| References | |
| Example Implementations (Mechanisms) | |
| Link to Specification Source Code | |
| Notes | This bdq:Supplementary test is not regarded as CORE (cf. bdq:CORE) because assessment of dwc:eventTime is out of scope for the CORE use case, where temporal resolution is only considered down to the resolution of approximately one day. Time is often known for observational occurrence data, but very seldom recorded for vouchered specimen data. This test has significant value for research and other uses of observational data. Any analysis of time data needs to be very cognizant of substantial problems related to temporal data of which time zones are just the tip of the iceberg, see: https://xkcd.com/2867/ |
| Time is of one or more of the reasons: not being widely applicable; not informative; not straightforward to implement or likely to return a high percentage of either bdq:COMPLIANT or bdq:NOT_COMPLIANT results (cf bdq:Response.result). A Supplementary test may be implemented as CORE when a suitable use case exists. |
chicoreus