below details of the OMERO version i am using and the problem i am facing
OMERO version used:
OMERO 5.5.1 docker compose
I am setting an in-place import for all the images as i cannot afford to import the images directly into the docker compose. Simply a problem with space.
For the in place import in docker compose, i have set up the yml file so that there is a line under the OMERO server volume in which the remote folder (which in my case is on a NAS) with the images is mapped:
As it stand i can easily import all the images that are located in the NAS under the folder OMEROdata.
this is the typical expression i use
bin/omero import --transfer=ln_s /external_data/IMG_7106.JPG --sudo root -u smsg_manager -g smsg -T Dataset:name:imports
However, the folder OMEROdata will soon be populated with images from various users and it will make the in-place import very difficult as I cannot see how i can easily import “x” images if there are a hundresds of them in a folder, without any structure.
So, the logic is that the users that can access OMEROdata start building new directories and let the sysadmin to do the in place import from specific directories.
I tried to add a file which was in a subdirectory of OMEROdata (e.g. /mnt/OMEROdata/newfolder/IMG009.jpg) but it didn’t work.
Essentially the error message is “UNREADABLE_FILE”
Any clue on how this issue can be overcome?
Do i need to modify the line in the yml file? Do i simply need to change the --transfer=ln_s with the path of the linked directory?
thanks a lot,