Closed joshmoore closed 5 years ago
Opening for discussion. Requires tests & docs.
Code looks fine as an initial step and some smoketesting went fine too. :+1:
Capturing here an interesting behavior that I realized following a copy-n-paste in IDR dataset import. The following workflow:
$ bin/omero import -T Project:name:foo/Dataset:name:bar test.fake
$ bin/omero import -T Project:name:foo2/Dataset:name:bar test.fake
$ bin/omero import -T Project:name:foo/Dataset:name:bar2 test.fake
leads to the bar
datasets being multi-linked in projects foo
and foo2
and containing 2 images:
On second thought, I completely understand how my workflow led to this layout. I am mentioning it here as my initial naive user expectation was that the default target behavior would be applied to the combination of the project and the dataset rather than each container individually. This might be something worth mentioning when the docs get amended to document this feature. When we document this feature as part of the import targets
A command like:
now loads a sub-target of type
Dataset
internally. The output from such an import looks like:see: https://forum.image.sc/t/cli-import-specifiy-project-to-place-dataset/27037/3