As a Sustainability apps user I would like to have a first MVP of the web-component implemented

[rcavaliere]

• [x] integration of Suedtirol Radelt data
• [ ] review of reference design (for just this MVP - see detailed proposals below)
• [ ] application of MVP design
• [ ] integration in the Open Data Hub Web Components Store (with configurator of the design aspects)

Requirement: the filter "Sustainability Action" and "Organisation" should be considered even in the web-component and in the configuration of the web-component store.

Expected behavior:

• if in the web component configuration just a sustainability action is chosen -> the web-component does not present the sustainability action filter
• if in the web component configuration just an organisation is chosen -> the web-component does not present the organisation filter
• if in the web component configuration a sustainability action and an organisation is chosen -> the web-component does not present any filter
• if in the web component configuration no filters are applied -> the web-component present both filters

Review of reference design: 240523_ConceptAPPReview_NOI.pdf

[rcavaliere]

Just a clarification: in the field "Organisationen" we expect to see the nr of organizations, by enlarging the details we just see here the nr. of organizations divided per type.

[rcavaliere]

Another comment: for the field "Teilnehmerranking" should not contain e.g. "Autonome Provinz Bozen". I would suggest here:

• no "Details ausblenden"
• possibility to change ref. criteria for the ranking (e.g. KM, CO2)
• search button
• ranking

Please also include the possibility to scroll down the ranking.

Also the search must be defined. What happens if no result is obtained? What happens if a research returns multiple results? What happens if a user then selects an organization? In this last scenario: ranking centered to the position of this organization, which is properly highlighted (e.g. other background color) in the ranking

[rcavaliere]

@Peter080202 I add also here the reference to the API calls:

• CompanyGamificationAction: challgenge data, specific per organization https://mobility.api.opendatahub.testingmachine.eu/v2/flat,node/CompanyGamificationAction/*/latest?where=sactive.eq.true&limit=-1
• GamificationAction: total challenge data - https://mobility.api.opendatahub.testingmachine.eu/v2/flat,node/GamificationAction/*/latest?where=sactive.eq.true&limit=-1

These end-points retrieve only the last value. For getting the history, there is another API call (check https://swagger.opendatahub.com/?url=https://mobility.api.opendatahub.com/v2/apispec)

[rcavaliere]

Short summary of what we have agreed today with @Peter080202, relevant also for @danielecanu:

First implementation iteration (next week - to be discussed during the meeting scheduled on 6.9):

• first integration of Open Data Hub API
• visualization of "basic" KPI (e.g. number of km traveled, CO2 emissions reduced, nr. of participants, nr. of organizations, ranking of the organizations)
• implementation of all filters stuff -> first adaptation of original design proposal

Second implementation iteration:

• additional details / plots. Based on the available data, we could have as detail for the KPIs "number of km traveled", "CO2 emissions reduced" the temporal evolution (not a yearly basis based on the data available, but e.g. on a monthly basis)
• additional integration of Open Data Hub -> another API call must be used in order to retrieve the time series of the KPI evolution during time