search

tdwg / bdq

Biodiversity Data Quality (BDQ) Interest Group
https://github.com/tdwg/bdq
42 stars 7 forks source link

TG2-VALIDATION_SUBTRIBE_FOUND #208

Closed chicoreus closed 9 months ago

chicoreus commented 1 year ago
TestField Value
GUID 4527c47e-61d9-4abb-af3e-f2999191be17
Label VALIDATION_SUBTRIBE_FOUND
Description Does the value of dwc:subtribe occur at rank of Subtribe in bdq:sourceAuthority?
TestType Validation
Darwin Core Class Taxon
Information Elements ActedUpon dwc:subtribe
Information Elements Consulted
Expected Response EXTERNAL_PREREQUISITES_NOT_MET if the bdq:sourceAuthority is not available; INTERNAL_PREREQUISITES_NOT_MET if dwc:subtribe is bdq:Empty; COMPLIANT if the value of dwc:subtribe is found as a value at the rank of subtribe in the bdq:sourceAuthority; otherwise NOT_COMPLIANT
Data Quality Dimension Conformance
Term-Actions SUBTRIBE_FOUND
Parameter(s) bdq:sourceAuthority
Source Authority bdq:sourceAuthority default = "GBIF Backbone Taxonomy" [https://doi.org/10.15468/39omei]
API endpoint [https://api.gbif.org/v1/species?datasetKey=d7dddbf4-2cf0-4f39-9b2a-bb099caae36c&name=]
Specification Last Updated 2023-09-22
Examples [dwc:subtribe="Malinae": Response.status=RUN_HAS_RESULT, Response.result=COMPLIANT, Response.comment="dwc:subtribe has an equivalent at the rank of Subtribe in the bdq:sourceAuthority"]
[dwc:subtribe="Metazoa": Response.status=RUN_HAS_RESULT, Response.result=NOT_COMPLIANT, Response.comment="dwc:subtribe does not strictly have an equivalent at the rank of Subtribe in the bdq:sourceAuthority"]
Source
References
Example Implementations (Mechanisms) Kurator/FilteredPush sci_name_qc Library
Link to Specification Source Code https://github.com/FilteredPush/sci_name_qc/blob/v1.1.2/src/main/java/org/filteredpush/qc/sciname/DwCSciNameDQ.java#L3686
Notes The purpose of this test is to check whether the value is a name that is a result of a nomenclatural act at this rank. This excludes unpublished names, misspellings and vernacular names. The same test might return distinct results when using distinct source authorities. 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.
chicoreus commented 1 year ago

Needs review. Parallels other validations that evaluate single higher rank terms. Entailed by https://github.com/tdwg/dwc/issues/46

chicoreus commented 1 year ago

After discussion in TG2, marking this as NOT CORE. This is the position we have taken for similar tests for other sub/super ranks.

Also, appears that a current implementation against the desired default bdq:sourceAuthority of GBIF's backbone taxonomy would return NOT_COMPLIANT for any non-empty dwc:subtribe values, as GBIF does not appear to have subtribe data in the backbone taxonomy.

chicoreus commented 1 year ago

See: https://github.com/tdwg/bdq/issues/206#issuecomment-1619276874

ArthurChapman commented 1 year ago

Splitting Information Elements into "Information Elements ActedUpon" and "Information Elements Consulted".

Changed "Field" to "TestField", "Output Type" to "TestType" and updated "Specification Last Updated" deleted "Warning Type"