Closed ahahn-gbif closed 1 year ago
Agree this is unfortunate: http://backbonebuild-vh.gbif.org:9000/species/match2?verbose=true&name=Carex%20vulpina%20agg.
Sth odd with the aggregate matching, which is supposed to ignore the species and try the next higher level - Carex in this case. Which should yield a plant genus match: http://backbonebuild-vh.gbif.org:9000/species/match2?verbose=true&name=Carex
Cant say whats going wrong here
As would http://backbonebuild-vh.gbif.org:9000/species/match2?verbose=true&name=Carex%20vulpina - is "agg." recognized as a term to omit when matching (or would that even make sense)?
We explicitly did not want to match to the species in case of aggregates and had users complaining about that: https://github.com/gbif/portal-feedback/issues/4459
This happens because we remove the exact matches due to the aggregate, but leave in the fuzzy ones. I will change the code so we also ignore any fuzzy matches in case we removed exact matches due to the aggregate rank
Now matching at genus level with full higher taxonomy of the correct group (Cyperaceae), http://backbonebuild-vh.gbif.org:9000/species/match2?verbose=true&name=Carex%20vulpina%20agg.
matches now correctly to higher genus: http://backbonebuild-vh.gbif.org:9000/species/match2?verbose=true&name=Carex%20vulpina%20agg.
Similar to #272, a plant (Carex vulpina agg.) mapped into butterflies due to name similarity (Carea vulpina Warren, 1912) plus missing higher taxonomy