Markus Döring

We actually try to catch those by merging all accepted genera from the same source that have the same parent, e.g. family. Homonyms can exist across distant parts of the...

The new backbone treats it fine again: http://backbonebuild-vh.gbif.org:9000/species/match?verbose=true&name=Hyla

adding a language filter is rather simple, but partial matches are basically a new suggest search requiring different indices

I don't quite see how to solve this better. The behavior is expected and the same as we deal with Linnean names. What else would you expect? Synonyms of names...

Oh, I agree with that and are surprised the behavior is different. This should be addressed in the next update for sure!

Moss names in the Catalogue of Life have not been updated since 2004. We are about to update them from [Bryonames](https://www.bryonames.org) which is already available in ChecklistBank: https://www.checklistbank.org/dataset/170394/about

This unfortunately won't make it into the new GBIF backbone we are releasing as I type.

there is source for confusion here: "verbatim_scientificName": "Sedum rupestre L., 1753 [nom. et typ. cons.]", "current_scientificName": "Sedum rupestre Vill., 1789", "proposed_scientificName": "Sedum rupestre Hacq. ex Nyman, 1879", 4 species in...

Postgres data has been successfully removed, it is just in Elastic now

There is indeed no invasive field in the [SpeciesProfile class](https://github.com/gbif/gbif-api/blob/dev/src/main/java/org/gbif/api/model/checklistbank/SpeciesProfile.java#L29) that backs this service. Seems to be an oversight not discovered for a decade :)