API returns 2 new taxa for a taxonomic swap

[jeanphilippeb]

I looks like a bug… can you help me?

Consider this taxonomic swap:
Scorpaeniformes 47286 replaced with Perciformes 47233.
https://www.inaturalist.org/taxon_changes/101796

But the API suggests that the inactive taxon 47286 corresponds to 2 active taxa 47233 and 1555654:
https://api.inaturalist.org/v1/taxa/47286

So, I get it wrong if I interprete this API response as a taxonomic split from taxon 47286 to the 2 taxa 47233 and 1555654.

What’s wrong?
How can I figure out from the API response about taxon 47286 that there was a taxonomic swap replacing it with taxon 47233 only.

[jeanphilippeb]

Not found in api.inaturalist.org but similar:
https://www.inaturalist.org/taxon_changes.json?taxon_id=47286

[pisum]

@jeanphilippeb

Scorpaeniformes 47286 replaced with Perciformes 47233.
https://www.inaturalist.org/taxon_changes/101796

But the API suggests that the inactive taxon 47286 corresponds to 2 active taxa 47233 and 1555654

there was a subsequent split of 47233 into 47233 and 1555654.

[jeanphilippeb]

Thank you, it clarifies the result of https://api.inaturalist.org/v1/taxa/47286

My need is to update the definition of the Phylogenetic Projects, after a taxonomic change impacting the taxon linked to a project. And I would like to automate this update. In the present case, I am going to rename the project Unknown / Scorpaeniformes as Unknown / Perciformes, after the swap 47286 → 47233.

Since the split 47233 → 47233,1555654 didn’t change the status active of taxon 47233 Perciformes, it does not affect the definition of the project. In other words, it’s still consistent to have a project linked to taxon 47233. The split might only affect the choice of the project new observations are pushed to.