Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Phylum and Division should not both be options in the same tree #1200

Open
grantfitzsimmons opened this issue Aug 12, 2022 · 6 comments
Open
Labels

Comments

@grantfitzsimmons
Copy link
Member

grantfitzsimmons commented Aug 12, 2022

In botany and mycology, division refers to a rank equivalent to phylum.

@beach53
Copy link
Member

beach53 commented Aug 12, 2022

Botanists use Division, Zoologists use Phylum.

@maxpatiiuk
Copy link
Member

@grantfitzsimmons Where do you see "Division"?

The default ranks are created by Sp6. I belive the setup wizard choose Division/Phylum correctly depending on the discipline

@grantfitzsimmons
Copy link
Member Author

grantfitzsimmons commented Aug 16, 2022

@maxpatiiuk I believe it was a Botany database that I noticed this issue on. Theresa said she has seen the same behavior on some databases

@maxpatiiuk
Copy link
Member

maxpatiiuk commented Aug 16, 2022

Could it be that someone manually changed the discipline post database creation?

@maxpatiiuk
Copy link
Member

This is a Sp6 bug that affects Sp7
Replicated in a blank Botany database without preloaded taxa
The tree definition contains both Division and Phylum
They have the same TaxonTreeDefItem.rankId of 30
The Sp6 UI uses Division/Phylum randomly (opening the tree viewer shows Division one time, and Phylum next time)

@maxpatiiuk
Copy link
Member

maxpatiiuk commented Aug 16, 2022

Looks like the bug is in SpWizard. Both Division and Phylum are present in the database even before Specify is opened for the first time.

Screenshot (13)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants