RFE: IDelete - Skipping error message

[atarkowska]

I was importing plate using Insight importer and exidently shut the application in the middle of import. The plate object was created in the datable but non of the wells were rendered correctly. Then I decided to delete Plate and I end up with the error message in status:

Finished 0 error(s) (Skipping delete of LogicalChannel:1289 
Skipping delete of LogicalChannel:1290 Skipping delete of DetectorSettings:19 
Skipping delete of DetectorSettings:19 
Skipping delete of ObjectiveSettings:3 ConstraintViolation: fkimage_experiment_experimentConstraintViolation: fkdetectorsettings_detector_detectorSkipping delete of LogicalChannel:1289 
Skipping delete of LogicalChannel:1290 Skipping delete of DetectorSettings:19 
Skipping delete of DetectorSettings:19 Skipping delete of ObjectiveSettings:3 
ConstraintViolation: fkimage_experiment_experiment
ConstraintViolation: fkdetectorsettings_detector_detector
Skipping delete of LogicalChannel:1289 
Skipping delete of LogicalChannel:1290 Skipping delete of DetectorSettings:19 
Skipping delete of DetectorSettings:19 Skipping delete of ObjectiveSettings:3
 ConstraintViolation: fkimage_experiment_experimentConstraintViolation: 

[jmoore]

Ola, passing back to you after the conversation in devteam. I think the best choice until we improve reporting is to not show the users the warnings, but you'll need to confirm with J-M and have the strategy the same in both clients.

[jburel]

Reduce the message to something: "Delete not completed"
but it also means that we will need to have a force delete option so corrupted data can be deleted.
From a user point of view, the import failed so he/she should be able to remove the plate.
Attaching ticket to delete phase II

[jmoore]

It's a bit more complicated than that, since in this case, nothing has gone wrong. It's only saying that N-1 of N attempts to delete the LogicalChannel failed. The final one passed. So, in this case, there's nothing for the user to do. In the case of a user tries to delete one image that shares with another image a LogicalChannel and so the LogicalChannel really cannot be deleted, then there's no reason to offer a "force" option, since there's nothing we can do about it (other than to delete the second image).

I don't think this is related to the failed import or not.

[Aleksandra Tarkowska <A.Tarkowska@…>]

(In [f0d726aef66dc9f091aff14c8d3210042524c6ed/ome.git] on branch develop) this replace error/warning server messages by the appropriate string, see #6003

[jmoore]

Changing to an RFE. I agree that it's not ideal but:

1. it's not harming the user (though it certainly may be confusing them)
2. it will require significant reworking to detect.

If any of you disagree and can think of something specific server-side I can do to make this better now, let me know.

[jmoore]

Won't be making any changes to this for the moment.

[jamoore]

Delete1 implementation is now all but completely gone.