Task #4666 (new)
Opened 14 years ago
Last modified 13 years ago
Derived columns must provide metadata to that effect
| Reported by: | jamoore | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | General | Version: | n.a. |
| Keywords: | n.a. | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Assuming the execution of one or more OmeroScripts produced a new column, this execution should be described in the column metadata for tracing provenance.
If possible, this should be handled within the system:
bin/omero med execute Script:5 Data:6 --join-output=ProjectCHI
would produce some output table which get joined back to the original table via the "ProjectCHI" column.
Change History (2)
comment:1 Changed 13 years ago by cxallan
comment:2 Changed 13 years ago by jmoore
- Milestone changed from OMERO-Beta4.3 to Unscheduled
Moving to Unscheduled since 4.3 is going into freeze.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Referencing ticket #4650 has changed sprint.