gbif / backbone-feedback

2 stars 0 forks source link

How to remove "artificial accepted usage for a synonym"? #439

Closed gbif-portal closed 5 months ago

gbif-portal commented 4 years ago

How to remove "artificial accepted usage for a synonym"?

"Carex pendula" was originally published in the "Global Register of Introduced and Invasive Species - Belgium", as an accepted name for "Carex agastachys": https://www.gbif.org/species/162644337. We have since (March 19) reverted back to the name "Carex agastachys" (keeping the same taxonID), since "Carex pendula" is the name of another native species to Belgium

On the backbone page for Carex pendula however, the Belgian register is still listed, with a reference to https://www.gbif.org/species/159747346, which states is a:

Artificial accepted usage for a synonym if its missing to preserve the taxonomic hierarchy.

Is there a way to remove this, so the Belgian register is no longer listed as a source for Carex pendula being introduced in Belgium?


Github user: @peterdesmet User: See in registry System: Chrome 80.0.3987 / Mac OS X 10.14.6 Referer: https://www.gbif.org/species/159747346 Window size: width 1368 - height 766 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: INFO

ManonGros commented 3 years ago

Hi @peterdesmet Let me know if this issue has gone out of scope.

Right now the Global Register of Introduced and Invasive Species - Belgium checklist published on GBIF shows that Carex agastachys L.f. is a synonym of Carex pendula Huds.:

Screenshot 2021-09-02 at 11 28 09

The checklist doesn't have any entry for Carex pendula Huds. This is why Carex pendula Huds. is now labelled as "doubtful" in its GRIIS Belgium checklist version on GBIF https://www.gbif.org/species/159747346

You could consider updating the checklist to show Carex agastachys L.f. as an accepted name.

However, it wouldn't change the GBIF backbone. The current source for both species, the World Checklist of Selected Plant Families via the CoL, shows Carex agastachys L.f. as a synonym of Carex pendula Huds: https://www.gbif.org/species/2725229 Do you think this is incorrect? Let us know and we will forward the issue.

peterdesmet commented 3 years ago

Thanks @ManonGros

  1. Will the record for Carex agastachys L.f. be treated differently if we set the taxonomicStatus to ACCEPTED in our source checklist? E.g. will https://www.gbif.org/species/159747346/verbatim no longer be created?
  2. I'm not a plant expert, but yes, in TrIAS we consider Carex agastachys L.f. (exotic in Belgium) different than Carex pendula (native in Belgium), so forwarding this along would be helpful.
ManonGros commented 3 years ago

@peterdesmet

  1. Will the record for Carex agastachys L.f. be treated differently if we set the taxonomicStatus to ACCEPTED in our source checklist? E.g. will https://www.gbif.org/species/159747346/verbatim no longer be created?

Yes, changing taxonomicStatus to ACCEPTED and replacing the name and ID of Carex pendula Huds. by Carex agastachys L.f.'s in the acceptedNameUSage and acceptedNameUsageID fields should make the entry disappear.

Thanks we will forward the issue about Carex agastachys L.f. to the CoL repository.

peterdesmet commented 3 years ago

I have updated the source checklist, removing taxonomicStatus, acceptedNameUsage and acceptedNameUsageID (https://github.com/trias-project/unified-checklist/commit/cefc340e0fd9d153fb0b03d2856fa21449d67540), since we consider all our taxa as their own concepts, i.e. accepted.

Once the crawling is finished, https://www.gbif.org/species/162644337/verbatim should no longer list those fields and https://www.gbif.org/species/159747346/verbatim should disappear.

peterdesmet commented 3 years ago

This issue is now resolved!

camiplata commented 5 months ago

This issue has been adress

Captura de pantalla 2024-06-14 a la(s) 11 43 28 a m