[ome-devel] Saving ROIs with Z=T=C=-1

[Alison Walter]

Hello,

I've noticed some oddities when saving ROIs with Z=T=C= -1 via the
ROIFacility. I'm using OMERO 5.4.

1. Using ROIFacility.saveROIs(...) I get duplicates returned

If I have a ROIData object with one EllipseData shape with Z=T=C= -1,
saving that ROI via saveROIs(...) returns two identical ROIData
objects. Only one ROI is actually saved to the server.

2. Updating a ROI with multiple shapes with Z=T=C= -1 causes some of
the shapes to be lost

If I have a ROIData object with three EllipseData shapes all with
Z=T=C= -1 that I've downloaded, and then I try to save the ROI back to
the server one of those shapes gets deleted. If the ROIData object
hasn't been saved to the server yet, then all the new shapes are
saved.

Here's a link to a gist with some test code:
https://gist.github.com/awalter17/bafb746b97dc21ee91e526b7b5853d42

When using a ROIData object with a single Z=T=C=-1 shape the output I get is:

Number of ROIs loaded: 1
ROIData id: 616
ShapeData id: 585

Number of ROIs saved: 2
ROIData id: 616
ShapeData id: 585

ROIData id: 616
ShapeData id: 585

When using a ROIData object with three shapes at Z=T=C= -1 the output I get is:

Number of ROIs loaded: 1
ROIData id: 618
ShapeData id: 589
ShapeData id: 590
ShapeData id: 591

Number of ROIs saved: 2
ROIData id: 618
ShapeData id: 589
ShapeData id: 590
ShapeData id: 589

ROIData id: 618
ShapeData id: 589
ShapeData id: 590
ShapeData id: 589

Please feel free to let me know if you require any additional
information from me.

Cheers,
Alison