Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Requirement #3535 (new)

Opened 10 years ago

Last modified 5 years ago

OME-XML/TIFF import/export — at Version 3

Reported by: jamoore Owned by:
Priority: critical Milestone: OMERO-Beta4.3
Component: n.a. Keywords: n.a.
Cc: jburel, mtbcarroll, cxallan, mlinkert, jrswedlow, ruben.munoz@…, pearu.peterson@…, jay_copeland@… Business Value: n.a.
Total Story Points: n.a. Roif: n.a.
Mandatory Story Points: n.a.

Description (last modified by jrswedlow)

OME-XML (Josh, Jean-Marie, Chris, Andrew)

 * Requirements for improving OME-TIFF
    * Institute in Estonia
        * Putting 2000 images in one OME-XML
        * Lots of annotations in comments, long, boolean
    * Harvard Screening (Jay Copeland)
        * Export a single row / column / well group
    * EMBL Screening (Ruben Muñoz, Jan Ellenberg)
        * Not duplicating XML for each field, _plane_, etc.
    * Jean-Marie using OME-TIFF to communicate with ImageJ

 * OME-TIFF "lite", "basic"?
    * Just for display

 * Namespaces for annotations, etc.

 * Export
    * Where will we export from? (cF. cluster example)
    * Doing it in the client?
    * Andrew: Transporting one big TIFF and the client can piece it apart
    * Chris: exporter has to be modular
    * Jean-Marie: a danger is there are no clear strategies on namespace
    * Chris: Delete-like configuration, then choose the images
        * Josh: Instrument and a single plane?
        * Jean-Marie & Chris: Wait.

 * Using Metadata levels?
    * Josh: something similar in delete and in upcoming chgrp
    * Metadata levels are currently just 4 options: ALL, PIXELS-ONLY, ROI
    * Intentation as opposed to implementation
        * Not as flexible as delete
        * That flexibility is probably overkill for export
    * Then technically do the export
        * TIFF per file
        * All ZIP'ed
    * Andrew: Metadata-only files?
        * OME-TIFFs as the companion file with minimal spec
        * Pseudo-schema on top of 2010-06 in OME-TIFF (only <OME uuid=""/>)
        * Lots of coding work

 * Steps
    * Delete-style options
    * Data-layout options (zip, single plane, etc.)
    * Model: how to split the files. (release before server?)
        * Andrew: publish but don't release (PREVIEW)
    * SA best practices
        * Have to show it in insight/web!
    * Round-tripping
        * LSIDs working
        * Have a graph which was written in the original import (utility of that?)
    * Full OmeroReader implementation (all 400 methods)
        * a couple of individuals; reverse of the Store
    * Timescale: something by mid- to late-January

Change History (3)

comment:1 Changed 10 years ago by jburel

  • Cc mlinkert-x added

comment:2 Changed 10 years ago by jburel

  • Description modified (diff)

comment:3 Changed 10 years ago by jrswedlow

  • Description modified (diff)
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

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

We're Hiring!