EDIT

Please have in mind that OriginalSourceBase also allows the String attribute originalNameString. This is a more generic field that does not only apply for names. It is also possible that the original name is stored in this field. In E+M this may be the case as E+M in Berlin Model also allows foreign keys as well as Strings for original name information.

Also we have to have in mind that missing original name information does not necessarily mean that the name used in the source is the one of the the accepted taxon. It may also be left out or in the Berlin Model Editor when you moved a taxon you may have forgot to adapt the information accordingly. In this case automatic addition of the name will lead to wrong data.

adding a snipped from my notes just for not to lose it:

"this behaviour whether name in source is automatically filled or not, should be configurable in the dialogue : checkbox!"

The method with setting the name should be moved down in menu

The labels of the 2 menus should be equal except for the addition about the Name in Source. Is there a reason why you use selected facts once and only fact(s) other time? Use the shorter as "selected" is not necessary.
This is correct for Descriptions but not for DescriptionELements.

"... Other Taxon ..." => "other taxon" for all 4 menu entries.

"... and set Name in Source" => "... and set Name in Source if empty" (for the 2 menu entries)

Andreas Müller wrote:

Please open a new ticket for the final implementation with a new wizard including the question if the name in sources should be taken from the accepted taxon if being empty and removing the second label.

What about checking all elements to move (including the description itself?) if they have sources with empty name in source. If yes have a dialog and ask if the empty name in sources should be set to old accepted taxon automatically and allow yes, no, cancel. Only then open the ordinary dialog/assistant.
Maybe only check sources of type primaryXXX, no import sources.

Andreas Müller wrote:

Currently both methods do end in an unexpected state. After running the operation the old taxon is dirty (and unsaved) and the new taxon does not yet contain the new data. Only by saving the old taxon this seems to happen.

I don't know if this is related to this ticket but it should be fixed urgently (to me seems to be a regression).

But this was a requirement we fixed a few weeks ago. The moving should be done after saving.(#8234)

Ok, in generall this probably makes sense. Maybe I just wasn't used to it yet.
However, if this is the expected behavior I do not understand why I get a warning that my taxon is not saved and it will be saved if I proceed with the command. I would expect this is not necessary at all for the old taxon and only necessary for the new taxon (and probably only for the save action and not yet during the move action)