EDIT

Creating larger termtrees is still cumbersome for multiple reasons

• adding a new term adds it add the beginning of the list, but usually one adds terms in the correct order so it should be added to the end
• adding multiple terms does not keept the order as it appears in the dialogue (order in vocabularies), however this is often also the expected order in the term tree and should be the default
• moving multiple terms (e.g. from top to the end) works but does not keep the order but inverses the order instead
• when moving multiple terms e.g. from the top to the end often the prvious last term is not before the moved terms but somewhere in between e.g. observered at second but last position
• when adding terms they can't be moved immediately as the need to be saved first, best would be to allow moving without saving, if this is not possible we should allow an add+save functionality in the dialogue.
• moving a term in large ordered term tree with many sibblings takes very long as you have to scrol during d&d, we either need a "move behind" menu method or some cut&paste solution
• it is slow by design as it still uses model objects at some places when loading

• new dialogue opens slow if it is for a term type with a large number of terms (e.g. term type State in ontology)

• Vocabulary editing: also adding terms to a large vocabulary creates many problems, when adding >2 terms to "architecture" in cdmterms/States the TaxEditor repeatedly crashed. There seems to be a memory issue.

All the above issues were observed when generating the ontology term lists.

See also #9697 for other issues related to term tree editing.