EDIT

I added a comparator which sorts according to the designation status defined by the ordered terms. But this order does not confirm with the order proposed in this ticket. Should we change the order in of the ordered terms rather than changing the comparator?

Yes this is a good idea. I created a related ticket: #7384

Can we anyway switch to the comparator already now as the existing order is already not so bad (with holotype at the beginning, followed by lectotype)

@AK: do you have a defined order for type designations status in phycobank?

Andreas Kohlbecker wrote:

Andreas Müller wrote:

Yes this is a good idea. I created a related ticket: #7384

Can we anyway switch to the comparator already now as the existing order is already not so bad (with holotype at the beginning, followed by lectotype)

@AK: do you have a defined order for type designations status in phycobank?

Yes I do!

The order logic is implemented in LinkedHashMap<TypedEntityReference, TypeDesignationWorkingSet> eu.etaxonomy.cdm.api.service.name.TypeDesignationSetManager.orderByTypeByBaseEntity(Map<TypedEntityReference, TypeDesignationWorkingSet> stringsByTypeByBaseEntity)

If you move the second anonymous Comparator class into its own class file you can use it for to solve this issue here.

Andreas

I extracted the comparator and added another comparator for TypeDesignationBase.

Andreas K.: Could you also take a quick look?

Seems to work and can be closed.

Still does not work. After model update (updating orderIndex) I still get the old order in UI, see attachement.

Tested on rem_conf_am.

Added comparator to combo

OK, the sorting of the designations worked before already. Misunderstanding from my side.

Also the dropdown has the same order now. Great. We can close the tickt.