[
https://issues.apache.org/jira/browse/OODT-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesha Sudasingha updated OODT-986:
-----------------------------------
Description:
As of now, OODT provides a webapp to monitor component status, ingested files
(and metadata) and workflow status through a [wicket|https://wicket.apache.org]
component (available under
[_webapp_|https://github.com/apache/oodt/tree/master/webapp] directory) based
UI. This UI lacks few important features like searching capability and lacks in
stability at the moment. Furthermore, the existing UI is not user friendly and
some occasions prints stack traces when errors occur in backend. To address all
these loopholes, we are thinking of implementing a new UI based on a modetn
front end framework.
As of now, React is the suggested framework while other suggestions can be
discussed as well. The original plan is to have a component based webapp, where
individual components can be used out of the box when OODT based apps are being
developed by users or embed/add these components to their existing webapps.
When these components are developed individually, they can be integrated
together to build the new OPSUI webapp.
[*These*|https://balsamiq.cloud/sgp43nx/pdsiadc] UI wireframes were created by
[~bugg_tb] as a starting point. Some information on this issue is available
under OODT-1001 as well.
To support the web app developments, an existing set of REST APIs (JAX-RS) are
available under [webapp|https://github.com/apache/oodt/tree/master/webapp]
module. Few minor modifications may require to be made to achieve all the
suggested functionalities from the new user interface.
Please refer the following links for more information on OODT:
- OODT Confluence Documentation -
https://cwiki.apache.org/confluence/display/OODT/Home
- OODT APIs - https://cwiki.apache.org/confluence/display/OODT/Apache+OODT+APIs
was:
As of now, OODT provides a webapp to monitor component status, ingested files
(and metadata) and workflow status through a [wicket|https://wicket.apache.org]
component (available under
[_webapp_|https://github.com/apache/oodt/tree/master/webapp] directory) based
UI. This UI lacks few important features like searching capability and lacks in
stability at the moment. Furthermore, the existing UI is not user friendly and
some occasions prints stack traces when errors occur in backend. To address all
these loopholes, we are thinking of implementing a new UI based on a modetn
front end framework.
As of now, React is the suggested framework while other suggestions can be
discussed as well. The original plan is to have a component based webapp, where
individual components can be used out of the box when OODT based apps are being
developed by users or embed/add these components to their existing webapps.
When these components are developed individually, they can be integrated
together to build the new OPSUI webapp.
[*These*|https://balsamiq.cloud/sgp43nx/pdsiadc] UI wireframes were created by
[~bugg_tb] as a starting point. Some information on this issue is available
under OODT-1001 as well.
To support the web app developments, an existing set of REST APIs (JAX-RS) are
available under [webapp|https://github.com/apache/oodt/tree/master/webapp]
module. Few minor modifications may require to be made to achieve all the
suggested functionalities from the new user interface.
Please refer the following links for more information on OODT:
[1] OODT Confluence Documentation -
https://cwiki.apache.org/confluence/display/OODT/Home
[2] OODT APIs -
https://cwiki.apache.org/confluence/display/OODT/Apache+OODT+APIs
> A React based new UI for OPSUI
> ------------------------------
>
> Key: OODT-986
> URL: https://issues.apache.org/jira/browse/OODT-986
> Project: OODT
> Issue Type: Improvement
> Components: opsui
> Reporter: Imesha Sudasingha
> Priority: Major
> Labels: GSoC2019, gsoc2019
>
> As of now, OODT provides a webapp to monitor component status, ingested files
> (and metadata) and workflow status through a
> [wicket|https://wicket.apache.org] component (available under
> [_webapp_|https://github.com/apache/oodt/tree/master/webapp] directory) based
> UI. This UI lacks few important features like searching capability and lacks
> in stability at the moment. Furthermore, the existing UI is not user friendly
> and some occasions prints stack traces when errors occur in backend. To
> address all these loopholes, we are thinking of implementing a new UI based
> on a modetn front end framework.
> As of now, React is the suggested framework while other suggestions can be
> discussed as well. The original plan is to have a component based webapp,
> where individual components can be used out of the box when OODT based apps
> are being developed by users or embed/add these components to their existing
> webapps. When these components are developed individually, they can be
> integrated together to build the new OPSUI webapp.
> [*These*|https://balsamiq.cloud/sgp43nx/pdsiadc] UI wireframes were created
> by [~bugg_tb] as a starting point. Some information on this issue is
> available under OODT-1001 as well.
> To support the web app developments, an existing set of REST APIs (JAX-RS)
> are available under
> [webapp|https://github.com/apache/oodt/tree/master/webapp] module. Few minor
> modifications may require to be made to achieve all the suggested
> functionalities from the new user interface.
> Please refer the following links for more information on OODT:
> - OODT Confluence Documentation -
> https://cwiki.apache.org/confluence/display/OODT/Home
> - OODT APIs -
> https://cwiki.apache.org/confluence/display/OODT/Apache+OODT+APIs
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
