[ome-users] Question about omero FS configurability

Mark Carroll (Staff) m.t.b.carroll at dundee.ac.uk
Tue Feb 5 12:45:55 GMT 2019


On 2/5/19 8:00 AM, Jake Carroll wrote:

> root at omero-prod-gen3:/omero.datastore/ManagedRepository/usernameHere_3253/2019-01/16/15-33-30.273#
>
> So, I've two questions:
>
>  1. Is the name of the directory more...configurable? I'd dearly love to
>     be able to use "real" names of experiments or work as is found in
>     the OMERO GUI itself, rather than a cryptic string of things. Is it
>     possible to use more usable names, for ease of navigability? An
>     example might be:
>
> root at omero-prod-gen3:/omero.datastore/ManagedRepository/usernameHere_3253/2019-01/16/GFP_bright_red_experiment_blah
>
> Is something like this possible? Ultimately, trying to figure out how
> configurable the directory structure OMERO.fs provides us really is -
> and how we can massage it around to do the things we want, for our users.

The server sets up the path in ManagedRepositoryI.createTemplatePath.
The project or screen into which the import is occurring that was
requested by ImportLibrary via
http://downloads.openmicroscopy.org/latest/omero5.4/api/slice2html/omero/grid/ImportSettings.html
is passed through the server's ManagedImportRequestI into the metadata
store's TargetProcessor for linking. That's available at import time but
it's only after the metadata step of ManagedImportRequestI that other
container names encoded in the uploaded files themselves are known. Of
course, the template path setup is done before the files are even
transferred to the server: it broadly relies on what it is told via the
import settings to figure out what that path should be so the
configuration options at
https://docs.openmicroscopy.org/latest/omero5.4/sysadmins/fs-upload-configuration.html#template-path
fit within what is then known.

Sorry it's not easier! Generally the repository path structure is of
most interest for:

* offering read-only network mounts of repository subdirectories based
on the group into which data was imported
* ensuring that new imports arrive onto new disks that still have plenty
of space, e.g., as at
https://docs.openmicroscopy.org/latest/omero5.4/sysadmins/repository-move.html#extending-the-managed-repository

-- Mark

The University of Dundee is a registered Scottish Charity, No: SC015096


More information about the ome-users mailing list