Taxon.isAccepted should be set to true if the taxon is preferred.

[benanhalt]

To Reproduce
Here is one symptom that can be reproduced:

1. Upload a collection object data set with determinations and taxon mapped (don't map Taxon.isPreferred).
2. Open the uploaded records in Specify 6.
3. Any record that is determined to a newly uploaded taxon will show a blank preferred taxon.
4. The preferred taxon does appear in Specify 7.
   See screenshots below.

Screenshots

Desktop (please complete the following information):

• Specify 7 Version 7.6.1

Reported By
Andy

[benanhalt]

To fix this, I will add a business rule that automatically sets isAccepted according to whether acceptedId is null.

[benanhalt]

This applies to other trees as well.

[maxpatiiuk]

Should I hide isAccepted for other trees too?

[benanhalt]

Probably. But I'm still investigating why these fields even exist. Let me finish that and I'll let you know.

[maxpatiiuk]

If it helps, isAccepted is a field many taxon and geography authorities have to mark names as being widely accepted by authorities.

I usually exclude all non accepted taxa from the tree when doing imports

[grantfitzsimmons]

May be fixed in xml-editor

[melton-jason]

@specify/ux-testing

This was made into a businessrule as of #2965.
(See #3157 (comment) for more context).

Can the fix be verified and this issue closed?

[melton-jason]

Specify 7 is now correctly setting the isAccepted depending on whether the Taxon is synonymized (True if the Taxon is not synonymzied and False otherwise).