Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hedera subspecies problem #92

Open
timadriaens opened this issue Jan 8, 2021 · 10 comments
Open

Hedera subspecies problem #92

timadriaens opened this issue Jan 8, 2021 · 10 comments

Comments

@timadriaens
Copy link
Member

Hi, upon wanting to check emergence status of Atlantic ivy (Hedera hibernica), I noticed differences in taxon matching of several datases:

  • Florabank matches with Hedera helix subsp. hibernica (Poit.) D.C.McClint. (gbif key 6307044) - considered a synonym by gbif
  • observations.be matches with Hedera hibernica (G.Kirchn.) Carrière (gbif key 8168344), whereas in obs.be itself the taxon name is Hedera helix subsp. hibernica (Kirchner) McClintock

In GRISS Belgium, there is only Hedera hibernica (G.Kirchn.) Bean (such as in the Manual of Alien Plants) (gbif key 8410115).

Fact: 3 different gbif keys for the same thing. Consequence: the species does not pop up as emerging in the trias indicator flow, whilst probably every field person will say it is clearly emerging.

Solution?

@damianooldoni
Copy link
Contributor

Thanks @timadriaens to pointing out this.

Hedera helix subsp. hibernica (Poit.) D.C.McClint. is a synonym of Hedera hibernica Poit. so this two are by GBIF linked to each other 👍

The only problem is that Hedera hibernica (G.Kirchn.) Bean is not linked to the other two. @qgroom: do you think are there reasons to mention this to GBIF Backbone as an issue as we did in the past (see gbif/backbone-feedback#466)? Obviously this doesn't mean we get an answer fast

@qgroom
Copy link

qgroom commented Jan 20, 2021

We can raise it as an issue. I suspect it will come down to the Catalogue of Life again and getting that changed doesn't seem possible. Nevertheless, never give up never surrender...

@damianooldoni
Copy link
Contributor

@damianooldoni
Copy link
Contributor

It seems that this issue is not an indicators issue in the sense that no one of these three taxa are present in the unified checklist.

While checking the last version of the occurrence cube metadata (be_alientaxa_info.csv) I fond that the only taxon from genus Hedera is Hedera colchica (K.Koch) K.Koch. It means these taxa are not present in any checklist we harvest or they are not taken into account during the process of unifying the cheklists. I will check this right now and I will open in case a new issue in other repo.

@damianooldoni
Copy link
Contributor

damianooldoni commented Feb 17, 2021

I was partly wrong:
Hedera hibernica (G.Kirchn.) Bean is present in the unified checklist.
But there are only 13 occurrences in BE and they are all preserved specimen from botanic garden Meise:
https://www.gbif.org/occurrence/search?country=BE&taxon_key=8410115 without coordinates (!) and 11 have no date even. So, no way they get to indicators. @qgroom: something to check with your colleagues of botanic garden, maybe?

Still, the other two taxa are not in the unified.

@timadriaens
Copy link
Member Author

timadriaens commented Feb 17, 2021

@damianooldoni yes, but the species is much more in the occurrences but under the different names, hence the problem for the indicators...

@timadriaens
Copy link
Member Author

we merged the different dataset to try to build the GAM, see this issue , and if you do that you get of course a different picture of "emergence"

image

@damianooldoni
Copy link
Contributor

Yes, @timadriaens, I agree on this. At the end it's an indicator problem.

But the solution is to get one or both of the taxa 6307044 and 8168344 in the unified checklist. As I wrote this morning the taxa 8410115, present in GRIIS Belgium, doesn't play any role occurrence-speaking unless GBIF solves gbif/portal-feedback#3225 which I opened 20 days ago and which I mentioned above, still unlikely it will happen shortly.

6307044 is synonym of 8168344. Still, it would be sufficient to have it published in one of the checklists and indicate we trust the synonymy match and the accepted taxon 8168344 will appear in the unified and will stream up to a new occurrence cube with all occurrences of both taxa.

@damianooldoni
Copy link
Contributor

I have just asked an update status to GBIF: gbif/portal-feedback#3225 (comment)

@damianooldoni
Copy link
Contributor

@timadriaens, update from GBIF Backbone:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants