-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TG2-VALIDATION_INFRASPECIFICEPITHET_NOTEMPTY #219
Comments
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. |
…tdwg/bdq#220 tdwg/bdq#219 and tdwg/bdq#218 more not empty tests, including bugfix in utility method to evaluate ordering of pairs of rank values, bugfixes to multiple tests that check a higher classification term and the rank, and unit tests.
The text was updated successfully, but these errors were encountered: