Cervelli In Fuga

About the project

The project stems from the necessity of visualizing the data related to young individuals choosing to leave the country of Italy. The aim is to identify possible correlations between the emigration rate and other factors such as the employment rate after graduation, the average of housing prices over the years and the satisfaction with one's working conditions.
Inspiration was taken by a report published on the European Data Journalism Network by Giuseppe Chiellino (Il Sole 24 Ore) having title "Italy is stuck in a European brain drain". The report highlights the lack of third-level education, especially in the South of Italy, as well as the high emigration rate in the whole country. "Cervelli in Fuga"'s aim is to make an hypothesis on the hidden reasons behind the decision to leave that a lot of Italians make.

Research questions

?

Is there a correlation between brain drain and the rate of young people still living with their parents or their working condition and satisfaction?
Is there a difference when talking about graduates?

The project in numbers

50697

Young people emigrated.

17%

Graduates that are very satisfied at work.

67,6%

Young people still living at home with their parents.

103

House prices (indice 2015=100).

14.75€

Graduates' average hourly wage.

Data: Istat, 2021

Datasets

Name Source/URL Format file
D1. Young people (18-39) of Italian citizenship emigrated to foreign countries from 2014 to 2022 Istat CSV D1.csv
D2. Young people (18-34) still living with at least one of their parents (2014-2022) Istat CSV D2.csv
D3. House prices (2014-2022) Istat CSV D3.csv
D4. Work satisfaction (2014-2022) Istat CSV D4.csv
D5. Hourly wage based on type of contract (2014-2021) Istat CSV D5.csv
D6. Hourly wage by age bracket (2014-2021) Istat CSV D6.csv
D7. Hourly wage by educational qualification (2014-2021) Istat CSV D7.csv
D8. Employment rate after graduation (2022) AlmaLaurea CSV D8.csv
D9. Employment rate after graduation (2021) AlmaLaurea CSV D9.csv
D10. Employment rate after graduation (2020) AlmaLaurea CSV D10.csv
D11. Employment rate after graduation (2019) AlmaLaurea CSV D11.csv
D12. Employment rate after graduation (2018) AlmaLaurea CSV D12.csv
D13. Employment rate after graduation (2017) AlmaLaurea CSV D13.csv
D14. Employment rate after graduation (2016) AlmaLaurea CSV D14.csv
D15. Employment rate after graduation (2015) AlmaLaurea CSV D15.csv
D16. Employment rate after graduation (2014) AlmaLaurea CSV D16.csv

Name Source Datasets File
D.17 Employment rate after graduation (2014-2022) D.8, D.9, D.10, D.11, D.12, D.13, D.14, D.15, D.16 D17.csv
I1. Economic independence. D.2, D.3 I1.csv

Name Source Datasets File
I2. Working status by age. D.4, D.6 I2.csv
I3. Work wages across sectors. D.5, D.6, D.7 I3.csv
I4. Graduates' employment status. D.4, D.7, D.17 I4.csv
I5. Emigration and economic independence. D.1, I1 I5.csv

Analyses

Accuracy Coherence Completeness Timeliness
D1 done done done Regular updates (annual)
D2 done done done Regular updates (annual)
D3 done done done Regular updates (quarterly)
D4 done done done Regular updates (annual)
D5 No syntactic accuracy in some headings of (NOTE_CONTARCTUAL_OCCUPATION; NOTE_EMPLOYESS CLASS). Data in the columns are not compromised. done No data available for 2022 Annual updates - not respected
D6 No syntactic accuracy in some headings of (NOTE_CONTARCTUAL_OCCUPATION; NOTE_EMPLOYESS CLASS) Data in the columns are not compromised. done No data available for 2022 Annual updates- not respected
D7 No syntactic accuracy in some headings of (NOTE_CONTARCTUAL_OCCUPATION; NOTE_EMPLOYESS CLASS). Data in the columns are not compromised. Incoherent data - it's present a column called "missing data" and refers to no educational qualification specified. No data available for 2022 Annual updates - not respected
D8 done done done Supposedly annual updates
D9 done done Missing data about column "Scienze della Formazione primaria (corso pre-riforma D.M. n. 249/2010)". Supposedly annual updates
D10 done done done Supposedly annual updates
D11 done done done Supposedly annual updates
D12 done done done Supposedly annual updates
D13 done done done Supposedly annual updates
D14 done done done Supposedly annual updates
D15 done done done Supposedly annual updates
D16 done done done Supposedly annual updates

Origin Format Metadata License
Istat CSV, JSON, Excel, SDMX-CSV Level 4: available SDMX (XML) in which there can be found metadata about each single datum.
Level 2: further metadata are available accessing the portal SIqual.
CC-BY-3.0
AlmaLaurea CSV Level 1: no metadata available. "Unless otherwise indicated, reproduction for non-commercial purposes with citation of the source is authorized"

Young people (18-39) of Italian citizenship emigrated to foreign countries from 2014 to 2022
Issues Questions Dataset
Privacy Is the dataset free of any personal data as defined in the Regulation (EU) 2016/679? yes
Is the dataset free of any indirect personal data that could be used for identifying the natural person? If so, is there a law that authorize the PA to release them? Or any other legal basis? Identify the legal basis. yes
Is the dataset free of any particular personal data (art. 9 GDPR)? If so is there a law that authorize the PA to release them? yes
Is the dataset free of any information that combined with common data available in the web, could identify the person? If so, is there a law that authorize the PA to release them? yes
Is the dataset free of any information related to human rights (e.g. refugees, witness protection, etc.)? yes
Do you use a tool for calculating the range of the risk of de-anonymization? Do you anonymize the dataset? With which technique? Did you check the three mandatory parameters: singling out, linking out, inference out? no, the dataset is already anonymized
Are you using geolocalization capabilities ? Do you check that the geolocalization process can’t identify single individuals in some circumstances? yes, but we the selected data is related to macro-areas and therefore the individuals cannot be identified
Did you check that the open data platform respect all the privacy regulations (registration of the end-user, profiling, cookies, analytics, etc.)? yes
Do you know who are in your open data platform the Controller and Processor of the privacy data of the system? the Controller is the National Institute of Statistics, and the Processor is Istat
Where the datasets are physically stored (country and jurisdiction)? Do you have a cloud computing platform? Do you have checked the privacy regulation of the country where the dataset are physically stored? (territoriality) data stored in Italy; there are no details provided on cloud computing platform by Istat; data is subjected to privacy regulation in Italy
Do you have non-personal data? Are you sure that are not “mixed data”? yes, the data is anonymized and therefore non-personal
IPR of the dataset Do you have created and generated the dataset ? no
Are you the owner of the dataset? How is the owner? no, the owner is Istat
Are you sure to not use third party data without the proper authorization and license ? Are the dataset free from third party licenses or patents? yes
Have you checked if there are some limitations in your national legal system for releasing some kind of datasets with open license? yes
Licences Do you release the dataset with an open data license ? In case of the use of CC0 do you check that you have all the right necessary for this particular kind of license (e.g., jurisdiction)? yes
Do you include the clause: "In any case the dataset can’t be used for re-identifying the person" ? no, it is not present in Istat
Do you release the API (in case you have) with an open source license ? no, because we have not released the API
Do you check that the open data/API platform license regime is compliant with your IPR policy ? Do you have all the licences related to the open data platform/API software? yes
Limitations on public access Do you check that the dataset concerns your institutional competences, scope and finality? Do you check if the dataset concerns other public administration competences? yes
Do you check the limitations for the publication stated by your national legislation or by the EU directives ? yes
Do you check if there are some limitations connected to the international relations, public security or national defence? yes
Do you check if there are some limitations concerning the public interest ? yes
Do you check the international law limitations ? yes
Do you check the INSPIRE law limitations for the spatial data? yes
Economical Conditions Do you check that the dataset could be released for free ? yes
Do you check if there are some agreements with some other partners in order to release the dataset with a reasonable price ? Istat allows third parties to adapt their dataset also for commercial purposes
Do you check if the open data platform terms of service include a clause of “non liability agreement” regarding the dataset and API provided ? yes, there is a non liability statement
In case you decide to release the dataset to a reasonable price do you check if the limitation imposed by the new directive 2019/1024/EU are respected ? Are you able to calculate the “marginal cost”? Are you able to justify the “reasonable return on investment” limited to cover the costs of collection, production, reproduction, dissemination, preservation and rights clearance? There is a national law that justify your public administration to apply the “reasonable return of investment”? yes, to calculate the "marginal cost" and justify the "reasonable return on investment," it's essential to consider the costs associated with the various stages of data provision and the specific conditions outlined in the Open Data Directive. This may involve assessing the direct costs of data collection, production, and dissemination, as well as indirect costs such as preservation and rights clearance. The Italian legal framework for the re-use of public sector information (PSI) is governed by several laws and regulations. The main law for cost-free access to PSI is Act no. 241 of 7 August 1990, which provides for general access to government documents, although access in many cases depends on the existence of a legal interest.
In case you decide to release the dataset to a reasonable price do you check the e-Commerce directive and regulation? yes
Temporary aspects Do you have a temporary policy for updating the dataset ? yes, it is present in Istat as stated in the quality analysis
Do you have some mechanism for informing the end-user that the dataset is updated at a given time to avoid mis-usage and so potential risk of damage ? yes
Did you check if the dataset for some reason can’t be indexed by the research engines (e.g. Google, Yahoo, etc.) ? yes, it is indexed correctly
In case of personal data, do you have a reasonable technical mechanism for collecting request of deletion (e.g. right to be forgotten)? the data dealt with is non-personal

Young people (18-34) still living with at least one of their parents (2014-2022)
Issues Questions Dataset
Privacy Is the dataset free of any personal data as defined in the Regulation (EU) 2016/679? yes
Is the dataset free of any indirect personal data that could be used for identifying the natural person? If so, is there a law that authorize the PA to release them? Or any other legal basis? Identify the legal basis. yes
Is the dataset free of any particular personal data (art. 9 GDPR)? If so is there a law that authorize the PA to release them? yes
Is the dataset free of any information that combined with common data available in the web, could identify the person? If so, is there a law that authorize the PA to release them? yes
Is the dataset free of any information related to human rights (e.g. refugees, witness protection, etc.)? yes
Do you use a tool for calculating the range of the risk of de-anonymization? Do you anonymize the dataset? With which technique? Did you check the three mandatory parameters: singling out, linking out, inference out? no, the dataset is already anonymized
Are you using geolocalization capabilities ? Do you check that the geolocalization process can’t identify single individuals in some circumstances? yes, and in small area it would probably be easier to single out the individuals. However, in the mesh-up phase we the selected data is related to macro-areas and therefore the individuals cannot be identified; moreover, we used percentages to display the measuraments, therefore one cannot understand how many individuals in a specific area are taken into consideration
Did you check that the open data platform respect all the privacy regulations (registration of the end-user, profiling, cookies, analytics, etc.)? yes
Do you know who are in your open data platform the Controller and Processor of the privacy data of the system? the Controller is the National Institute of Statistics, and the Processor is Istat
Where the datasets are physically stored (country and jurisdiction)? Do you have a cloud computing platform? Do you have checked the privacy regulation of the country where the dataset are physically stored? (territoriality) data stored in Italy; there are no details provided on cloud computing platform by Istat; data is subjected to privacy regulation in Italy
Do you have non-personal data? Are you sure that are not “mixed data”? yes, the data is anonymized and therefore non-personal
IPR of the dataset Do you have created and generated the dataset ? no
Are you the owner of the dataset? How is the owner? no, the owner is Istat
Are you sure to not use third party data without the proper authorization and license ? Are the dataset free from third party licenses or patents? yes
Do you have checked if there are some limitations in your national legal system for releasing some kind of datasets with open license? yes
Licences Do you release the dataset with an open data license ? In case of the use of CC0 do you check that you have all the right necessary for this particular kind of license (e.g., jurisdiction)? yes
Do you include the clause: "In any case the dataset can’t be used for re-identifying the person" ? no, it is not present in Istat
Do you release the API (in case you have) with an open source license ? no, because we have not released the API
Do you check that the open data/API platform license regime is compliance with your IPR policy ? Do you have all the licences related to the open data platform/API software? yes
Limitations on public access Do you check that the dataset concerns your institutional competences, scope and finality? Do you check if the dataset concerns other public administration competences? yes
Do you check the limitations for the publication stated by your national legislation or by the EU directives ? yes
Do you check if there are some limitations connected to the international relations, public security or national defence? yes
Do you check if there are some limitations concerning the public interest ? yes
Do you check the international law limitations ? yes
Do you check the INSPIRE law limitations for the spatial data? yes
Economical Conditions Do you check that the dataset could be released for free ? yes
Do you check if there are some agreements with some other partners in order to release the dataset with a reasonable price ? Istat allows third parties to adapt their dataset also for commercial purposes
Do you check if the open data platform terms of service include a clause of “non liability agreement” regarding the dataset and API provided ? yes, there is a non liability statement
In case you decide to release the dataset to a reasonable price do you check if the limitation imposed by the new directive 2019/1024/EU are respected ? Are you able to calculate the “marginal cost”? Are you able to justify the “reasonable return on investment” limited to cover the costs of collection, production, reproduction, dissemination, preservation and rights clearance? There is a national law that justify your public administration to apply the “reasonable return of investment”? yes, to calculate the "marginal cost" and justify the "reasonable return on investment," it's essential to consider the costs associated with the various stages of data provision and the specific conditions outlined in the Open Data Directive. This may involve assessing the direct costs of data collection, production, and dissemination, as well as indirect costs such as preservation and rights clearance. The Italian legal framework for the re-use of public sector information (PSI) is governed by several laws and regulations. The main law for cost-free access to PSI is Act no. 241 of 7 August 1990, which provides for general access to government documents, although access in many cases depends on the existence of a legal interest.
In case you decide to release the dataset to a reasonable price do you check the e-Commerce directive and regulation? yes
Temporary aspects Do you have a temporary policy for updating the dataset ? yes, it is present in Istat as stated in the quality analysis
Do you have some mechanism for informing the end-user that the dataset is updated at a given time to avoid mis-usage and so potential risk of damage ? yes
Did you check if the dataset for some reason can’t be indexed by the research engines (e.g. Google, Yahoo, etc.) ? yes, it is indexed correctly
In case of personal data, do you have a reasonable technical mechanism for collecting request of deletion (e.g. right to be forgotten)? the data dealt with is non-personal

House prices (2014-2022)
Issues Questions Dataset
Privacy Is the dataset free of any personal data as defined in the Regulation (EU) 2016/679? yes
Is the dataset free of any indirect personal data that could be used for identifying the natural person? If so, is there a law that authorize the PA to release them? Or any other legal basis? Identify the legal basis. yes
Is the dataset free of any particular personal data (art. 9 GDPR)? If so is there a law that authorize the PA to release them? yes
Is the dataset free of any information that combined with common data available in the web, could identify the person? If so, is there a law that authorize the PA to release them? yes
Is the dataset free of any information related to human rights (e.g. refugees, witness protection, etc.)? yes
Do you use a tool for calculating the range of the risk of de-anonymization? Do you anonymize the dataset? With which technique? Did you check the three mandatory parameters: singling out, linking out, inference out? no, the dataset is already anonymized
Are you using geolocalization capabilities ? Do you check that the geolocalization process can’t identify single individuals in some circumstances? yes, but since the data is not related to individuals or groups of people there is no risk of identifying them
Did you check that the open data platform respect all the privacy regulations (registration of the end-user, profiling, cookies, analytics, etc.)? yes
Do you know who are in your open data platform the Controller and Processor of the privacy data of the system? the Controller is the National Institute of Statistics, and the Processor is Istat
Where the datasets are physically stored (country and jurisdiction)? Do you have a cloud computing platform? Do you have checked the privacy regulation of the country where the dataset are physically stored? (territoriality) data stored in Italy; there are no details provided on cloud computing platform by Istat; data is subjected to privacy regulation in Italy
Do you have non-personal data? Are you sure that are not “mixed data”? yes, the data is related to averages of house prices and therefore non-personal
IPR of the dataset Do you have created and generated the dataset ? no
Are you the owner of the dataset? How is the owner? no, the owner is Istat
Are you sure to not use third party data without the proper authorization and license ? Are the dataset free from third party licenses or patents? yes
Do you have checked if there are some limitations in your national legal system for releasing some kind of datasets with open license? yes
Licences Do you release the dataset with an open data license ? In case of the use of CC0 do you check that you have all the right necessary for this particular kind of license (e.g., jurisdiction)? yes
Do you include the clause: "In any case the dataset can’t be used for re-identifying the person" ? no, it is not present in Istat
Do you release the API (in case you have) with an open source license ? no, because we have not released the API
Do you check that the open data/API platform license regime is compliance with your IPR policy ? Do you have all the licences related to the open data platform/API software? yes
Limitations on public access Do you check that the dataset concerns your institutional competences, scope and finality? Do you check if the dataset concerns other public administration competences? yes
Do you check the limitations for the publication stated by your national legislation or by the EU directives ? yes
Do you check if there are some limitations connected to the international relations, public security or national defence? yes
Do you check if there are some limitations concerning the public interest ? yes
Do you check the international law limitations ? yes
Do you check the INSPIRE law limitations for the spatial data? yes
Economical Conditions Do you check that the dataset could be released for free ? yes
Do you check if there are some agreements with some other partners in order to release the dataset with a reasonable price ? Istat allows third parties to adapt their dataset also for commercial purposes
Do you check if the open data platform terms of service include a clause of “non liability agreement” regarding the dataset and API provided ? yes, there is a non liability statement
In case you decide to release the dataset to a reasonable price do you check if the limitation imposed by the new directive 2019/1024/EU are respected ? Are you able to calculate the “marginal cost”? Are you able to justify the “reasonable return on investment” limited to cover the costs of collection, production, reproduction, dissemination, preservation and rights clearance? There is a national law that justify your public administration to apply the “reasonable return of investment”? yes, to calculate the "marginal cost" and justify the "reasonable return on investment," it's essential to consider the costs associated with the various stages of data provision and the specific conditions outlined in the Open Data Directive. This may involve assessing the direct costs of data collection, production, and dissemination, as well as indirect costs such as preservation and rights clearance. The Italian legal framework for the re-use of public sector information (PSI) is governed by several laws and regulations. The main law for cost-free access to PSI is Act no. 241 of 7 August 1990, which provides for general access to government documents, although access in many cases depends on the existence of a legal interest.
In case you decide to release the dataset to a reasonable price do you check the e-Commerce directive and regulation? yes
Temporary aspects Do you have a temporary policy for updating the dataset ? yes, it is present in Istat as stated in the quality analysis
Do you have some mechanism for informing the end-user that the dataset is updated at a given time to avoid mis-usage and so potential risk of damage ? yes
Did you check if the dataset for some reason can’t be indexed by the research engines (e.g. Google, Yahoo, etc.) ? yes, it is indexed correctly
In case of personal data, do you have a reasonable technical mechanism for collecting request of deletion (e.g. right to be forgotten)? the data dealt with is non-personal

Work satisfaction (2014-2022)
Issues Questions Dataset
Privacy Is the dataset free of any personal data as defined in the Regulation (EU) 2016/679? yes
Is the dataset free of any indirect personal data that could be used for identifying the natural person? If so, is there a law that authorize the PA to release them? Or any other legal basis? Identify the legal basis. yes
Is the dataset free of any particular personal data (art. 9 GDPR)? If so is there a law that authorize the PA to release them? yes
Is the dataset free of any information that combined with common data available in the web, could identify the person? If so, is there a law that authorize the PA to release them? yes
Is the dataset free of any information related to human rights (e.g. refugees, witness protection, etc.)? yes
Do you use a tool for calculating the range of the risk of de-anonymization? Do you anonymize the dataset? With which technique? Did you check the three mandatory parameters: singling out, linking out, inference out? no, the dataset is already anonymized
Are you using geolocalization capabilities ? Do you check that the geolocalization process can’t identify single individuals in some circumstances? no
Did you check that the open data platform respect all the privacy regulations (registration of the end-user, profiling, cookies, analytics, etc.)? yes
Do you know who are in your open data platform the Controller and Processor of the privacy data of the system? the Controller is the National Institute of Statistics, and the Processor is Istat
Where the datasets are physically stored (country and jurisdiction)? Do you have a cloud computing platform? Do you have checked the privacy regulation of the country where the dataset are physically stored? (territoriality) data stored in Italy; there are no details provided on cloud computing platform by Istat; data is subjected to privacy regulation in Italy
Do you have non-personal data? Are you sure that are not “mixed data”? yes, the data is anonymous and therefore non-personal
IPR of the dataset Do you have created and generated the dataset ? no
Are you the owner of the dataset? How is the owner? no, the owner is Istat
Are you sure to not use third party data without the proper authorization and license ? Are the dataset free from third party licenses or patents? yes
Did you check if there are some limitations in your national legal system for releasing some kind of datasets with open license? yes
Licences Do you release the dataset with an open data license ? In case of the use of CC0 do you check that you have all the right necessary for this particular kind of license (e.g., jurisdiction)? yes
Do you include the clause: "In any case the dataset can’t be used for re-identifying the person" ? no, it is not present in Istat
Do you release the API (in case you have) with an open source license ? no, because we have not released the API
Do you check that the open data/API platform license regime is compliance with your IPR policy ? Do you have all the licences related to the open data platform/API software? yes
Limitations on public access Do you check that the dataset concerns your institutional competences, scope and finality? Do you check if the dataset concerns other public administration competences? yes
Do you check the limitations for the publication stated by your national legislation or by the EU directives ? yes
Do you check if there are some limitations connected to the international relations, public security or national defence? yes
Do you check if there are some limitations concerning the public interest ? yes
Do you check the international law limitations ? yes
Do you check the INSPIRE law limitations for the spatial data? yes
Economical Conditions Do you check that the dataset could be released for free ? yes
Do you check if there are some agreements with some other partners in order to release the dataset with a reasonable price ? Istat allows third parties to adapt their dataset also for commercial purposes
Do you check if the open data platform terms of service include a clause of “non liability agreement” regarding the dataset and API provided ? yes, there is a non liability statement
In case you decide to release the dataset to a reasonable price do you check if the limitation imposed by the new directive 2019/1024/EU are respected ? Are you able to calculate the “marginal cost”? Are you able to justify the “reasonable return on investment” limited to cover the costs of collection, production, reproduction, dissemination, preservation and rights clearance? There is a national law that justify your public administration to apply the “reasonable return of investment”? yes, to calculate the "marginal cost" and justify the "reasonable return on investment," it's essential to consider the costs associated with the various stages of data provision and the specific conditions outlined in the Open Data Directive. This may involve assessing the direct costs of data collection, production, and dissemination, as well as indirect costs such as preservation and rights clearance. The Italian legal framework for the re-use of public sector information (PSI) is governed by several laws and regulations. The main law for cost-free access to PSI is Act no. 241 of 7 August 1990, which provides for general access to government documents, although access in many cases depends on the existence of a legal interest.
In case you decide to release the dataset to a reasonable price do you check the e-Commerce directive and regulation? yes
Temporary aspects Do you have a temporary policy for updating the dataset ? yes, it is present in Istat as stated in the quality analysis
Do you have some mechanism for informing the end-user that the dataset is updated at a given time to avoid mis-usage and so potential risk of damage ? yes
Did you check if the dataset for some reason can’t be indexed by the research engines (e.g. Google, Yahoo, etc.) ? yes, it is indexed correctly
In case of personal data, do you have a reasonable technical mechanism for collecting request of deletion (e.g. right to be forgotten)? the data dealt with is non-personal

Hourly wage based on type of contract (2014-2021)
Issues Questions Dataset
Privacy Is the dataset free of any personal data as defined in the Regulation (EU) 2016/679? yes
Is the dataset free of any indirect personal data that could be used for identifying the natural person? If so, is there a law that authorize the PA to release them? Or any other legal basis? Identify the legal basis. yes
Is the dataset free of any particular personal data (art. 9 GDPR)? If so is there a law that authorize the PA to release them? yes
Is the dataset free of any information that combined with common data available in the web, could identify the person? If so, is there a law that authorize the PA to release them? yes
Is the dataset free of any information related to human rights (e.g. refugees, witness protection, etc.)? yes
Do you use a tool for calculating the range of the risk of de-anonymization? Do you anonymize the dataset? With which technique? Did you check the three mandatory parameters: singling out, linking out, inference out? no, the dataset is already anonymized
Are you using geolocalization capabilities ? Do you check that the geolocalization process can’t identify single individuals in some circumstances? yes, but the wage is the median of all wages in the area therefore no personal data is directly implied in the dataset
Did you check that the open data platform respect all the privacy regulations (registration of the end-user, profiling, cookies, analytics, etc.)? yes
Do you know who are in your open data platform the Controller and Processor of the privacy data of the system? the Controller is the National Institute of Statistics, and the Processor is Istat
Where the datasets are physically stored (country and jurisdiction)? Do you have a cloud computing platform? Do you have checked the privacy regulation of the country where the dataset are physically stored? (territoriality) data stored in Italy; there are no details provided on cloud computing platform by Istat; data is subjected to privacy regulation in Italy
Do you have non-personal data? Are you sure that are not “mixed data”? yes, the data is anonymized and therefore non-personal
IPR of the dataset Do you have created and generated the dataset ? no
Are you the owner of the dataset? How is the owner? no, the owner is Istat
Are you sure to not use third party data without the proper authorization and license ? Are the dataset free from third party licenses or patents? yes
Do you have checked if there are some limitations in your national legal system for releasing some kind of datasets with open license? yes
Licences Do you release the dataset with an open data license ? In case of the use of CC0 do you check that you have all the right necessary for this particular kind of license (e.g., jurisdiction)? yes
Do you include the clause: "In any case the dataset can’t be used for re-identifying the person" ? no, it is not present in Istat
Do you release the API (in case you have) with an open source license ? no, because we have not released the API
Do you check that the open data/API platform license regime is compliance with your IPR policy ? Do you have all the licences related to the open data platform/API software? yes
Limitations on public access Do you check that the dataset concerns your institutional competences, scope and finality? Do you check if the dataset concerns other public administration competences? yes
Do you check the limitations for the publication stated by your national legislation or by the EU directives ? yes
Do you check if there are some limitations connected to the international relations, public security or national defence? yes
Do you check if there are some limitations concerning the public interest ? yes
Do you check the international law limitations ? yes
Do you check the INSPIRE law limitations for the spatial data? yes
Economical Conditions Do you check that the dataset could be released for free ? yes
Do you check if there are some agreements with some other partners in order to release the dataset with a reasonable price ? Istat allows third parties to adapt their dataset also for commercial purposes
Do you check if the open data platform terms of service include a clause of “non liability agreement” regarding the dataset and API provided ? yes, there is a non liability statement
In case you decide to release the dataset to a reasonable price do you check if the limitation imposed by the new directive 2019/1024/EU are respected ? Are you able to calculate the “marginal cost”? Are you able to justify the “reasonable return on investment” limited to cover the costs of collection, production, reproduction, dissemination, preservation and rights clearance? There is a national law that justify your public administration to apply the “reasonable return of investment”? yes, to calculate the "marginal cost" and justify the "reasonable return on investment," it's essential to consider the costs associated with the various stages of data provision and the specific conditions outlined in the Open Data Directive. This may involve assessing the direct costs of data collection, production, and dissemination, as well as indirect costs such as preservation and rights clearance. The Italian legal framework for the re-use of public sector information (PSI) is governed by several laws and regulations. The main law for cost-free access to PSI is Act no. 241 of 7 August 1990, which provides for general access to government documents, although access in many cases depends on the existence of a legal interest.
In case you decide to release the dataset to a reasonable price do you check the e-Commerce directive and regulation? yes
Temporary aspects Do you have a temporary policy for updating the dataset ? yes, it is present in Istat as stated in the quality analysis
Do you have some mechanism for informing the end-user that the dataset is updated at a given time to avoid mis-usage and so potential risk of damage ? yes
Did you check if the dataset for some reason can’t be indexed by the research engines (e.g. Google, Yahoo, etc.) ? yes, it is indexed correctly
In case of personal data, do you have a reasonable technical mechanism for collecting request of deletion (e.g. right to be forgotten)? the data dealt with is non-personal

Hourly wage by age bracket (2014-2021)
Issues Questions Dataset
Privacy Is the dataset free of any personal data as defined in the Regulation (EU) 2016/679? yes
Is the dataset free of any indirect personal data that could be used for identifying the natural person? If so, is there a law that authorize the PA to release them? Or any other legal basis? Identify the legal basis. yes
Is the dataset free of any particular personal data (art. 9 GDPR)? If so is there a law that authorize the PA to release them? yes
Is the dataset free of any information that combined with common data available in the web, could identify the person? If so, is there a law that authorize the PA to release them? yes
Is the dataset free of any information related to human rights (e.g. refugees, witness protection, etc.)? yes
Do you use a tool for calculating the range of the risk of de-anonymization? Do you anonymize the dataset? With which technique? Did you check the three mandatory parameters: singling out, linking out, inference out? no, the dataset is already anonymized
Are you using geolocalization capabilities ? Do you check that the geolocalization process can’t identify single individuals in some circumstances? yes, but the wage is the median of all wages in the area therefore no personal data is directly implied in the dataset
Did you check that the open data platform respect all the privacy regulations (registration of the end-user, profiling, cookies, analytics, etc.)? yes
Do you know who are in your open data platform the Controller and Processor of the privacy data of the system? the Controller is the National Institute of Statistics, and the Processor is Istat
Where the datasets are physically stored (country and jurisdiction)? Do you have a cloud computing platform? Do you have checked the privacy regulation of the country where the dataset are physically stored? (territoriality) data stored in Italy; there are no details provided on cloud computing platform by Istat; data is subjected to privacy regulation in Italy
Do you have non-personal data? Are you sure that are not “mixed data”? yes, the data is non-personal
IPR of the dataset Do you have created and generated the dataset ? no
Are you the owner of the dataset? How is the owner? no, the owner is Istat
Are you sure to not use third party data without the proper authorization and license ? Are the dataset free from third party licenses or patents? yes
Did you check if there are some limitations in your national legal system for releasing some kind of datasets with open license? yes
Licences Do you release the dataset with an open data license ? In case of the use of CC0 do you check that you have all the right necessary for this particular kind of license (e.g., jurisdiction)? yes
Do you include the clause: "In any case the dataset can’t be used for re-identifying the person" ? no, it is not present in Istat
Do you release the API (in case you have) with an open source license ? no, because we have not released the API
Do you check that the open data/API platform license regime is compliance with your IPR policy ? Do you have all the licences related to the open data platform/API software? yes
Limitations on public access Do you check that the dataset concerns your institutional competences, scope and finality? Do you check if the dataset concerns other public administration competences? yes
Do you check the limitations for the publication stated by your national legislation or by the EU directives ? yes
Do you check if there are some limitations connected to the international relations, public security or national defence? yes
Do you check if there are some limitations concerning the public interest ? yes
Do you check the international law limitations ? yes
Do you check the INSPIRE law limitations for the spatial data? yes
Economical Conditions Do you check that the dataset could be released for free ? yes
Do you check if there are some agreements with some other partners in order to release the dataset with a reasonable price ? Istat allows third parties to adapt their dataset also for commercial purposes
Do you check if the open data platform terms of service include a clause of “non liability agreement” regarding the dataset and API provided ? yes, there is a non liability statement
In case you decide to release the dataset to a reasonable price do you check if the limitation imposed by the new directive 2019/1024/EU are respected ? Are you able to calculate the “marginal cost”? Are you able to justify the “reasonable return on investment” limited to cover the costs of collection, production, reproduction, dissemination, preservation and rights clearance? There is a national law that justify your public administration to apply the “reasonable return of investment”? yes, to calculate the "marginal cost" and justify the "reasonable return on investment," it's essential to consider the costs associated with the various stages of data provision and the specific conditions outlined in the Open Data Directive. This may involve assessing the direct costs of data collection, production, and dissemination, as well as indirect costs such as preservation and rights clearance. The Italian legal framework for the re-use of public sector information (PSI) is governed by several laws and regulations. The main law for cost-free access to PSI is Act no. 241 of 7 August 1990, which provides for general access to government documents, although access in many cases depends on the existence of a legal interest.
In case you decide to release the dataset to a reasonable price do you check the e-Commerce directive and regulation? yes
Temporary aspects Do you have a temporary policy for updating the dataset ? yes, it is present in Istat as stated in the quality analysis
Do you have some mechanism for informing the end-user that the dataset is updated at a given time to avoid mis-usage and so potential risk of damage ? yes
Did you check if the dataset for some reason can’t be indexed by the research engines (e.g. Google, Yahoo, etc.) ? yes, it is indexed correctly
In case of personal data, do you have a reasonable technical mechanism for collecting request of deletion (e.g. right to be forgotten)? the data dealt with is non-personal

Hourly wage by educational qualification (2014-2021)
Issues Questions Dataset
Privacy Is the dataset free of any personal data as defined in the Regulation (EU) 2016/679? yes
Is the dataset free of any indirect personal data that could be used for identifying the natural person? If so, is there a law that authorize the PA to release them? Or any other legal basis? Identify the legal basis. yes
Is the dataset free of any particular personal data (art. 9 GDPR)? If so is there a law that authorize the PA to release them? yes
Is the dataset free of any information that combined with common data available in the web, could identify the person? If so, is there a law that authorize the PA to release them? yes
Is the dataset free of any information related to human rights (e.g. refugees, witness protection, etc.)? yes
Do you use a tool for calculating the range of the risk of de-anonymization? Do you anonymize the dataset? With which technique? Did you check the three mandatory parameters: singling out, linking out, inference out? no, the dataset is already anonymized
Are you using geolocalization capabilities ? Do you check that the geolocalization process can’t identify single individuals in some circumstances? yes, but the wage is the median of all wages in the area therefore no personal data is directly implied in the dataset
Did you check that the open data platform respect all the privacy regulations (registration of the end-user, profiling, cookies, analytics, etc.)? yes
Do you know who are in your open data platform the Controller and Processor of the privacy data of the system? the Controller is the National Institute of Statistics, and the Processor is Istat
Where the datasets are physically stored (country and jurisdiction)? Do you have a cloud computing platform? Do you have checked the privacy regulation of the country where the dataset are physically stored? (territoriality) data stored in Italy; there are no details provided on cloud computing platform by Istat; data is subjected to privacy regulation in Italy
Do you have non-personal data? Are you sure that are not “mixed data”? yes, the data is non-personal
IPR of the dataset Do you have created and generated the dataset ? no
Are you the owner of the dataset? How is the owner? no, the owner is Istat
Are you sure to not use third party data without the proper authorization and license ? Are the dataset free from third party licenses or patents? yes
Do you have checked if there are some limitations in your national legal system for releasing some kind of datasets with open license? yes
Licences Do you release the dataset with an open data license ? In case of the use of CC0 do you check that you have all the right necessary for this particular kind of license (e.g., jurisdiction)? yes
Do you include the clause: "In any case the dataset can’t be used for re-identifying the person" ? no, it is not present in Istat
Do you release the API (in case you have) with an open source license ? no, because we have not released the API
Do you check that the open data/API platform license regime is compliance with your IPR policy ? Do you have all the licences related to the open data platform/API software? yes
Limitations on public access Do you check that the dataset concerns your institutional competences, scope and finality? Do you check if the dataset concerns other public administration competences? yes
Do you check the limitations for the publication stated by your national legislation or by the EU directives ? yes
Do you check if there are some limitations connected to the international relations, public security or national defence? yes
Do you check if there are some limitations concerning the public interest ? yes
Do you check the international law limitations ? yes
Do you check the INSPIRE law limitations for the spatial data? yes
Economical Conditions Do you check that the dataset could be released for free ? yes
Do you check if there are some agreements with some other partners in order to release the dataset with a reasonable price ? Istat allows third parties to adapt their dataset also for commercial purposes
Do you check if the open data platform terms of service include a clause of “non liability agreement” regarding the dataset and API provided ? yes, there is a non liability statement
In case you decide to release the dataset to a reasonable price do you check if the limitation imposed by the new directive 2019/1024/EU are respected ? Are you able to calculate the “marginal cost”? Are you able to justify the “reasonable return on investment” limited to cover the costs of collection, production, reproduction, dissemination, preservation and rights clearance? There is a national law that justify your public administration to apply the “reasonable return of investment”? yes, to calculate the "marginal cost" and justify the "reasonable return on investment," it's essential to consider the costs associated with the various stages of data provision and the specific conditions outlined in the Open Data Directive. This may involve assessing the direct costs of data collection, production, and dissemination, as well as indirect costs such as preservation and rights clearance. The Italian legal framework for the re-use of public sector information (PSI) is governed by several laws and regulations. The main law for cost-free access to PSI is Act no. 241 of 7 August 1990, which provides for general access to government documents, although access in many cases depends on the existence of a legal interest.
In case you decide to release the dataset to a reasonable price do you check the e-Commerce directive and regulation? yes
Temporary aspects Do you have a temporary policy for updating the dataset ? yes, it is present in Istat as stated in the quality analysis
Do you have some mechanism for informing the end-user that the dataset is updated at a given time to avoid mis-usage and so potential risk of damage ? yes
Did you check if the dataset for some reason can’t be indexed by the research engines (e.g. Google, Yahoo, etc.) ? yes, it is indexed correctly
In case of personal data, do you have a reasonable technical mechanism for collecting request of deletion (e.g. right to be forgotten)? the data dealt with is non-personal

Employment rate after graduation (2014-2022)
Issues Questions Dataset*
Privacy Is the dataset free of any personal data as defined in the Regulation (EU) 2016/679? yes, because only the graduates that agreed to being contacted were actually taken into consideration for the analysis
Is the dataset free of any indirect personal data that could be used for identifying the natural person? If so, is there a law that authorize the PA to release them? Or any other legal basis? Identify the legal basis. yes
Is the dataset free of any particular personal data (art. 9 GDPR)? If so is there a law that authorize the PA to release them? yes
Is the dataset free of any information that combined with common data available in the web, could identify the person? If so, is there a law that authorize the PA to release them? yes, because the employment rate is measured in percentages and displayed only according to such measures
Is the dataset free of any information related to human rights (e.g. refugees, witness protection, etc.)? yes
Do you use a tool for calculating the range of the risk of de-anonymization? Do you anonymize the dataset? With which technique? Did you check the three mandatory parameters: singling out, linking out, inference out? no, the dataset is already anonymized
Are you using geolocalization capabilities ? Do you check that the geolocalization process can’t identify single individuals in some circumstances? no
Did you check that the open data platform respect all the privacy regulations (registration of the end-user, profiling, cookies, analytics, etc.)? yes
Do you know who are in your open data platform the Controller and Processor of the privacy data of the system? the Controller is the AlmaLaurea Interuniversity Consortium, and the Processor is AlmaLaurea
Where the datasets are physically stored (country and jurisdiction)? Do you have a cloud computing platform? Do you have checked the privacy regulation of the country where the dataset are physically stored? (territoriality) data stored in Italy; the cloud computing platform is provided by the Consorzio Interuniversitario Cineca; data is subjected to privacy regulation in Italy
Do you have non-personal data? Are you sure that are not “mixed data”? yes, the data is anonymized and therefore non-personal
IPR of the dataset Do you have created and generated the dataset ? no
Are you the owner of the dataset? How is the owner? no, the owner is AlmaLaurea
Are you sure to not use third party data without the proper authorization and license ? Are the dataset free from third party licenses or patents? yes
Do you have checked if there are some limitations in your national legal system for releasing some kind of datasets with open license? yes
Licences Do you release the dataset with an open data license ? In case of the use of CC0 do you check that you have all the right necessary for this particular kind of license (e.g., jurisdiction)? no, the data is released with a non specified license for which one can only reproduce it if the use is not commercial
Do you include the clause: "In any case the dataset can’t be used for re-identifying the person" ? no, it is not present in AlmaLaurea
Do you release the API (in case you have) with an open source license ? no, because we have not released the API
Do you check that the open data/API platform license regime is compliance with your IPR policy ? Do you have all the licences related to the open data platform/API software? yes
Limitations on public access Do you check that the dataset concerns your institutional competences, scope and finality? Do you check if the dataset concerns other public administration competences? yes
Do you check the limitations for the publication stated by your national legislation or by the EU directives ? yes
Do you check if there are some limitations connected to the international relations, public security or national defence? yes
Do you check if there are some limitations concerning the public interest ? yes
Do you check the international law limitations ? yes
Do you check the INSPIRE law limitations for the spatial data? yes
Economical Conditions Do you check that the dataset could be released for free ? yes
Do you check if there are some agreements with some other partners in order to release the dataset with a reasonable price ? AlmaLaurea does not allow third parties to adapt their dataset for commercial purposes
Do you check if the open data platform terms of service include a clause of “non liability agreement” regarding the dataset and API provided ? yes, there is a statement in which AlmaLaurea declares that it is not liable for any damages or losses arising from the use of its database
In case you decide to release the dataset to a reasonable price do you check if the limitation imposed by the new directive 2019/1024/EU are respected ? Are you able to calculate the “marginal cost”? Are you able to justify the “reasonable return on investment” limited to cover the costs of collection, production, reproduction, dissemination, preservation and rights clearance? There is a national law that justify your public administration to apply the “reasonable return of investment”? yes, to calculate the "marginal cost" and justify the "reasonable return on investment," it's essential to consider the costs associated with the various stages of data provision and the specific conditions outlined in the Open Data Directive. This may involve assessing the direct costs of data collection, production, and dissemination, as well as indirect costs such as preservation and rights clearance. The Italian legal framework for the re-use of public sector information (PSI) is governed by several laws and regulations. The main law for cost-free access to PSI is Act no. 241 of 7 August 1990, which provides for general access to government documents, although access in many cases depends on the existence of a legal interest.
In case you decide to release the dataset to a reasonable price do you check the e-Commerce directive and regulation? yes
Temporary aspects Do you have a temporary policy for updating the dataset ? yes, it seems to be present given the yearly updates but not clearly outlined
Do you have some mechanism for informing the end-user that the dataset is updated at a given time to avoid mis-usage and so potential risk of damage ? yes
Did you check if the dataset for some reason can’t be indexed by the research engines (e.g. Google, Yahoo, etc.) ? yes, it is indexed correctly
In case of personal data, do you have a reasonable technical mechanism for collecting request of deletion (e.g. right to be forgotten)? the data dealt with is non-personal

*The datasets are downloadable individually per year, but the legal analysis resulted the same for all of them. Therefore, it was displayed only once for all the downloaded datasets.

Our analysis adhered to key data ethics principles, including fairness, accountability, transparency, and anonymity. We referenced guidelines from reputable sources like "Data ethics: principles and guidelines for Companies, Authorities and Organizations" and the UK government's "Data ethics framework."
In examining the data sources, ISTAT follows ethical and legal standards, emphasizing transparency, accessibility, and privacy protection. The institution aligns with Eurostat's framework, demonstrating a commitment to high standards and consistency in statistical practices. For AlmaLaurea, data on the Italian University's state has been annually collected since 1996, emphasizing accessibility and anonymity for non-commercial use. The organization is obligated to publish information in accordance with Legislative Decree 33/2013, granting the right to request such information. Overall, both ISTAT and AlmaLaurea demonstrate a commitment to ethical data handling practices, providing transparent, accessible, and anonymized data while adhering to legal and regulatory requirements. Further informations can be found on the documentation part of the website.

This is the third item's accordion body. It is hidden by default, until the collapse plugin adds the appropriate classes that we use to style each element. These classes control the overall appearance, as well as the showing and hiding via CSS transitions. You can modify any of this with custom CSS or overriding our default variables. It's also worth noting that just about any HTML can go within the .accordion-body, though the transition does limit overflow.

Visualization


I2: Working satisfaction per hourly wage

This visualisation showcases the relation between satisfaction of workers and their hourly wage. The columns display the satisfaction levels expressed in percentages, whereas the line in the chart displays the hourly wage in euros. For clarity purposes, you can refer to the legend in the graph, which is also interactive.

I3: Work wages across sectors

This visualisation showcases the average salary based on type of contract, age of the employees and educational qualification. The graphs represent four diffent areas of Italy, and a dropdown menu allows you to select the working sector to inspect. For clarity purposes, you can refer to the legend in the graph, which is interactive.

I4: Graduates' employment status

This visualisation showcases the graduates' employment status by portraying not only their satisfaction and occupation levels (displayed by the columns in different colours) but also their hourly wage on average (expressed in euros and portrayed by the line crossing the graph). For clarity puroposes, interact with the legend and select the variables you want to consider.


I5: Emigration and economic independence

This visualisation showcases on a map different variables: the percentages of young people still living at their parents' (in purple), the average house prices and the number of emigrated people. The map was chosen to highlight the differences between the different areas of Italy; however, the variable of time was taken into consideration in order to also show the changes over the years 2014-2022. Click on the spikes to visualize the data corresponding to the specific year and the specific variable!