-
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-AMENDMENT_GEOGRAPHY_STANDARDIZED #118
Comments
This needs to be worked on with #95 further before becoming a core test. |
This is the only test that we have an AMENDMENT_...STANDARDIZED without a corresponding VALIDATION..._NOTSTANDARD. In this case we decided it was too difficult to implement the VALIDATION. However, does this mean we need some sort of prerequisite to say that one or more of the administrative geographic terms (dwc:continent, dwc:country, dwc:countryCode, dwc:stateProvince, dwc:county, dwc:municipality) is not standard? |
We do appear to need at least one equivalent validation. John? |
I concur a matching validation/problem is needed. The Kurator workflow listed in link to source code is actually an implementation of such a problem finder. There is a Kurator workflow that matches this test as currently phrased as an amendment: https://github.com/kurator-org/kurator-validation/blob/master/packages/kurator_dwca/workflows/dwca_geography_cleaner.yaml |
I've added a matching validation/problem for discussion as #139. I'm not convinced by the discussion we had in Gainesville that it is too difficult to implement a matching validation, as both validation and amendment have implementations in the wild (in VertNet, and code from VertNet ported into Kurator). |
Excluding waterBody and including Continent raises a host of issues. The current text references "administrative geographic terms", but dwc:continent isn't a administrative/political term in the same way that the other listed terms (dwc:country, dwc:countryCode, dwc:stateProvince, dwc:county, dwc:municipality) are. Material from offshore but within some country's EEZ would be expected to have a value for dwc:country but none for dwc:continent, and would be distinguished from non-marine material from the same country by the values of waterBody and continent. As an amendment, this test could all to easily incorrectly propose filling in continent in such a case. Also, some places have multiple competing opinions about continental placement. VertNet places Hawaii in Oceania, but the Getty Thesaurus places it in North and Central America, with an alternative placement in Oceania. http://www.getty.edu/vow/TGNFullDisplay?find=Hawaii&place=&nation=&prev_page=1&english=Y&subjectid=7007249 We might be safer limiting this core test to just country to municipality terms, and having another test to look at water bodies, islands, etc. We skipped marine hierarchies in Gainesville, but that is something the OBIS team should probably weigh in on. |
Thanks @chicoreus. I bow to those of us with greater experience. "Target authority" here is significant. |
Looks like you have a way of validating @chicoreus. I think we could go ahead with #139 unless @tucotuco has some further objections. And agreed with waterbodies and marine |
I suggest the Expected Response: 'EXTERNAL_PREREQUISITES_NOT_MET if the bdq:sourceAuthority is not available or if the combination of the values of dwc:continent, dwc:country, dwc:countryCode, dwc:stateProvince, dwc:county, dwc:municipality could not be unambiguously resolved from the bdq:sourceAuthority; AMENDED if the values of dwc:continent, dwc:country, dwc:countryCode, dwc:stateProvince, dwc:county, dwc:municipality could be unambiguously interpreted from values in bdq:sourceAuthority; otherwise NOT_AMENDED' in place of: 'EXTERNAL_PREREQUISITES_NOT_MET if the bdq:sourceAuthority is not available or if the combination of the values of dwc:continent, dwc:country, dwc:countryCode, dwc:stateProvince, dwc:county, dwc:municipality could not be unambiguously resolved from the bdq:sourceAuthority; AMENDED the values of dwc:continent, dwc:country, dwc:countryCode, dwc:stateProvince, dwc:county, dwc:municipality if could be unambiguously interpreted from values in bdq:sourceAuthority; otherwise NOT_AMENDED' |
78640f09-8353-411a-800e-9b6d498fb1c9 duplicates #95, replacing with ba2d868c-afa3-409a-836b-fdcea9f75945 |
@tucotuco: Seems to me that there is redundancy. Why not simply 'EXTERNAL_PREREQUISITES_NOT_MET if the bdq:sourceAuthority is not available; AMENDED if the values of dwc:continent, dwc:country, dwc:countryCode, dwc:stateProvince, dwc:county, dwc:municipality could be unambiguously interpreted from values in bdq:sourceAuthority; otherwise NOT_AMENDED' ? If the ER as you had it was not able to be ambiguously resolved against the source authority, you would have EXTERNAL_PREREQUISITES_NOT_MET, which doesn't seem appropriate given the context of other tests. |
The zoom discussion with @ArthurChapman, @tucotuco and @chicoreus today concluded that tests #95, #139 and #118 were going to be very difficult to implement properly given the lack of a consistent geographic terms hierarchy by comparison with the taxonomic terms. Note the issues arising from the table above for example. We will therefore remove these tests from CORE. In their place, we will
|
Changed Field to TestField, added ActedUpon/Consulted, added date specification last modified. |
Changed "Output Type" to TestType |
@Tasilee - I thought this was a DO NOT IMPLEMENT rather than Supplementary given our definitions. |
Specifications updated to align with the current template |
The text was updated successfully, but these errors were encountered: