Skip to content
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_SPECIFICEPITHET_NOTEMPTY #220

Closed
Tasilee opened this issue Jan 28, 2024 · 1 comment
Closed

TG2-VALIDATION_SPECIFICEPITHET_NOTEMPTY #220

Tasilee opened this issue Jan 28, 2024 · 1 comment
Labels
Completeness NAME Supplementary Tests supplementary to the core test suite. These are tests that the team regarded as not CORE. Test Tests created by TG2, either CORE, Supplementary or DO NOT IMPLEMENT TG2 Validation

Comments

@Tasilee
Copy link
Collaborator

Tasilee commented Jan 28, 2024

TestField Value
GUID cdb37443-292e-49b6-a012-4718f0d7ba64
Label VALIDATION_SPECIFICEPITHET_NOTEMPTY
Description Is there a value in dwc:specificEpithet?
TestType Validation
Darwin Core Class Taxon
Information Elements ActedUpon dwc:specificEpithet
Information Elements Consulted
Expected Response INTERNAL_PREREQUISITES_NOT_MET if dwc:specificEpithet is EMPTY and dwc:taxonRank contains a value that is not interpretable as a taxon rank; COMPLIANT if dwc:specificEpithet is not EMPTY, or dwc:specificEpithet is EMPTY and the value in dwc:taxonRank is higher than specific epithet; otherwise NOT_COMPLIANT.
Data Quality Dimension Completeness
Term-Actions SPECIFICEPITHET_NOTEMPTY
Parameter(s)
Source Authority
Specification Last Updated 2024-06-05
Examples [dwc:specificEpithet="noidea": Response.status=RUN_HAS_RESULT, Response.result=COMPLIANT, Response.comment="dwc:specificEpithet is not EMPTY"]
[dwc:specificEpithet="": Response.status=RUN_HAS_RESULT, Response.result=NOT_COMPLIANT, Response.comment="dwc:specificEpithet 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.
@Tasilee Tasilee added TG2 NAME Test Tests created by TG2, either CORE, Supplementary or DO NOT IMPLEMENT Supplementary Tests supplementary to the core test suite. These are tests that the team regarded as not CORE. Completeness Validation labels Jan 28, 2024
@Tasilee Tasilee closed this as completed Feb 4, 2024
@Tasilee
Copy link
Collaborator Author

Tasilee commented Jun 4, 2024

Changed Expected Response from

COMPLIANT if dwc:specificEpithet is not EMPTY; otherwise NOT_COMPLIANT

to

INTERNAL_PREREQUISITES_NOT_MET if dwc:specificEpithet is EMPTY and dwc:taxonRank contains a value that is not interpretable as a taxon rank; COMPLIANT if dwc:specificEpithet is not EMPTY, or dwc:specificEpithet is EMPTY and the value in dwc:taxonRank is higher than specific epithet; otherwise NOT_COMPLIANT.

chicoreus added a commit to FilteredPush/sci_name_qc that referenced this issue Jul 18, 2024
…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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Completeness NAME Supplementary Tests supplementary to the core test suite. These are tests that the team regarded as not CORE. Test Tests created by TG2, either CORE, Supplementary or DO NOT IMPLEMENT TG2 Validation
Projects
Development

No branches or pull requests

1 participant