problem

On migrating TMs from OpenTM2 to t5memory it happens often, that some memories could not be migrated. Mostly because the memory is just empty in OpenTM2.

solution

The memory:migrate command needs an optional --create-empty=UUID switch, which converts a single TM but omits the export and the import, so that it is just created empty in t5memory and the location is re-routed in the LanguageResource DB.

Either the TM could then be left empty by the user, or data could then be imported manually.

Finally a possibility to clean up the config opentm2.server (remove source OpenTM2 URL and point the language resources to the remaining t5memory target URL) is needed if all TMs are migrated. Either by calling memory:migrate once again (currently it just exits) - or also with an additional option. What ever is easier.