bdq
bdq copied to clipboard
TG2-VALIDATION_EVENTDATE_NOTEMPTY
TestField | Value |
---|---|
GUID | f51e15a6-a67d-4729-9c28-3766299d2985 |
Label | VALIDATION_EVENTDATE_NOTEMPTY |
Description | Is there a value in dwc:eventDate? |
TestType | Validation |
Darwin Core Class | dwc:Event |
Information Elements ActedUpon | dwc:eventDate |
Information Elements Consulted | |
Expected Response | COMPLIANT if dwc:eventDate is bdq:NotEmpty; otherwise NOT_COMPLIANT |
Data Quality Dimension | Completeness |
Term-Actions | EVENTDATE_NOTEMPTY |
Parameter(s) | |
Source Authority | |
Specification Last Updated | 2023-09-17 |
Examples | [dwc:eventDate="1964-11-01T10:00-0600": Response.status=RUN_HAS_RESULT, Response.result=COMPLIANT, Response.comment="dwc:eventdate is bdq:NotEmpty"] |
[dwc:eventDate="": Response.status=RUN_HAS_RESULT, Response.result=NOT_COMPLIANT, Response.comment="dwc:eventDate is bdq:Empty"] | |
Source | TG2-Gainesville |
References | |
Example Implementations (Mechanisms) | Kurator/FilteredPush event_date_qc Library 10.5281/zenodo.596795. |
Link to Specification Source Code | event_date_qc v3.0.5 DwCEventDQ.validationEventdateNotEmpty() |
Notes |
Comment by Lee Belbin (@Tasilee) migrated from spreadsheet: Added post scoring for completeness
Noting for cross reference that we previously had a corresponding measure EVENT_DATE_COMPLETENESS 0a59e03f-ebb5-4df3-a802-2e444de525b5.
This test is a prerequisite for amendments #61, #86, #93, #132 - if these amendments are run and fail, then eventDate would still be empty, and thus on the re validation, this test will remain an important test.
Splitting bdqffdq:Information Elements into "Information Elements ActedUpon" and "Information Elements Consulted"