Ticket #78 (closed task: fixed)
Opened 2007-03-22T10:25:23-05:00
Last modified 2011-02-02T04:45:00-06:00
Implement OMERO upload and download logic
| Reported by: | curtis | Owned by: | curtis |
|---|---|---|---|
| Priority: | critical | Milestone: | |
| Component: | ome-io | Severity: | non-issue |
| Keywords: | plugins | Cc: | |
| Blocked By: | Blocking: |
Description (last modified by curtis)
Currently, OME I/O contains logic to communicate with an OME database. For downloading, loci.ome.io.OMEReader allows transparent access to individual planes on the server. For uploading, loci.ome.io.OMEWriter allows client-side import of images onto the server.
The next step is to implement the same support for the OMERO database: OMEROReader and OMEROWriter. This implementation would allow the Data Browser, VisBio, and other applications to gain OMERO-related features nearly for free.
The easiest way to implement the classes is probably to adapt code from OMERO.insight and OMERO.importer.
Once the code exists, the "Download from OME" and "Upload to OME" plugins should be updated to work with both OME and OMERO.
Change History
comment:5 Changed 2007-11-30T09:54:30-06:00 by melissa
- Severity set to non-issue
OMEROReader added in r3429 - next step is to add ImageJ plugin that calls OMEROReader (similar to OMEPlugin).
comment:6 Changed 2008-01-18T16:03:18-06:00 by curtis
- Owner changed from melissa to allison
The "Download from OME" plugin calls OMEROReader. We still need an OMEROWriter, though, and LociUploader needs to call it as appropriate.
comment:8 Changed 2008-09-24T15:31:40-05:00 by curtis
- Owner changed from allison to curtis
- Component changed from bio-formats to ome-io
comment:10 Changed 2011-02-02T04:45:00-06:00 by curtis
- Status changed from new to closed
- Resolution set to fixed
moved to ome:#4084