Task #10325 (new)
Opened 11 years ago
Last modified 8 years ago
Introduce ImportSet — at Initial Version
| Reported by: | jamoore | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 5.0.0-beta1 |
| Component: | OmeroFs | Version: | n.a. |
| Keywords: | fs | Cc: | fs@…, wmoore, cxallan |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Currently the hierarchy is:
/Fileset
-> /OriginalFile collection
-> /Image collection
The issue is that on import clients may not know what all is contained in the fileset, and therefore there will need to be a "pulling apart" (or the use of a DirectoryReader in Bio-Formats which reads everything a la ImportCandidates).
If the import action of the clients creates a ImportSet rather than a Fileset, there will be fewer overall top-level containers, and the server can adjust the Filesets as necessary. (NB: It would be important the clients could delete a single fileset from that import set)
The new hierarchy might look something like:
/ImportSet
-> /OriginalFile collection
-> /Fileset collection
-> /Image collection
-> /OriginalFile collection (reused pointers?)
Jean-Marie has raised the issue that we will need to also examine how we deal with multi-image filesets, possibly linking Fileset under Dataset, though this cannot be done for the demo. In which case, we may want to omit ImportSet (i.e. this ticket) as well.
