Open thomasstjerne opened 3 years ago
The species pair above is indeed problematic since the page display on GBIF becomes L. juvernica instead of the species pair. Because L. juvernica comes first of the two (juvernica/sinapis), the searches will seem to overrepresent juvernica (the rarer of the two) https://www.gbif.org/occurrence/2622082436. It nicely highlights the need for proper handling of aggregates
For the Swedish Butterfly Monitoring Scheme SEBMS, this represents 1008 entries for the years 2010-2019 that "look" like juvernica https://www.gbif.org/occurrence/search?q=6006844&dataset_key=be77e203-486c-4651-91b9-8347968b728c&advanced=1
UPDATE: ah, i see that that was the cause of the original https://github.com/gbif/portal-feedback/issues/2935 . With our data, it happens quite massively and I believe some other BMS have decided to keep the aggregates outside GBIF instead of uploading them with the rest of the data (which is a pity)
See: https://github.com/gbif/portal-feedback/issues/2935
Suggest to display the verbatim name on species pages and in tables, like we do with fuzzy taxon matches.
Example of species pair: https://www.gbif.org/occurrence/2622082436 Example of s. lato : https://www.gbif.org/occurrence/2238565917