Calipseo is FAO web- based platform for national Fisheries Authorities to streamline management of fisheries data and the production, analysis and reporting of fishery statistics.
1
stars
0
forks
source link
[CALR-30] Investigate capacity of shiny-calipseo to load a single module as widget #30
Issue migrated from JIRA: https://sdlc.review.fao.org/jira/browse/CALR-30
Creator/Reporter: Emmanuel Blondel @eblondel
Assignee: Alexandre Bennici @abennici
Priority: Medium
Status: To Do
Date of creation: 2021-11-25T20:26:22.000+0000
The idea is to introduce progressively the concept of widget. Widgets would another category of module that would work a standalone and would focus on a very specific item. It could be a linechart, a piechart, a single map. To work as standalone, the overall app should search for a URL param 'module' id/name, and if available, the app would work as 'fluid' (for embedded mode) instead of dashboard (relates to CALR-19). In this way the app could be embedded in Calipseo with a single widget context, instead of a dashboard context including many widget.
The granularity of a widget may vary. A Widget could be actually built on top of a module that has more or less features / UIs and is more and less complex. Whatever module initially mapped to a dashboard 'page' could be considered as widget, but a widget could be managed in the source code and loaded ONLY in a embedded mode, and not necessarily used in the dashboard. In other words, similarly as the shiny-calipseo app allows to display different country dashboard contexts, it may allow to display different module contexts.
For example, we could think of a single widget that displays countings of vessels licenses status. It would be set as module, not necessarily available in the dashboard, but loadable by targeting it through shiny app URL; to embedd it in the Calipseo webapp.
cc [~alexandre.bennici@fao.org] related to CALR-19
The idea is to introduce progressively the concept of
widget. Widgets would another category of module that would work a standalone and would focus on a very specific item. It could be a linechart, a piechart, a single map. To work as standalone, the overall app should search for a URL param 'module' id/name, and if available, the app would work as 'fluid' (for embedded mode) instead of dashboard (relates to CALR-19). In this way the app could be embedded in Calipseo with a single widget context, instead of a dashboard context including many widget.The granularity of a widget may vary. A Widget could be actually built on top of a module that has more or less features / UIs and is more and less complex. Whatever module initially mapped to a dashboard 'page' could be considered as widget, but a widget could be managed in the source code and loaded ONLY in a embedded mode, and not necessarily used in the dashboard. In other words, similarly as the shiny-calipseo app allows to display different country dashboard contexts, it may allow to display different module contexts.
For example, we could think of a single widget that displays countings of vessels licenses status. It would be set as module, not necessarily available in the dashboard, but loadable by targeting it through shiny app URL; to embedd it in the Calipseo webapp.
cc [~alexandre.bennici@fao.org] related to CALR-19