airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (AIRAVATA-3029) Custom output viewers
Date Mon, 01 Jul 2019 19:14:00 GMT


ASF subversion and git services commented on AIRAVATA-3029:

Commit 5be3f3eeb6c42fabd0aca6f92821a5629ac1b3cc in airavata-django-portal's branch refs/heads/master
from Marcus Christie
[;h=5be3f3e ]

AIRAVATA-3029 Handle missing app interface, app output

> Custom output viewers
> ---------------------
>                 Key: AIRAVATA-3029
>                 URL:
>             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

View raw message