Markus Döring

Matches to the species correctly: http://backbonebuild-vh.gbif.org:9000/species/match2?verbose=true&kingdom=Animalia&phylum=Arthropoda&class=Insecta&order=Coleoptera&family=Ptinidae&genus=Ptilinus&species=fuscus&name=Ptilinus%20fuscus

Indeed. We should probably use the species matching to find out the right genus. Odd though to have a true homonym being accepted, I raise this to COL. The grass...

... which happens because of a Plazi classification, which in turn uses older COL data. These days at least it is considered a grass by COL: https://www.catalogueoflife.org/data/taxon/67GRF @myrmoteras @gsautter this...

Is it the `http://eol.org/schema/media/Document` extension? We only support the GBIF ones so far: https://rs.gbif.org/extension/gbif/1.0/multimedia.xml

hm, probably a previously unknown synonym. Hard to fix. I could hard map it to Fungi?

If you lookup the species directly via the database it still has the taxonID: http://api.gbif.org/v1/species/154667321 This must have happened when we rebuilt the search index while deploying the new backbone...

Understood. This is a bug. Meanwhile you can page through the database like this, even though paging is a terrible thing for accessing all records. This is true for both...

... the limits are there for good reasons :)

@marcos-lg @fmendezh maybe you have an idea why the search is missing the taxonID field? It apparently was there before. The field is in NameUsageSearchResult, but not in NameUsageAvro if...

Makes sense, but I don't feel higher rank match is entirely wrong in these indet. cases. I'll see how I can change it