TC5.7 - Dashboard for Data Comparison: Multiple Selector, and cross communication among widgets

Test Case Title

TC5.7 - Dashboard for Data Comparison: Multiple Selector, and cross communication among widgets

Goal

I can:

Compare trends of different kind of data/sensors (traffic flow, environment, pollution, IOT, referral data, etc. etc.) on the basis of time, enabling visual exploration for new relationships

Cross communications among Widgets in the same Dashboard (Cross Widget Paradigm) to keep them aligned and showing synchronized data.

Prerequisites

A PC with a browser. Access to the dashboard

The following functionalities are available only for specific Snap4city users with specific privileges.

Expected successful result

Access to the dashboards accessible by the links and see them, see data updated with the interval declared by each widget and the time elapsed. If you push F11 you can go and exit from full screen. Showing how dashboard can be used to communicate and for getting feedback from the city users and stakeholders.

Steps

 

 

Example 1: perform time trend compare from different real-time data sources

  • Open the following link to see a dashboard to test click:
  • https://dashboard.km4city.org/view/index.php?iddasboard=MjQ3  
  • Select one source to compare from the selector from the left
  • For example the parking
    • Select a parking, for example that from the station, main
    • Select one source of comparison from the selector from the right
  • See the selections performed from the figure

  • Select the time trend you would like to compare: 4 hours, 1 day (addition time windows can be added)
  • Different or identical time trends can be selected from both views
  • Compare the time trends as in the figure. 

 


Example 2: Cross communication among Widgets in the same Dashboard (Cross Widget Paradigm), for example:

  • at the push of a widget button to activate a different action in other Widgets of the same dashboard;
  • at the click on some list of events, to activate the rendering on map of the event plus related data;
  • at the click of a button to activate multiple cross widget events. For example, to change the content of one or more widgets, to send an API REST Call, to send commands to other widgets (change TV camera, change parking under monitoring, to change the monitored sensor, etc…)
  • At the click of a button/widget to open an URL on a IFRAME widget

You can start testing this requirement by following the sequence of actions:

If you pass the mouse over the buttons (without clicking), you can see that headers of some widgets change their colour with the colour of the button, indicating that if you click the button that widgets is involved in the interaction.

Click on the buttons you prefer, to see the widgets updated accordingly.