Welcome to the AI Watch T6 Explorer!

The AI Watch T6 Explorer (AIWatch-T6-X) is an exercise to provide an integrated view of public services using AI, and to derive statistical data from them.

Service records are collected from voluntarily contributed data sources (e.g., surveys, catalogues, datasets), which are harmonised into a common data schema - nothing complicated, just a flat list of attributes, as the name and description of the service, the geographic area covered, its social and policy uptake (if any).

If you are interested in contributing, please follow the instructions outlined in the following section.

How to contribute

Contributions must be submitted via pull requests (PR) to this repository. The data must be submitted as a CSV (Comma-Separated Values) files, whose columns must have specific names and values.

The submission steps are the following ones:

Creating an issue describing your contribution

As a first step, you are recommended to open an issue providing a description of the data source and the services you would like to contribute. This would help understand whether your contribution is in scope with this work, and to verify which information has been collected for the services to be contributed.

Preparing the files to be submitted

The submission consists of 2 CSV files:

• one describing the data source
• one describing the service records

The columns and values of these files must correspond to the ones defined in the data schema. Please note that all columns not matching the defined names will be ignored.

The example folder in this repository includes two empy CSV files with the standard column names. You can copy-paste the data there, and modify the column values (if needed) to match the allowed values.

Creating a pull request

One the two CSV files are ready, you can create a pull request to the src folder.

The title and/or description of the pull request must include a reference to the issue you have previously created.

The two files to be submitted should ideally encoded in UTF-8, and they must have a file name following the pattern:

• [N]-catalog-[name].csv
• [N]-services-[name].csv

where "N" is an integer, and "name" is the abbreviation of your data source.

Note that "N" and "name" should correspond to the same values in both files - e.g.:

• 1-catalog-jrc.csv
• 1-services-jrc.csv

The value of "N" must be incremental to the ones used in the already contributed data sources in folder src.

Data schema

Data source

Code	Values	Description
c_name	free text	The name/title of the data source
c_description	free text	A brief description of the data source
c_contact	email or URL	A contact email / URL for the data source
c_url	URL	The URL of the page of the data source
c_publisher	free text	The name of the organization who published / released the data source
c_type	Desk research, Online survey, Catalogue	The way service records have been collected

Service

Code	Values	Description
id	integer	The identifier for the service in the data source, expressed an an integer (starting from 1). In case of multiple submission of the same data source (in case there was an error, or because it has been updated), the identifier MUST NOT CHANGE across the different versions of the data source
name	free text	Name of the service/activity
type	One of the values from the IPS service types taxonomy	The type of service/activity
url	URL	The URL of the page of the service (if any). Preferably, this should be a persistent URL.
contact	email or URL	A contact email / URL for the service
description	free text	A brief description of the service
geoextent	One of the values from the IPS geo extent taxonomy	The spatial scale at which the service is implemented. Subnational is used as generic category for services for which the sub-national scale is not known (i.e. regional, or city, or neighborhood). All regional, city and neighborhood services are also sub-national services.
geocoverage	Comma-separated list of ISO 3166 country names	The areas covered by the service, specified as a comma-separated list of country names. Country names MUST correspond to those defined in ISO 3166
lead_organization_name	free text	Name of the lead organisation. Local name, in native language.
lead_organization_category	One of the values from the IPS organisation categories taxonomy	The category of the lead organisation.
start_date	Date in the ISO 8601 format YYYY-MM-DD (e.g., 2019-03-04)	The start date of the service
active	Yes|No	Whether the service was or not still active at the moment when it was added to the data source
end_date	Date in the ISO 8601 format YYYY-MM-DD (e.g., 2019-03-04)	The end date of the service
primary_sector	One of the values from the COFOG taxonomy	The primary sector for this service.
secondary_sector	One of the values from the COFOG taxonomy	The secondary sector tackled by the service.
cross_sector	Yes|No	Whether the service is used or can be used across sectors, or in cross-sector scenarios.
cross_border	Yes|No	Whether the service is used or can be used across borders, or in cross-border scenarios.
technology	One of the values from the IPS technologies taxonomy	The primary technology used in the service.
status	One of the values from the IPS status taxonomy	The maturity level of the service.
uptake	One of the values from the IPS uptake taxonomy	The level of uptake of the service. It basically corresponds to the percentage of stakeholders using the service.