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.
- Timestamp:
-
03/11/11 09:42:58 (13 years ago)
- Author:
-
jmoore
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
|
initial
|
v1
|
|
| 1 | | 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'''" (or whatever the project name becomes), then it should only be accessible via this mechanism, and no longer through raw OmeroTables. |
| | 1 | 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. |
| 2 | 2 | |
| 3 | | Users should be able to select the columns that they would like to see, as well as filter rows by some parameters. |
| | 3 | 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): |
| | 4 | {{{ |
| | 5 | bin/omero med export --csv --columns=0,1,2-5,10 --rows="%(0)s > 10" |
| | 6 | }}} |
| | 7 | |
| | 8 | 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'''. |
| 4 | 9 | |
| 5 | 10 | Further, as soon as some export functionality is ready, we should get feedback from the researchers. |
| | 11 | |
| | 12 | '''''Note: use of "med" above is subject to decision on the name of the project''''' |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.11587 sec.)
