Permissions problem with OMERO.insight upload

[Chris Cole]

Hi,

I'm managing our group of users and have a specific usergroup (which I'm the owner) and have also created an initial set of project folders for our students to use. The default permissions are 'read-annotate'.

However, the first student to try this is not able to upload to any of the folders I created. Is this expected behaviour? Thinking about it, I guess it is with 'read-annotate' permissions. Does that also mean that for any given folder or dataset only the owner is able to add images to it? if so, is there a work around to allow more than one user to upload to a folder?

Thanks,

Chris

[mtbc]

Chris,

You're correct: read-annotate allows the addition of comments, ROIs, etc. to another's image but you cannot put your data into another's project/dataset hierarchy, you need read-write groups for that. An existing group can have its permissions adjusted so with careful enough students read-write might be the way to go.

In read-annotate groups there aren't any convenient workarounds that I can think of. There are various odd possibilities like:

• Administrators may be able to import as if they were other users (a kind of "sudo") but you don't want student administrators being able to become you!
• If you own the group then I think the permissions allow you to remove an image from another's dataset, change its ownership, then add it to your dataset. (I'd have to try it to be sure.) If students import into designated datasets of their own then a group owner could periodically run a Python script or somesuch to change those images to being theirs in their dataset.

Sorry I don't have better news on this front.

Cheers,
Mark

[Chris Cole]

Hi Mark,

Thanks for the quick reply.

I doubt read/write is suitable for us, so will work with the current setup. I'll investigate scripting when we're further down the line.

Cheers,

Chris