You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Eroma (JIRA)" <ji...@apache.org> on 2017/08/29 20:39:00 UTC
[jira] [Assigned] (AIRAVATA-2510) Revamping application catalog in
Django gateway implementation
[ https://issues.apache.org/jira/browse/AIRAVATA-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eroma reassigned AIRAVATA-2510:
-------------------------------
Assignee: Eldho Mathulla
> Revamping application catalog in Django gateway implementation
> ---------------------------------------------------------------
>
> Key: AIRAVATA-2510
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2510
> Project: Airavata
> Issue Type: Task
> Components: PGA PHP Web Gateway
> Affects Versions: 0.18
> Reporter: Eroma
> Assignee: Eldho Mathulla
> Fix For: 0.19
>
>
> 1. Current application catalog implementation is a 3 step process.
> 2. Adding an application or a tool in to the gateway requires adding a module, interface and a deployment in order to be available for gateway users to use and submit experiments.
> 3. These 3 steps are managed in 3 different interfaces in the gateway portal, and only available for gateway admins.
> 4. Same set of information is required but when implementing in django framework focuses on
> # Make adding application more user freidnly
> # Make application catalog to different user groups as well, power users, faculty, not just gateway admins
> # Introduce better presentation of inputs in applications, radio buttons, check boxes, dropdowns
> # Easy navigation and retrieval for users
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)