[
https://issues.apache.org/jira/browse/AIRAVATA-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Christie updated AIRAVATA-3029:
--------------------------------------
Description:
Develop a way for custom output viewers to be registered as plugins in the
Django portal.
h5. TODO
* [x] Add METADATA column to experiment_output, process_output,
application_output (similar to METADATA on experiment_input, etc.)
* [ ] One problem I've encountered is that experimentOutput.metadata is
consulted 'output-view-providers', but these are copied from the
applicationOutput.metadata at the time of the experiment's creation. If the
output-view-providers are updated on applicationOutput.metadata after the
experiment is created then those aren't reflected in experimentOutput.metadata.
One approach would be to merge in any output-view-providers from
applicationOutput.metadata.
was:
Develop a way for custom output viewers to be registered as plugins in the
Django portal.
h5. TODO
* [x] Add METADATA column to experiment_output, process_output,
application_output (similar to METADATA on experiment_input, etc.)
> Custom output viewers
> ---------------------
>
> Key: AIRAVATA-3029
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3029
> Project: Airavata
> Issue Type: Bug
> Components: Django Portal
> Reporter: Marcus Christie
> Assignee: Marcus Christie
> Priority: Major
> Fix For: 0.19
>
>
> Develop a way for custom output viewers to be registered as plugins in the
> Django portal.
> h5. TODO
> * [x] Add METADATA column to experiment_output, process_output,
> application_output (similar to METADATA on experiment_input, etc.)
> * [ ] One problem I've encountered is that experimentOutput.metadata is
> consulted 'output-view-providers', but these are copied from the
> applicationOutput.metadata at the time of the experiment's creation. If the
> output-view-providers are updated on applicationOutput.metadata after the
> experiment is created then those aren't reflected in
> experimentOutput.metadata. One approach would be to merge in any
> output-view-providers from applicationOutput.metadata.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
