I am not sure if this is by design but in the current fgcz-ms sync architecture this completely fails to register files even though they get synced if the container and sample id are a mismatch. I wonder if it would be better to just not register the sample id rather than not create the import resource at all.
We could also allow order and parent project mixing as a compromise although I think it's not allowed by design.
I am not sure if this is by design but in the current fgcz-ms sync architecture this completely fails to register files even though they get synced if the container and sample id are a mismatch. I wonder if it would be better to just not register the sample id rather than not create the import resource at all.
We could also allow order and parent project mixing as a compromise although I think it's not allowed by design.