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

This is a chrysomelid as indicated, not a megachilid. #2930

Closed
gbif-portal opened this issue Aug 5, 2020 · 5 comments
Closed

This is a chrysomelid as indicated, not a megachilid. #2930

gbif-portal opened this issue Aug 5, 2020 · 5 comments
Assignees
Labels
backbone interpretation Interpretation issues, probably should wait to be solved in Pipelines

Comments

@gbif-portal
Copy link
Collaborator

This is a chrysomelid as indicated, not a megachilid.


Github user: @dshorthouse
User: See in registry
System: Chrome 84.0.4147 / Mac OS X 10.15.6
Referer: https://www.gbif.org/occurrence/658264657
Window size: width 1453 - height 792
API log
Site log
System health at time of feedback: OPERATIONAL
datasetKey: aae308f4-9f9c-4cdd-b4ef-c026f48be551
publishingOrgKey: b554c320-0560-11d8-b851-b8a03c50a862

@ManonGros
Copy link

It seems like the issue has to do with a missing name in the taxonomy. The Backbone doesn't contain Stolas costaricensis: https://www.gbif.org/species/search?q=Stolas%20costaricensis

@ahahn-gbif
Copy link

ahahn-gbif commented Aug 25, 2021

This is a taxon matching issue, similar to #3360 and #3110.

Propose: If a genus name exists that is identical with the verbatim genus name, and in the same family as given in the verbatim data, but the species name not available in the backbone, then taxon matching should match the name to the higher rank (genus), and not attempt to fuzzy-match it to a different genus name in a different family, even if the genus-epithet combination is similar.

@mdoering does this make sense, and is it doable, or is the extension of taxon data resources the only way to prevent this type of matching error?

@ahahn-gbif ahahn-gbif added interpretation Interpretation issues, probably should wait to be solved in Pipelines and removed data content labels Aug 25, 2021
@mdoering
Copy link
Member

This is doable, but a major change in how we match with potential changes all over. It might be all good changes though, I like the proposal. The only weak part is "if the verbatim family matches". Do we require a family to be present and match? What if there is only an order given? I guess sticking with just family initially safe guards us from unwanted side effects

@ahahn-gbif
Copy link

The only weak part is "if the verbatim family matches".

Right... might better be formulated along the lines of "if the next higher taxonomic rank given matches". The main point I was trying to make here was rather from the opposite angle: if the next higher rank of the proposed fuzzy match contradicts the one in the verbatim data, then do not fuzzy-match, and rather match upwards in taxonomic rank with the same spelling and higher taxonomy

@mdoering
Copy link
Member

Agree, thats a more robust logic!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backbone interpretation Interpretation issues, probably should wait to be solved in Pipelines
Projects
None yet
Development

No branches or pull requests

4 participants