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
Currently, if you download an OMERO object with annotations to ImageJ and then upload a new version of this object to OMERO the annotations are lost.
Example scenario:
In OMERO, you have an image which has a number of annotations (tags, files, etc.)
Download this image to ImageJ, and potentially make some changes
Upload the modified image to OMERO as a new image
In general, the new image which is uploaded should have all the same meta-data as the originally downloaded image (i.e. same description, name, etc.). But it doesn't. The annotations are not preserved.
As I understand annotations in OMERO, to make this happen we'd need to:
Store the annotations of the original OMERO object (annotations are not loaded by default!)
Upload the new object to OMERO, and retrieve it (or possibly just its ID)
Create a link between each of the original annotations and the new object
Upload the links to OMERO
I imagine that this won't be very efficient. So we probably want to make it an option for the user (i.e. detect if the original omero object had annotations and ask the user if they want to preserve them).
We'll need to support this for images, tables, and rois.
The text was updated successfully, but these errors were encountered:
Currently, if you download an OMERO object with annotations to ImageJ and then upload a new version of this object to OMERO the annotations are lost.
Example scenario:
In general, the new image which is uploaded should have all the same meta-data as the originally downloaded image (i.e. same description, name, etc.). But it doesn't. The annotations are not preserved.
As I understand annotations in OMERO, to make this happen we'd need to:
I imagine that this won't be very efficient. So we probably want to make it an option for the user (i.e. detect if the original omero object had annotations and ask the user if they want to preserve them).
We'll need to support this for images, tables, and rois.
The text was updated successfully, but these errors were encountered: