Path/names of files should be sensible to users

[jamoore]

In order to increase the users' trust in the FS, all files stored in the managed repository should to the extent possible be easily identifiable by their paths. Similarly, all queries returning OriginalFile objects should return objects which are what the user expects. This will require (numerous) trade-offs between what the user really wants (a full OS-level filesystem) and what we can sensibly offer while also maintaining the Postgres DB.

Probably the most important aspect of making the names sensible is to have the correct (bug not too much) configurability in the clients and API. And what's not configurable should be simple and standardized.

[wmoore]

It seems to me that it's essential for the clients to support this path in their UI if we're going to ask users to configure it in the clients. It's tricky enough to make an intuitive UI for path configurability if you don't give the user any feedback on how their choice affects anything.

So we have to allow users to browse their FS data via path in the clients before we ask them to configure it (IMHO).

[jmoore]

I disagree that we have to allow users to browse their FS data first. I think we can start by showing them how it will map (C:\Users\me\Desktop\Data\Good\OME-TIFF\Tuesday\foo.ome.tif --> OME-TIFF\Tuesday\foo.ome.tif). But otherwise, agreed. We need to provide them good feedback so they know what to expect.

[agilo]

Updated status, related task in progress

[jmoore <josh@…>]

(In [da774d18191d63c7ddc2ce4f6a7d7d95b22fbdc9/ome.git] on branch develop) Initial draft of the new Fileset objects (See #9821)

Though there are likely other types and fields needed,
I'm uploading this so everyone can take a first look.

[jmoore]

Demoed today. See #10310.

[agilo]

Updated status, related task in progress

[jamoore]

Largely with demo 2 and certainly with demo 3 this work can be considered stable.

[agilo]

Updated status, related task in progress