Taxon form is based on current discipline, not host taxon discipline

[grantfitzsimmons]

While testing #3283 I found that the rank options are based on the current discipline's tree rather than the host taxon discipline.

It was originally /api/specify/taxontreedefitem/20/, appearing similar to the one below (link):

I can change the rank to the valid rank in the current discipline, which in this case is now "DB", which is a rank that does not exist in the other discipline's tree definition.

Screen.Recording.2023-04-03.at.7.43.36.PM.mov

Now I cannot open the "Life" rank as the lower rank is not part of the tree definition in the destination collection.

[grantfitzsimmons]

For more context, the rank Kingdom in the host taxon collection's discipline (Host) has a taxontreedefitem ID of 20. The rank of Kingdom in the source collection's discipline (Kriebel_Plants) has a taxontreedefitem ID of 2.

https://purdueherbaria11023-issue-2405.test.specifysystems.org/specify/view/taxontreedefitem/2/
https://purdueherbaria11023-issue-2405.test.specifysystems.org/specify/view/taxontreedefitem/20/

This means I cannot set the rank back to the correct option.

[maxpatiiuk]

This issue is a subset of #1886

[emenslin]

Can recreate in edge (7.9.6)

[bronwyncombs]

North Carolina State University Herbarium has reported this issue.

In order to add a new node to the host taxon tree, users must switch collections. The qcbx '+' brings up a new taxon form, but it is then set in the current collection.

Screen.Recording.2025-01-16.at.12.33.13.PM.mov