feature request #5346
openAllow 3 ways of ordering in Taxon Navigator
70%
Description
We may want to have 3 options to change the ordering: natural, rank - alphabet, pure alphabet. Currently the preferences allow only 2 types of ordering, natural and non-natural. We may want to create an enumeration for this and a dropdown in the preference section to choose from.
this is split from #3771
Updated by Katja Luther over 8 years ago
- Target version deleted (
Unassigned CDM tickets)
Updated by Katja Luther about 8 years ago
- Status changed from New to Resolved
- Assignee changed from k.luther - to Andreas Müller
fixed with r27323 and r27324
Updated by Andreas Müller about 8 years ago
- Assignee changed from Andreas Müller to k.luther -
The 3 options do now exist and work.
However, the natural ordering #3771 still doesn't work correctly. Choosing "Predecessor" adds the taxon at the higher level (as a predecessor of the parent) and does not refresh the tree correctly.
Also the Message and the button labels in the selection parent-predecessor-cancel could still be improved and made more intuitive.
Finally, it is currently not easy to put a taxon as a first child of a parent if children already exist. Maybe we want to move a taxon at first position by default if choosing "parent". Moving it to the last position can be done by moving it to the preceding taxon and choose "predecessor".
Updated by Andreas Müller about 8 years ago
Also I wonder if we couldn't automatically refresh the navigator if the preferences is changed. The navigator does not have unpersisted data so this is not dangerous (only may take some time, but needs to be done by the user anyway).
Updated by Katja Luther about 8 years ago
the natural order works now see r27609
Updated by Katja Luther almost 8 years ago
now if the taxonnode is moved as child it is put as first child and the text is changed see r27777
Updated by Andreas Kohlbecker over 4 years ago
- Description updated (diff)
- Private changed from Yes to No
Updated by Katja Luther about 2 years ago
Andreas Müller wrote in #note-4:
Also I wonder if we couldn't automatically refresh the navigator if the preferences is changed. The navigator does not have unpersisted data so this is not dangerous (only may take some time, but needs to be done by the user anyway).
this is fixed now.
Updated by Katja Luther about 2 years ago
Katja Luther wrote in #note-6:
now if the taxonnode is moved as child it is put as first child and the text is changed see r27777
Actually when creating a new child, this is added at the end, I think we should keep this as it is.
Updated by Katja Luther about 2 years ago
- Assignee changed from Katja Luther to Andreas Müller
Please have a short look and then we can close this ticket.
Updated by Andreas Müller about 2 years ago
- Status changed from Resolved to Feedback
- Assignee changed from Andreas Müller to Katja Luther
- % Done changed from 0 to 70
What exactly is the reason, why taxa can't be moved in between 2 other taxa? Currently you always get asked if you want to move it as a child or following sibling. Was the reason the old navigator which we do not use anymore.
If there is a possibility to allow in-between moving we should try to implement this similar to the term tree editor and others.
If it is not possible, then we should first ask where to move and then show the "Secundum reference differs" message as this message depends on the exact target location.
Alos if it is not possible to move in-between the label for "Behind" should be "Below (as sibbling)" to make semantics clearer. In a tree view "behind" is an clear term.
Updated by Katja Luther almost 2 years ago
Andreas Müller wrote in #note-11:
What exactly is the reason, why taxa can't be moved in between 2 other taxa? Currently you always get asked if you want to move it as a child or following sibling. Was the reason the old navigator which we do not use anymore.
If there is a possibility to allow in-between moving we should try to implement this similar to the term tree editor and others.If it is not possible, then we should first ask where to move and then show the "Secundum reference differs" message as this message depends on the exact target location.
Alos if it is not possible to move in-between the label for "Behind" should be "Below (as sibbling)" to make semantics clearer. In a tree view "behind" is an clear term.
To move between two nodes is not possible in the navigator, I already made a lot of research to find a solution. I will change the order of the secundum and the question where to move the node. The labels are adapted as well.
Updated by Katja Luther almost 2 years ago
- Assignee changed from Katja Luther to Andreas Müller
Everything is done, except a translation for sibbling in terms of trees? "Geschwister" sounds not very nice, actually I have as german label:
"Wollen Sie den Taxonknoten als Kind oder hinter den Zielknoten verschieben?"