RFE: do not ignore image name on import

[mtbcarroll]

If I set an image name in the metadata of my OME-TIFF then it seems to be ignored upon import with the CLI. Perhaps it would be nice to name the image for that given name instead of falling back to the filename.

[mtbcarroll]

shows the problem

[pwalczysko]

But that draws a precedent which I am not sure about: we are telling our users that omero never changes the name of the file and the default image name is taken from the filename (certainly for the purposes of the webtagging app which even ignores if you change the name in omero client).

[mtbcarroll]

Webtagging should be looking at the client path from the fileset entry which still provides the original filename, if it isn't already, and OMERO will also retain the same filename (after platform-specific tweaks) in the managed repository. I'm just talking about the image name as already editable in the clients, not the filename -- after all there's not a one-to-one mapping between them.

[pwalczysko]

But the user thinks there is such mapping... Possibly you are right, but still do not want to be the one to explain this to any user :)

[mtbcarroll]

I don't want to explain to them why we threw away the original metadata that the file included. (-: There may be no good solution here?

[mtbcarroll]

pwalczysko draws my attention to ​https://github.com/MicronOxford/webtagging/issues/22#issuecomment-221622205 --

For files that have a concept of image name different from the filename (typical for formats that have a series of images, e.g., volocity), auto-tag should use the image name instead of the filename.

While importing the image to omero, you only select "20160511_199.mvd2" (which then picks up all the files within Data/). These files are actually 16 images, and each one has a name besides any of the filenames. This is their names in omero (bioformats reads their names automatically) ...

[mtbcarroll]

See also ​https://github.com/openmicroscopy/design/issues/57.