Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
- Timestamp:
-
09/16/11 10:03:09 (13 years ago)
- Author:
-
jburel
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
-
Property
Milestone
changed from
OMERO-Beta4.3.2
to
OME-5.0
-
|
v3
|
v4
|
|
| 1 | | So far we have focused on the project silo model. The data for which was manually anonymised, extracted and transfer |
| | 1 | So far we have focused on the project silo model. The data for which was manually anonymised, extracted and transferred from the mssql servers on the NHS network at HIC to the HIC/OMERO server on the UNI network. |
| 2 | 2 | |
| 3 | 3 | It is going to be useful for other stories that we develop the dataset silo model as a parent layer of the project silo within this pilot. |
| … |
… |
|
| 22 | 22 | |
| 23 | 23 | === Implementation === |
| 24 | | A dataset silo in OMERO should be exportable to a re-anonymized project silo. If the work for #4652 (server-side API), then this work can be implemented as sub |
| | 24 | A dataset silo in OMERO should be exportable to a re-anonymized project silo. If the work for #4652 (server-side API), then this work can be implemented as sub-directories in the silo fs repository. Along with the links between input tables and output tables, metadata about any operations (see #6321) that were performed on the data should also be recorded. |
| 25 | 25 | |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.12400 sec.)
