You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all, I have just added Amphitremida (order in Labyrinthulea) to IRMNG since it was not there previously; its included family, Amphitremidae, which contains the genera Amphitrema and Archerella, was originally placed in Cercozoa but has more recently (2013 onwards) been transferred to Labyrinthulea a.k.a. Labyrinthulomycetes, hence a source of potential confusion in various data sources which may or may not have the most recent allocations.
I checked OpenTree and found some oddities which someone may or may not care to resolve... First Amphitremida https://tree.opentreeoflife.org/taxonomy/browse?id=394559 seems to be treated as a genus name, not an order, within family Thraustochytriaceae, which is wrong - it should be an order within Labyrinthulomycetes, see https://www.ncbi.nlm.nih.gov/Taxonomy/Browser/wwwtax.cgi?id=1287658 . (Note, NCBI has an erroneous spelling for the included family name, Amphitraemidae should read Amphitremidae).
Second, Amphitrema (genus) currently has 2 entries under opentree, reflecting its history of placement, although these are in fact the same taxon: https://tree.opentreeoflife.org/taxonomy/browse?name=Amphitrema . "Amphitrema (genus in subkingdom SAR)" is the correct one, although its family placement should be in Amphitremidae, not Thraustochytriaceae. "Amphitrema (genus in phylum Sarcomastigophora)" reflects the previous higher tax. placement (as also in IRMNG up to today) but this record should be deleted and its content (gbif:7580765 (irmng:1300266)) merged with "Amphitrema (genus in subkingdom SAR)". This should also eliminate the "major_rank_conflict_inherited" status, perhaps.
Hoping this is resolvable by some manual or other fix. Cheers - Tony
The text was updated successfully, but these errors were encountered:
BTW It looks like the GBIF record https://www.gbif.org/species/7580765 was deleted in 2017 as someone encountered the same issue and did relevant data cleaning in GBIF.
Thanks. @kcranston has built a version of OTT with an updated GBIF. She is doing quality control checks on that version of OTT. Hopefully, it will be on a server in the near future. But we'll make sure to check on this group.
Hi all, I have just added Amphitremida (order in Labyrinthulea) to IRMNG since it was not there previously; its included family, Amphitremidae, which contains the genera Amphitrema and Archerella, was originally placed in Cercozoa but has more recently (2013 onwards) been transferred to Labyrinthulea a.k.a. Labyrinthulomycetes, hence a source of potential confusion in various data sources which may or may not have the most recent allocations.
I checked OpenTree and found some oddities which someone may or may not care to resolve... First Amphitremida https://tree.opentreeoflife.org/taxonomy/browse?id=394559 seems to be treated as a genus name, not an order, within family Thraustochytriaceae, which is wrong - it should be an order within Labyrinthulomycetes, see https://www.ncbi.nlm.nih.gov/Taxonomy/Browser/wwwtax.cgi?id=1287658 . (Note, NCBI has an erroneous spelling for the included family name, Amphitraemidae should read Amphitremidae).
Second, Amphitrema (genus) currently has 2 entries under opentree, reflecting its history of placement, although these are in fact the same taxon: https://tree.opentreeoflife.org/taxonomy/browse?name=Amphitrema . "Amphitrema (genus in subkingdom SAR)" is the correct one, although its family placement should be in Amphitremidae, not Thraustochytriaceae. "Amphitrema (genus in phylum Sarcomastigophora)" reflects the previous higher tax. placement (as also in IRMNG up to today) but this record should be deleted and its content (gbif:7580765 (irmng:1300266)) merged with "Amphitrema (genus in subkingdom SAR)". This should also eliminate the "major_rank_conflict_inherited" status, perhaps.
Hoping this is resolvable by some manual or other fix. Cheers - Tony
The text was updated successfully, but these errors were encountered: