Manz wrote:Hey, I found some weirdness. If the image is in Orphan and you move it to another group, it remains in Orphan but also appears in the orphan of the group you transfer it to. But if its in a dataset (haven't tested in anything else yet) then the image disappears from dataset and appears in the orphan of the group its meant to be in.
NB:- I should elaborate on this one. I just discovered that if it is in a dataset and you chgrp it, in appears in the orphan images in both the group you are moving it to and the group it has come from. This occurred when I tried using a layered image.
In the above, you mean you are modifying in the cli and then checking that it's location in OMERO.web? But you retried this process, so I don't need to worry about any of this, just that which follows, right? (Also, what's a layered image?)
Ah, good to know. I added a request for DEBUG output there. I'll also bring this up with the web team.
So if you are owner of a group and not a sysadmin, there is some serious weirdness.... one of which means you can't delete your own images. If you aren't an owner or if you are an owner AND a sysadmin, you work fine.
I tried to replicate this error in the previous version of omero (4.3 not chgrp branch)(changed myself to a non-sysadmin who owned groups) and had no problems deleting or importing (import was done through dropbox this time). But I know at some stage this error did come up as we posted it on the forums. I think last time we recreated new groups and the errors stopped. I will attempt to replicate this error or work out why sometimes it comes up and sometimes not. Would you guys have any idea?
Can you not delete your images after chgrp or ever? Off-hand I don't have an idea. Logs and stack traces would be really helpful.
Manz wrote:It isn't possible to import into a dataset either if you are owner but not admin. You get the following error:-
- Code: Select all
bin/omero import -d 204 /tmp/lease.png
[code]Using session df452a79-320c-498f-868d-79e604c27382 (user1@localhost:4064). Idle timeout: 10.0 min. Current group: group1_private
...
java.lang.RuntimeException: omero.SecurityViolation
serverStackTrace = "ome.conditions.SecurityViolation: Cannot read ome.model.containers.Dataset:Id_204
And when you try to delete images when you are owner
EDIT:- nevermind about the import issue, I was trying to import when the session was still based on the previous user. But the first issue I still can't replicate
Right. If the dataset is in another group, it's not expected that you can import into it, though if no specific group is requested perhaps we could automatically login to the other group. Keep an eye on
https://trac.openmicroscopy.org.uk/ome/ticket/7814 on how we can best fix that.
Cheers,
~Josh