Species Lookup Tool

[gbif-portal]

Species Lookup Tool

I don't know whether this is a cataloguing issue or a problem with the Species Lookup Tool itself, but I've noticed some records return a "Higher Rank" match in preference to a "Synonym" match. For example, my data includes "Pithecopus azureus". When this data is passed through the Species Lookup Tool, the normalized result returns the genus Pithecopus as an accepted higher rank. However, I expect this record actually refers to "Phyllomedusa azurea" which is an accepted species (and previously classified as Pithecopus azureus).

---

User: See in registry System: Chrome 75.0.3770 / Windows 10.0.0 Referer: https://www.gbif.org/tools/species-lookup Window size: width 1920 - height 969 API log&_a=(columns:!(_source),index:'prod-varnish-',interval:auto,query:(query_string:(analyze_wildcard:!t,query:'response:%3E499')),sort:!('@timestamp',desc))) Site log&_a=(columns:!(_source),index:'prod-portal-',interval:auto,query:(query_string:(analyze_wildcard:!t,query:'response:%3E499')),sort:!('@timestamp',desc))) System health at time of feedback: OPERATIONAL

[MortenHofft]

The tool is simply intended as an easy way to get started with the APIs. It is really just doing a bunch of calls to our public APIs. In this case the match api documented here https://www.gbif.org/developer/species

http://api.gbif.org/v1/species/match?name=Pithecopus%20azureus&verbose=true

The API is, as you say, returning the genus Pithecopus. If this is incorrect, then the issue is likely to be our backbone that do not know the synonym.

[yroskov]

Irrelevant to CoL.

[ManonGros]

Does this mean that Pithecopus azureus should be added as a synonym of Phyllomedusa azurea?

[jhnwllr]

I am closing this issue because it does not really seem actionable. Matching higher rank happens when we don't have the taxa in the backbone.