[
https://issues.apache.org/jira/browse/AIRAVATA-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16875230#comment-16875230
]
ASF subversion and git services commented on AIRAVATA-3029:
-----------------------------------------------------------
Commit f2b68c7c8576e36d0e038df2cb90ee823e381ec7 in airavata-django-portal's
branch refs/heads/master from Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=f2b68c7 ]
AIRAVATA-3029 Add in any output view providers added to the app interface
> 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.)
> * [x] 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.
> * [x] add display name for output view providers
> * [x] rename the default download output view provider to just "default"
> since in the future we might have it do more than just download
> * [x] only add the "default" view provider if not already in the list
> * [x] only show the outputs when the experiment is completed
> * [x] provide the output file to the generate_data method
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
