You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@airavata.apache.org by "Marcus Christie (JIRA)" <ji...@apache.org> on 2019/04/18 16:42:00 UTC

[jira] [Updated] (AIRAVATA-2987) Support for optional input files

     [ https://issues.apache.org/jira/browse/AIRAVATA-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcus Christie updated AIRAVATA-2987:
--------------------------------------
    Description: Ideally I would like to see us move away from optional input files. Instead we could have an application input that would be 1) *optional* and 2) *type URI_COLLECTION*.  That would require some support from the backend, however.  (was: Ideally I would like to see us move away from optional input files. Instead we could have an application input that would is 1) *optional* and 2) *type URI_COLLECTION*.  That would require some support from the backend, however.)

> Support for optional input files
> --------------------------------
>
>                 Key: AIRAVATA-2987
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2987
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: Django Portal
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
>
> Ideally I would like to see us move away from optional input files. Instead we could have an application input that would be 1) *optional* and 2) *type URI_COLLECTION*.  That would require some support from the backend, however.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)