EPIC: As an Open data hub Manager I want that the Weather Data, Air Quality Data, eCharging Dataset and Vehicular Time data is browsable through the Data Browser 2.0 to test the integration of the Mobility Domain

[sseppi]

This issue wants to integrate the data of the Mobiltiy Domain in the existing Data Browser structure.

The user flow should be the following:

1. Also Mobility Data Sets are integrated in the Datasets list.
2. The user clicks on the "Access to table view" button
3. The table view renders the list of all "Stations" included in the dataset showing for each station the relative metadata;
4. The user clicks on "Detail";
5. The Deatil View showse all metadata and the last measurements of the selected station.

Note: for all mobility datasets the value smetadata shoudl be rendered as a JSON since the content it could be different from Data Provider to Data Provider.

Here below I post some useful link to start with for the first PoC:

• [ ] The Link to the Weather Data (see issue #441 ): Station description/metadata: https://mobility.api.opendatahub.com/v2/flat/MeteoStation Station last values: https://mobility.api.opendatahub.com/v2/flat/MeteoStation/*/latest
• [ ] The Link to the Qir Quality Data (see issue #442 ): Station description/metadata: https://mobility.api.opendatahub.com/v2/flat/EnvironmentStation Station last values: https://mobility.api.opendatahub.com/v2/flat/EnvironmentStation/*/latest
• [ ] The link to the eCharging APIs (concept of parent child station) (see issue #443): https://mobility.api.opendatahub.com/v2/flat/EChargingPlug https://mobility.api.opendatahub.com/v2/flat/EChargingStation
• [ ] The link to the Vehicular Time data (concept of parent child with beginn and end station) (see issue #444) Station description/metadata: https://mobility.api.opendatahub.com/v2/flat/LinkStation Station last values: https://mobility.api.opendatahub.com/v2/flat/LinkStation/*/latest

In the first iteration maybe we should disable the search and filter options for all mobility datasets (@gappc do you think is better to create a separate issue for the management of filters and search in mobility domain). For the filter and search functionality, a dedicated issue has been created #427

[pkritzinger]

@sseppi @gappc please find the first draft of the configuration for the datasets above here:

https://studiohug.sharepoint.com/:x:/s/server/EdTwMFyTM0dDv4c_Iabv84wBH60obite1-7Hb-x5Pp22Ug?e=MWfYb3

Open task: define "understandable" labels for all attributes. Would work on that after the structure of the different views has been approved.

Questions are highlighted in red, comments in yellow.

[sseppi]

@pkritzinger I got the feedback from Roberto, he said that the proposed configuration is fine and easily extensible also to the other datasets.

I would suggest to proceed with the proposal you did.

[pkritzinger]

hi @sseppi Sounds great - happy to hear that. How will we proceed?

@gappc can you already start with setting up the first proof of concept or do you need sth. else from our side?

[pkritzinger]

@sseppi great, happy to hear that. Is there any open to do from our side or can you, @gappc , start?

How shall we proceed with our comment (see below) in the excel regarding data visualization?

• It would be great to show a small chart of the values of the last 7 days

[sseppi]

@sseppi great, happy to hear that. Is there any open to do from our side or can you, @gappc , start?

@gappc I would suggest to reuse as much as possible already existing components.

How shall we proceed with our comment (see below) in the excel regarding data visualization?

• It would be great to show a small chart of the values of the last 7 days

In my point of view, it could be useful as preview of what could be displayed in the Open Data Hub Analytics tool. But for now this feature is a nice to have.

@mrabans and @rcavaliere do you agree?

In case I can create a dedicated issue to proceed with the 7 days preview

[rcavaliere]

@sseppi I agree!

[gappc]

@pkritzinger @sseppi @rcavaliere I think the configuration proposed by studiohug is fine. The use-case of showing data of the last X days seems interesting, too. As @sseppi suggested I would open a dedicated issue for that functionality.

[sseppi]

@pkritzinger and @gappc as emerged duuring the discussion I suggest to proceed with the configuration of the single fields for the first PoC.

I've also create a dedicated issue for the 7 days preview: #456