User Story #4651 (closed)
Opened 13 years ago
Closed 11 years ago
HIC: full data export + UX
| Reported by: | jamoore | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | Unscheduled |
| Component: | General | Keywords: | n.a. |
| Cc: | saloynton | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description (last modified by jmoore)
The first step toward interacting with the researchers is the export of existing data sets. This is the inverse operation to #4650 (import) and should also be fully audited. For this reason, once a table has been marked as "med", then it should only be accessible via this mechanism, and no longer through raw OmeroTables.
Users should be able to select the columns that they would like to see, as well as filter rows by some parameters. As an example (exact options need to be improved):
bin/omero med export --csv --columns=0,1,2-5,10 --rows="%(0)s > 10"
If a user does not have authorization to access the given columns and/or rows, then a SecurityViolation (or subclass) should be thrown, and handled appropriately by med.py.
Further, as soon as some export functionality is ready, we should get feedback from the researchers.
Note: use of "med" above is subject to decision on the name of the project
Change History (3)
comment:1 Changed 13 years ago by jmoore
- Description modified (diff)
comment:2 Changed 13 years ago by cxallan
- Milestone changed from OMERO-Beta4.3 to Unscheduled
comment:3 Changed 11 years ago by jamoore
- Resolution set to invalid
- Status changed from new to closed
Closing all specific HIC tasks.