Use GBIF taxon keys of accepted taxa even if synonyms occur in specie list
damianooldoni opened this issue · 3 comments
As discussed in riparias/riparias-target-list#23, we have two synonyms in the RIPARIAS target species list due to some changes in the GBIF Backbone. We agreed in that issue to:
- stick with scientific name of the synonyms in the user interface as those names are the ones everybody in BE is used to at the moment
- use the GBIF taxon key of the accepted taxon to get all occurrences in case someone starts to use the accepted taxon or other synonyms
Notice that the checks of new synonyms or other changes due to new versions of the GBIF Backbone are now operational via https://github.com/riparias/taxon-keys-early-alert
Based on riparias/riparias-target-list#23 (confirmed by workflow in https://github.com/riparias/taxon-keys-early-alert), I have changed the GBIF taxon key associated to Egeria densa and Heracleum sosnowskyi in DEV. I don't expect dramatic changes in the occurrence download, but I think it's better to get this checked on dev before moving to production.
By running the checks on dev species list, I have just noticed that species list on dev version contains two errors:
- Hydrocotyle ranunculoides was still linked to 7978544 which was deleted from the Backbone in Nov 2022
- Heracleum persicum was still linked to 8000520 which is a synonym of another taxon, sharing the same canonical name, but other authorship
I updated these two and tomorrow we will see these changes on dev as well.
As expected the change of the taxon keys of Egeria densa and H. sosnowkyi to the ones of the correspondent accepted taxa worked well and no new obs have been added. The many new imported observations are all related to Hydrocotyle ranunculoides which has indeed a new taxon key.
I am going to apply the taxon changes of Egeria densa and Heracleum sosnowskyi in production before new import this night.