As an Open Data Hub Manager I want to add the provider and licence fields to the mobility API, to know were the data comes from and who is responsible for it.

[sseppi]

The actual mobility API schema has the origin field were in some cases is stored the Data Provider (e.g. Municipality Bolzano, Municipality Trento, etc.) that is responsible for the data and in other cases is stored the Technical Source (e.g. Algorab, Famas).

The proposal is to add a new field to the mobility API. If we do so we will have the following fields for the Source and the Provider of the data:

• origin: this field will store the technical source of the data (e.g. Algorab, Famas, Systems, etc.)
• provider: this field will store the data provider (e.g. Municipality of Merano, Municipality of Trento, etc.) which is the data owner that signs the data sharing contract and is responsible for it.

N.B. We need to update all data collectors to write correctly this information into the database

[clezag]

I've created an Excel sheet where we can define the origin and provider for all data collectors and elaborations.
I've used the ci/cd script names to create the list, as some data collectors have multiple deployment configurations (e.g. spreadsheets).
I will update the sheet with current origins.

On the implementation side, we'll need to

• add "provider" field to station table
• add "provider" field to writer API
• upgrade all data collectors and elaborations to use the new API + set new origin and provider
• update old stations in DB that are not synced by data collectors anymore
• add "provider" field to ninja API
• add "provider" to analytics
• update documentation of writer, ninja, readthedocs

If I forgot something, feel free to add it to the list

[rcavaliere]

PoC implemented, @sseppi and @mrabans are checking if Data Spaces require additional requirements

[sseppi]

We agreed to add 3 new fields at an measurement and station level.
The 3 new fields are:

• owner: the name of the data provider who sign the contract;
• source: the name of the source who provides the data;
• license: the license of the data

In future the origin will be deprecated and future Data Collector won't fill it anymore, since those fields will substitute it.

While defining the owner and source name we have to worry about the names that should be unique, to allow in future to extend the information (e.g. contact, address, etc.) in a dedicated dataset (probably in the content API) and link it.

@rcavaliere @clezag @mrabans : if I forgot something important please add a comment.