EDIT

Please ask Katja if unclear how to implement.

Applied in changeset taxeditor|ac1659d4fb4bd6a0f42c5e3cef97dee1ccad7925.

Looks like other additional languages are not stored correctly.

Also we may think about make it fully invisible as long as isExcluded is not checked. This may simplify the standard interface (feel free to make a new ticket for this if not easy to implement.

Patrick Plitzner wrote:

While reviewing I saw that even the isExcluded is not persisted anymore. Have to recheck if anything has changed

Actually, the TaxonNodeService does not correctly load the boolean values of the TaxonNode. In the data base they are stored correctly.
@Andreas: Has there been any model or service changed related to these values?

Patrick Plitzner wrote:

Patrick Plitzner wrote:

While reviewing I saw that even the isExcluded is not persisted anymore. Have to recheck if anything has changed
Actually, the TaxonNodeService does not correctly load the boolean values of the TaxonNode. In the data base they are stored correctly.
@Andreas: Has there been any model or service changed related to these values?

I added a test in TaxonNodeDaoTest which proofs that reading works fine for excluded and unplaced and also for excludedNote (not fully complete). Please adapt test if you think something does not work.

I could only reproduce the strange behavior (TaxonNode excluded and unplaced flag not initialised) in one data source which may be corrupted during an too early schema update.
Anyway, I tested the multi language text fields also for description elements. It seems like it does not work there either or I do not know how it is supposed to work. @Andreas: Can you check?
If so, we can close this ticket and open a new one for this issue

Before we close this there is one remaining issue:

Please move the "Open in Editor Check box down to the very bottom. An even better solution would be to have 3 buttons: save (or finish), save and open, Cancel

The current implementation makes one think that Open in Editor is an Attribute, not a workflow information.

A couple of layout and workflow issues for the node wizard are now handled in #6520. So we can close this ticket.