Makes me think: we should probably store the transform job id in the migrate batch so that we can link both steps, at least for debug.
:brain:
Maybe we should just make clear in transform that failed transformations won't create a migration.
We could yes, and simply display the number of "skipped" records the migration report, in case the user didn't pay attention in the transform step. They can go back to the transform step to look into the errors if they want.
Makes me think: we should make it clear somehow that the report pages are persistent and user can go return to them (bookmark or whatever). With the step-by-step flow it feels transient (at least to me).
:brain:
We could yes, and simply display the number of "skipped" records the migration report, in case the user didn't pay attention in the transform step. They can go back to the transform step to look into the errors if they want. Makes me think: we should make it clear somehow that the report pages are persistent and user can go return to them (bookmark or whatever). With the step-by-step flow it feels transient (at least to me).
_Originally posted by @streino in https://github.com/ecolabdata/ecospheres-migrator/pull/26#discussion_r1753681894_