Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"
As specified in #2615 and spec.xml, the options argument to queueDelete should take a map of path arguments to specify how strict the delete should be.
The various configuration tasks are intended to be linked from here.
Just thinking about deleting of Comments, as 'non-shareable' annotations, with respect to the way I have used them to store Publication data linked to several Projects in EMDB: I think it is OK to delete a Comment on a P/D/I if it is not used elsewhere, but if it is linked to other objects, then it probably should not be deleted? I guess I'm suggesting that you treat it a bit more like a Tag: If is is not used elsewhere then delete it. If it is, don't delete it. This would not change the current behavior for Insight comments, since they will never be on more than 1 P/D/I?
Just thinking about deleting of Comments, as 'non-shareable' annotations, with respect to the way I have used them to store Publication data linked to several Projects in EMDB: I think it is OK to delete a Comment on a P/D/I if it is not used elsewhere, but if it is linked to other objects, then it probably should not be deleted? I guess I'm suggesting that you treat it a bit more like a Tag: If is is not used elsewhere then delete it. If it is, don't delete it. This would not change the current behavior for Insight comments, since they will never be on more than 1 P/D/I?