Task #7814 (closed)
Bug: Better handle CLI import into dataset in non-current group
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | critical | Milestone: | OMERO-4.4 |
Component: | Import | Version: | n.a. |
Keywords: | cli, import | Cc: | cxallan, jburel, amanda.miotto.1@… |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | 0.0d |
Sprint: | n.a. |
Description
If the user specifies that an image should be imported into a dataset which is not in the current group, then at the least a message should be printed and not reams of stack traces. Even better would be changing to the specified group (though care must be taken if there are conflicting group wishes). This, however, will require a method which allows users to query among all groups that they are a member of.
See: https://www.openmicroscopy.org/community/viewtopic.php?f=6&t=1028 (at the bottom)
Change History (4)
comment:1 Changed 12 years ago by jmoore
comment:2 Changed 12 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
comment:3 Changed 12 years ago by jmoore <josh@…>
- Remaining Time set to 0
(In [8bb17d278460c34d5d7f2c1f2d300283e171655b/ome.git] on branch develop) Run import in group of target (See #3527, Fix #7814)
comment:4 Changed 12 years ago by jmoore <josh@…>
(In [52d5f30817b6593411f7f689a6fa3bb3d62256d1/ome.git] on branch develop) Fix NPE and mis-use of -1 when no target is set (See #7814)
Fix using the call context pushed to my github: https://github.com/joshmoore/openmicroscopy/commit/8bb17d278460c34d5d7f2c1f2d300283e171655b
This needs testing from insight; I only validated from the CLI on an image into a dataset, not screens, etc.