Importer assigning data to wrong user (OMERO.insight)

[davemason]

Hello community,

I've just started working with OMERO and have run into some odd behaviour as I'm playing with the virtual appliance and interfacing with OMERO.insight. I'm having problems with the importer (1) Not allowing the creation of custom project names/experiment names and (2) Imported data being assigned to other users (possibly only the group owner - TBC).

Here's how I reproduce the problem:
- First login to OMERO as root user. Make three users, [baggins, gamgee, took]. Create a private group [baggins lab] and assign the three users to the group. Make baggins the owner. Logout.
- Login as baggins, import some data, specifying custom Project [Project A] and experiment names [Experiment 01]. Wait for import and confirm successful upload. Logout.

01-BagginsData.PNG (13.33 KiB) Viewed 1667 times

-Login as gamgee, try to repeat the previous step. Here, when I click "New..." to specify [Project B] / [Experiment 02], the dropdown box does not update. If I pull down the dropdown box, my custom titles have been added but I can't select them. If I click upload anyway, the data upload but then don't appear in the users Projects. Logout.
- Login as baggins, and see gamgee's uploaded data (unassigned to a project - Pos1) and empty folders (of the same Project/Experiment name as specified but not selected in the dropdown by gamgee).

01-BagginsDataMess.PNG (10.13 KiB) Viewed 1667 times

If any one has any thoughts on why this is happening, I would be most appreciative of the input. Surely, the inability for non-owner users of a private group to specify custom experiment names isn't a feature?

Best,

Dave

[bpindelski]

Hi Dave,

The behaviour you described is indeed unusual. We have done preliminary investigation and project folder disappearence seems to occur between multiple user log ins. That issue has been ticketed (https://trac.openmicroscopy.org.uk/ome/ticket/12055) and will be dealt with.

In the meantime - I have discovered that restarting Insight fully between switching users tends to fix the issue for the moment.

Regards,
Blazej

[davemason]

Thanks! I've confirmed the behaviour on my end, and a restart of insight between users does indeed solve the problem. That's all the workaround I need for the time being.