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_MONTH_NOTEMPTY #241

Closed
Tasilee opened this issue Feb 3, 2024 · 3 comments
Closed

TG2-VALIDATION_MONTH_NOTEMPTY #241

Tasilee opened this issue Feb 3, 2024 · 3 comments
Labels
CODED Completeness 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 TIME Validation

Comments

@Tasilee
Copy link
Collaborator

Tasilee commented Feb 3, 2024

TestField Value
GUID dc2fc946-8114-491b-8a7b-3242a274a221
Label VALIDATION_MONTH_NOTEMPTY
Description Is there a value in dwc:month?
TestType Validation
Darwin Core Class location
Information Elements ActedUpon dwc:month
Information Elements Consulted
Expected Response COMPLIANT if dwc:month is bdq:NotEmpty; otherwise NOT_COMPLIANT
Data Quality Dimension Completeness
Term-Actions MONTH_NOTEMPTY
Parameter(s)
Source Authority
Specification Last Updated 2024-02-04
Examples [dwc:month="Jan": Response.status=RUN_HAS_RESULT, Response.result=COMPLIANT, Response.comment="dwc:month is bdq:NotEmpty"]
[dwc:month="": Response.status=RUN_HAS_RESULT, Response.result=NOT_COMPLIANT, Response.comment="dwc:month is bdq:Empty"]
Source TG2
References
Example Implementations (Mechanisms) Kurator/FilteredPush event_date_qc Library DOI: 10.5281/zenodo.596795
Link to Specification Source Code https://github.com/FilteredPush/event_date_qc/blob/v3.0.5/src/main/java/org/filteredpush/qc/date/DwCEventDQ.java#L2581
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 Validation TIME 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 labels Feb 3, 2024
@ymgan
Copy link
Collaborator

ymgan commented Feb 5, 2024

I am a little confused. Is this not covered by #88 ?
edit: nevermind, I just noticed that #88 check for any of the temporal fields.

@ArthurChapman
Copy link
Collaborator

No @ymgan #88 is a general "Time" test and asks if there is any Time information - it doesn't ask specifically if dwc:month is empty NOTEMPTY or not

@chicoreus
Copy link
Collaborator

@ymgan #88 is one of a set of three tests that check for any temporal, spatial #40, or scientific name #105 information present in a Darwin Core SingleRecord. Each of those checks the the full set of Darwin Core terms relevant to their scope (time/space/taxon) that we considered to fall within the scope of CORE to see if any information is present. Temporal information is something of a special case in Darwin Core as there are three separate ways of providing a date in structured form (not including verbatim), intended as an aid for mobilization of data from disparate date storage forms. Of these, we test for dwc:year not empty #49, as it is shared by more than one representation, and temporal resolution to a year, regardless of the presence of a value in dwc:eventDate indicates data of use for many of the research cases examined by TG3, thus as an exception to the general pattern we included this test. We consider dwc:eventDate to be the primary term for representation of temporal data, so #33 is the primary not empty test, and we leave out of core other possible not empty tests such as this one.

@Tasilee Tasilee closed this as completed Feb 6, 2024
@chicoreus chicoreus added the CODED label Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CODED Completeness 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 TIME Validation
Projects
None yet
Development

No branches or pull requests

4 participants