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
While curating this study, I added these two taxa: Tropicoporus stratificans and Tropicoporus tropicalis.
Once added, one terminal containing each taxa was able to be mapped BUT I was not able to map the other terminals under these taxa (these two taxa had multiple terminals). I tried adding these taxa again (this time checking the unmapped terminals) and the system told me these taxa were Already in OT taxonomy!
If I added those two taxa, why I am not able to map additional OTUs under those taxa? I saved the study and logged out of it and logged in again, but the same Failed mapping OTUs.
I opted for assigning one representative terminal for those taxa, the one that was mapped.
Other OTUs are able to be mapped, even if they appear multiple times in the trees, so this is a little confusing.
Thanks!
Romina
The text was updated successfully, but these errors were encountered:
Reference study:
https://tree.opentreeoflife.org/curator/study/edit/ot_1138/?tab=otu-mapping
While curating this study, I added these two taxa: Tropicoporus stratificans and Tropicoporus tropicalis.
Once added, one terminal containing each taxa was able to be mapped BUT I was not able to map the other terminals under these taxa (these two taxa had multiple terminals). I tried adding these taxa again (this time checking the unmapped terminals) and the system told me these taxa were Already in OT taxonomy!
If I added those two taxa, why I am not able to map additional OTUs under those taxa? I saved the study and logged out of it and logged in again, but the same Failed mapping OTUs.
I opted for assigning one representative terminal for those taxa, the one that was mapped.
Other OTUs are able to be mapped, even if they appear multiple times in the trees, so this is a little confusing.
Thanks!
Romina
The text was updated successfully, but these errors were encountered: