Taxon determinations on Collection Objects displaying in wrong "order"

[tmcelrath]

Describe the bug
If I add two determinations with two different years, the most recent determination should be the one displayed as "current"

To Reproduce
Steps to reproduce the behavior:

1. When I add two determinations.
2. Then I add the older one second.
3. Then the older one is displayed, not the most "current" one.

Example

Expected behavior
Determinations should "rank" based on age.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please identify where you experience this bug:
*** One of ***

• Production
• Chrome

[mjy]

You must drag the preferred determination to the top of the list. It is not based on age.

[tmcelrath]

Am I missing something? I can't drag them.

[mjy]

Might have been added then removed in Comprehensive in the list.

…

On Fri, Mar 6, 2020 at 4:16 PM Tommy McElrath ***@***.***> wrote: Am I missing something? I can't drag them. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1355?email_source=notifications&email_token=AAAFQSGNFRSI5N5AGXK6LY3RGFY2RA5CNFSM4LDHYUXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEODA56Q#issuecomment-595988218>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAFQSDHVWTTQVUKT2C2PQTRGFY2RANCNFSM4LDHYUXA> .

[tmcelrath]

Should I edit issue to "Can't change determination order"?

[mjy]

Sounds good.

…

On Fri, Mar 6, 2020 at 4:18 PM Tommy McElrath ***@***.***> wrote: Should I edit issue to "Can't change determination order"? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1355?email_source=notifications&email_token=AAAFQSDC73BEERFHHZBLXELRGFZEZA5CNFSM4LDHYUXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEODBE3Y#issuecomment-595989103>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAFQSB3K4QYZ4YQIRN5LP3RGFZEZANCNFSM4LDHYUXA> .

[mjy]

@jlpereira You did something with positoin, is this resolved?

[jlpereira]

@mjy if I remember well there was some issue at the backend

[tmcelrath]

This is not resolved. Still an issue.

[tmcelrath]

Please fix ASAP

[jlpereira]

@tmcelrath this is still an issue? since Browse collection object was refactored, maybe it's already fixed. Could you let us know?

[tmcelrath]

Still an issue. Still not using the most recent one as the "current" identification.

[tmcelrath]

That same CO is still a good example. Only using the older identification for display and for export to DWC.

[mjy]

Only using the older identification for display and for export to DWC.

I rememver, this multiple issues.

• Allow curator to update position of Determinations (top is current)
• Replace call to /collection_objects/123/dwca with /collection_objects/123/dwc?rebuild=true` (fully deprecate throught)
  • Browse collection object
  • others?!
• Refresh object label (in header) on Comprehensive if Determination changes because new top record
• Ensure top curation is exported to DWC
  • Requires full nuke/rebuild at this time
• Restore date column to comprehensive (order is correct there AFAICT)

[mjy]

We think we have it now.