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.

Changes between Version 3 and Version 4 of Ticket #2128


Ignore:
Timestamp:
05/19/11 07:42:35 (13 years ago)
Author:
jmoore
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2128

    • Property Component changed from to OmeroFs
    • Property Summary changed from FS Improvements to FS Data de-duplication
  • Ticket #2128 – Description

    v3 v4  
     1== Goal == 
     2 
     3A major barrier to adoption by many sites is the fact that OMERO (4.2 and earlier, as well as much of 4.3) stores binary pixel data in an optimized internal format. This ''duplication'' of the data (the original file and then the byte array under `/OMERO/Pixels`) along with possible duplicated backups of that data can overwhelm available storage. The goal of this work is to phase out the use of the internal data format in favor of ccessing binary data directly from the files via BioFormats. Data previously converted into the interior file format will remain so, if the related original files were not archived.  
     4 
     5== Phase 1 == 
     6 
     7The initial phase will focus on having a user view on their files as they sit on the filesystem. A prototype FS viewer is already in place in Insight ('''URL/SCREENSHOT HERE'''), and as of 4.3, the server is already directly accessing some files, like very wide & tall SVS files. (In some tickets this is referred to as "fs-lite") 
     8 
     9 
     10=== Stories include: === 
     11 
     12 * #978   CMS like view of files 
     13 * #2728  Accessing binary data 
     14 * #3162  Handle read-only directories mounted in FS  
     15 * #2307  Standardize repository paths on unix path-style  
     16 * #5305  Handle integration with legacy repository  
     17 * #2595  FS cleanup tasks 
     18 * #870   Original file service improvements  
     19 * #5158  FS/PixelData follow-on  
     20 
     21== Phase 2 == 
     22 
     23The second phase, which may accompany the initial release, will focus on stability and any features which users request during phase 1 testing. 
     24 
     25=== Stories include: === 
     26 
     27 * #1740  Support for multiple FS File Server  
     28 * #988   File corruptions/immutability guarantees under OmeroFs  
     29 * #909   OriginalFiles need an organizational structure  
     30 * #4033  Have one user import data for another.  
     31 
     32== Phase 3 == 
     33 
     34There are several extended features that have been requested but which are not critical to the central goal of "data de-duplication". As time permits (and according to user-based priority), these will be added. 
     35 
     36=== Stories include: === 
     37 
     38 * #2850 User management of repositories 
     39 * #914  Support archiving to tape via OMERO.fs  
     40 * #836  Quotas for user  
     41 
     42== Phase N : Notification == 
     43 
     44An advanced feature of FS includes integration with native FS notifications. These notifications are the basis for the DropBox feature, which has been been the sole FS-feature to date. If notifications are integrated into FS proper, then the DropBox feature may be phased out. 
     45 
     46=== Stories include: === 
     47 
     48 * #4032  Allow Project/Datasets for DropBox?  
     49 * #1445  Remote DropBox  
     50 * #1230  RepositoryInfo rework - Interface may be removed 
     51 * #1433  FS should provide a method getSupportEventTypes()  
     52 * #1571  FS should obtain parameters without duplication  
     53 
     54  
     55 
     56---- 
    157 
    258 

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.16910 sec.)

We're Hiring!