bdq
bdq copied to clipboard
tdwg
TG2-VALIDATION_INFRASPECIFICEPITHET_NOTEMPTY
| TestField | Value |
|---|---|
| GUID | 77c6fde2-c3ca-4ad3-b2f2-3b81bba9a673 |
| Label | VALIDATION_INFRASPECIFICEPITHET_NOTEMPTY |
| Description | Is there a value in dwc:infraspecificEpithet? |
| TestType | Validation |
| Darwin Core Class | Taxon |
| Information Elements ActedUpon | dwc:infraspecificEpithet |
| Information Elements Consulted | |
| Expected Response | INTERNAL_PREREQUISITES_NOT_MET if dwc:infraspecificEpithet is EMPTY and dwc:taxonRank contains a value that is not interpretable as a taxon rank; COMPLIANT if dwc:infraspecificEpithet is not EMPTY, or dwc:infraspecificEpithet is EMPTY and the value in dwc:taxonRank is higher than infraspecific epithet; otherwise NOT_COMPLIANT. |
| Data Quality Dimension | Completeness |
| Term-Actions | INFRASPECIFICEPITHET_NOTEMPTY |
| Parameter(s) | |
| Source Authority | |
| Specification Last Updated | 2024-06-05 |
| Examples | [dwc:infraspecificEpithet="noidea": Response.status=RUN_HAS_RESULT, Response.result=COMPLIANT, Response.comment="dwc:infraspecificEpithet is not EMPTY"] |
| [dwc:infraspecificEpithet="": Response.status=RUN_HAS_RESULT, Response.result=NOT_COMPLIANT, Response.comment="dwc:infraspecificEpithet is 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 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. |
This test very much calls out for examination of dwc:taxonRank as noted in #214. Any occurrences identified to the rank of species or above will correctly have dwc:infraspecificEpithet as empty, similarly for Taxon records in checklist data. This test, as is, will call out very large numbers of correct records as unfit for use. All of the tests listed in #214 suffer from this problem, but it is most egregious here and in the related but more complex problem in #265.
@chicoreus - I agree, with 1.5% GBIF records and 2.3% ALA records having NOTEMPTY, and the argument for the complexity in having to include other terms for utility suggests Immature/Incomplete?
Is the concept of the test informative (enough) either way (=Supplementary)? Is there a rational use case?
What do others think?
Agree with @chicoreus - I guess it still NEEDS WORK and is Immature/Incomplete as is.
Changed Expected Response from
COMPLIANT if dwc:infraspecificEpithet is not EMPTY; otherwise NOT_COMPLIANT
to
INTERNAL_PREREQUISITES_NOT_MET if dwc:infraspecificEpithet is EMPTY and dwc:taxonRank contains a value that is not interpretable as a taxon rank; COMPLIANT if dwc:infraspecificEpithet is not EMPTY, or dwc:infraspecificEpithet is EMPTY and the value in dwc:taxonRank is higher than infraspecific epithet; otherwise NOT_COMPLIANT.