You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The error message such as 'cannot move channel[xxxxx] while LogicalChannel[xxxxx] remains when a Move of derived images is attempted, such as Projections, and the original image is left in original group is insufficient.
As reported recently by @mporter-gre, the follow-up hql query omero hql -q --limit=10 --all "select id, pixels from Channel where logicalChannel=9428714"
followed by omero hql -q --limit=10 --all "select p.image from Pixels p where p.id=4319640"
is simply too much even for a user who is familiar with OMERO concepts.
The question is whether we could not offer the Image IDs in the error message instead ?
The error message such as
'cannot move channel[xxxxx] while LogicalChannel[xxxxx] remains
when a Move of derived images is attempted, such as Projections, and the original image is left in original group is insufficient.As reported recently by @mporter-gre, the follow-up hql query
omero hql -q --limit=10 --all "select id, pixels from Channel where logicalChannel=9428714"
followed by
omero hql -q --limit=10 --all "select p.image from Pixels p where p.id=4319640"
is simply too much even for a user who is familiar with OMERO concepts.
The question is whether we could not offer the Image IDs in the error message instead ?
Further, @mporter-gre suggested
A detailed description of the projects and datasets would be nice, like when you click the 'Show parent projects/datasets' button in web.
cc @joshmoore
The text was updated successfully, but these errors were encountered: