In place import : changing the symlink name
Posted: Wed Jun 28, 2017 4:30 pm
I'm using in place import to store some files with OMERO and we have a perhaps unique situation that at the point of doing the import, the file name that we are linking to is an undecipherable hash - we use the actual file name as a key/value pair that can be retrieved but when we look at the files with omero web, we see the hash on the left pane and the only way to get to the original file name is by expanding the 'key value pairs' tab on the right and searching for the original file name.
Now I agree the simpler solution would be to pass the original file name to the in place import command, but for reasons I'd rather not get into, that is not an option for us.
Here is an idea of what the files look like, once imported to OMERO:
So in omero web, we would see hashes like 8898a7abf72344d18bc5301d525cf15f on the left pane.
We would like the hash to be changed to something readable - which we know at the time of doing the in place import.
So the ask is if it is possible to have the in place import use a user supplied symlink, where we supply it specifically to the tool. So then the above file structure could look like this:
thanks,
thushara (S/W Engineer @ Allen Institute for Cell Science)
Now I agree the simpler solution would be to pass the original file name to the in place import command, but for reasons I'd rather not get into, that is not an option for us.
Here is an idea of what the files look like, once imported to OMERO:
- Code: Select all
/omero/managed/omero_2/2017-06/
├── 02
├── 26
├── 22-49-39.354
│ │ └── 8898a7abf72344d18bc5301d525cf15f -> /file-storage-service/data/dev/5f/8898a7abf72344d18bc5301d525cf15f
│ ├── 22-49-39.354.log
│ ├── 22-49-47.433
│ │ └── da81347a829244ff84911640409cfe2c -> /file-storage-service/data/dev/2c/da81347a829244ff84911640409cfe2c
│ ├── 22-49-47.433.log
│ ├── 22-49-55.292
│ │ └── a2c5652bdc4b497f894cc166ec49e923 -> /file-storage-service/data/dev/23/a2c5652bdc4b497f894cc166ec49e923
So in omero web, we would see hashes like 8898a7abf72344d18bc5301d525cf15f on the left pane.
We would like the hash to be changed to something readable - which we know at the time of doing the in place import.
So the ask is if it is possible to have the in place import use a user supplied symlink, where we supply it specifically to the tool. So then the above file structure could look like this:
- Code: Select all
/omero/managed/omero_2/2017-06/
├── 02
├── 26
├── 22-49-39.354
│ │ └── stem_cell_30_days.tiff -> /file-storage-service/data/dev/5f/8898a7abf72344d18bc5301d525cf15f
│ ├── 22-49-39.354.log
│ ├── 22-49-47.433
│ │ └── stem_cell_60_days.tiff -> /file-storage-service/data/dev/2c/da81347a829244ff84911640409cfe2c
│ ├── 22-49-47.433.log
│ ├── 22-49-55.292
│ │ └── differentiated_1_day.tiff -> /file-storage-service/data/dev/23/a2c5652bdc4b497f894cc166ec49e923
thanks,
thushara (S/W Engineer @ Allen Institute for Cell Science)