fslite (phase 0 of FS)

[jamoore]

This requirement breaks down phase-0 of the whole FS requirement as defined under #2128. Stories are multiply linked here and under #2128 in order to provide a cleaner overview of the status of 4.5.

The primary goal of fslite is to have all client imports consist solely of uploading files to OMERO as OriginalFiles with human-readable paths (/OMERO/ManagedRepository/<user>/<date>/some.dir/some.file) and then registering for server-side import. The managed repository is not (yet) intended for user-consumption. Instead, it is intended to:

1. Reduce the duplication caused by the parsed data of /OMERO/Pixels;
2. Provide a recovery-mechanism for system administrators in the case of a total loss of the OMERO DB;
3. and, as a result, increase the overall user-trust in OMERO to allow for deletion of the initially acquired data.

In order to facilitate the later phases of FS as described under #2128, several issues must be addressed:

1. All files must be registered with the security system to prevent unauthorized access.
2. Newly created directories (.../some.dir-1/...) created due to naming conflicts caused by imports of similar directory structures should be sensible to the average user.

[jmoore]

Will's screenshot from FS demo 1

[pwalczysko]

Petr's screenshot from FS Demo 2

[pwalczysko]

Petr's screenshot from FS Demo 2 b

[jamoore]

Considering phase 0 good and well done with 5.0.0, and well improved over the patch releases. The few remaining stories will either be closed (moved to trello) or doubly-linked elsewhere.