Task #5016 (closed)
Opened 8 years ago
Closed 7 years ago
RapidService: Rapid XML, Staging and unstaging data
| Reported by: | dzmacdonald | Owned by: | dzmacdonald |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | General | Version: | n.a. |
| Keywords: | n.a. | Cc: | jos@…, jamoore, jburel, jrswedlow |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | 0.0d |
| Sprint: | n.a. |
Description
There needs to be an extension of the Rapid xml specification to allow different types of staging and unstaging data.
- Cluster and script are both OMERO agnostic.
- The Cluster is OMERO aware, the script is OMERO agnostic.
- The Cluster and script are OMERO aware.
As each of these methods require different types of pre/post staging code, it is necessary for the rapid xml to define what is required.
Change History (3)
comment:1 Changed 8 years ago by jburel
- Sprint changed from 2011-04-21 (10) to 2011-05-05 (11)
comment:2 Changed 8 years ago by dzmacdonald
- Milestone changed from OMERO-Beta4.3 to Unscheduled
- Sprint 2011-05-05 (11) deleted
comment:3 Changed 7 years ago by jburel
- Remaining Time changed from 1 to 0
- Resolution set to invalid
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Moved from sprint 2011-04-21 (10)