'Dublin' statistics (migr_dub)

National Reference Metadata in Single Integrated Metadata Structure (SIMS)

Compiling agency: Italian Ministry of Interior


Eurostat metadata
Reference metadata
1. Contact
2. Metadata update
3. Statistical presentation
4. Unit of measure
5. Reference Period
6. Institutional Mandate
7. Confidentiality
8. Release policy
9. Frequency of dissemination
10. Accessibility and clarity
11. Quality management
12. Relevance
13. Accuracy
14. Timeliness and punctuality
15. Coherence and comparability
16. Cost and Burden
17. Data revision
18. Statistical processing
19. Comment
Related Metadata
Annexes (including footnotes)



For any question on data and metadata, please contact: Eurostat user support

Download


1. Contact Top
1.1. Contact organisation

Italian Ministry of Interior

1.2. Contact organisation unit

Department of Civil Liberties and Immigration, Central Directorate for Civil Services and Immigration, Dublin Unit

1.5. Contact mail address

Piazza del Viminale, 1 - 00184 ROME - ITALY


2. Metadata update Top
2.1. Metadata last certified 22/09/2023
2.2. Metadata last posted 22/09/2023
2.3. Metadata last update 22/09/2023


3. Statistical presentation Top
3.1. Data description

This metadata information is provided by the authorities of Italy to ensure compliance with the requirements of Article 4.4 (Dublin statistics) of the Regulation (EC) 862/2007 on Migration and International Protection as amended by the Regulation (EU) 2020/851.

As required by Article 9 of the Regulation (EC) 862/2007, Member States must report to Eurostat on the data sources used, the reasons for the selection of these sources and the effects of the selected data on the quality of the statistics. Member States shall provide Eurostat with all the information necessary to evaluate the quality, comparability and completeness of the statistical information.

The reference document used for assessing the compliance of the concepts and definitions in this metadata file is the document Dublin statistics - Eurostat Technical guidelines to Dublin statistics (see Annex).

3.1.1. General description and overview of the statistical domain at national level

For outgoing requests, the Police headquarters or border police, after the registration of the asylum claim, verify the necessity to apply the Dublin procedure and register the person in the data base named "Vestanet" and, if the case, in the database named "Dublinet". All the information about the Dublin procedure is registered in the Dublin database, and the procedure is followed by the Dublin Unit until the transfer to another Member State responsible for the asylum procedure. In both databases, after the transfer the procedure is closed.

For Incoming requests, the first registration is done by the Dublin Unit in the "Dublin" database. In case of acceptance and after the transfer to Italy the person is also registered in Dublinet (only if the person must follow the asylum procedure, otherwise, in case he/she wants to withdrawn the asylum claim, he/she will be registered for the voluntary return in the "RVA" database).

Dublin statistics contain information based on Article 4.4 of the Regulation (EC) 862/2007 with reference to:

  • The number of requests for taking back or taking charge of an asylum seeker or a third-country national.
  • The provisions on which the requests for taking back or taking charge are based.
  • The decisions taken in response to the requests for taking back or taking charge.
  • The number of unilateral decisions taken by Member States to examine the application of an asylum seeker
  • The numbers of transfers to which the decisions taken in response to the requests for taking back or taking charge lead.
  • The number of requests for information and responses on such requests.
3.2. Classification system

See below.

3.2.1. International and national classifications and breakdowns used
Classification Eurostat breakdown National breakdown
Request Total, Request, Re-examination request, Unknown  Total, Request, Re-examination request, Unknown
Decision on request Total, Positive decision, Negative decision, Unknown  Total, Positive decision, Negative decision, Unknown
Legal provision (Dublin criteria) Please consult the latest Technical Guidelines documentation (in Annex)  Please consult the latest Technical Guidelines documentation (in Annex)
Duration of transfer Total, From 1 to 6 months, From 7 to 12 months, From 13 to 18 months  Total, From 1 to 6 months, From 7 to 12 months, From 13 to 18 months
Duration of response to a request for information Total, 5 weeks or less, Over 5 weeks, Unknown  Total, 5 weeks or less, Over 5 weeks, Unknown
Sex Total, Males, Females, Unknown  Total, Males, Females, Unknown
Applicant Total, Adult, Unaccompanied minor, Accompanied minor, Unknown  Total, Adult, Unaccompanied minor, Accompanied minor, Unknown
3.3. Coverage - sector

Migration and international protection – Dublin statistics

3.4. Statistical concepts and definitions

See below.

3.4.1. Definitions and discrepancies
Concept / Variable Definition at national level Discrepancy from Eurostat definition
Request For the incoming (resp. outgoing) dataset. Requests to take back to take charge of an asylum applicant or requests for information addressed by the Member States (Partner) to the declaring Member State (Geo) (resp. by the declaring Member State (Geo) to the Member States (Partner)).  None
Re-examination request For incoming (resp.outgoing) dataset. Total number of re-examination requests to take back and to take charge (disaggregated in requests, requests with eurodac, accepted, refused)  None
Request based on Eurodac Number of incoming/outgoing taking charge/taking back requests (requests, accepted and refused)  based on Eurodac hits.  None
Transfer

For outgoing: number of transfer requests (taking charge and taking back) which have been effectively carried out by Italy to Member State X for incoming: number of transfer requests (taking charge and taking back) which have been effectively carried out by Member State X to Italy

 None
Responsibility by default (Art. 3.2 First paragraph): no prior criteria applicable Article 3.2 First paragraph

When an applicant applies for international protection in Italy and Italy cannot identify the responsible Member State on the basis of one of the responsibility criteria, it shall become responsible for the application.  Whereas take back/charge requests imply an exchange between Member States, Article 3(2), first paragraph, applies from the time when Italy comes to the conclusion that no other Member State can be designated on the basis of the responsibility criteria. There is no need to consult any other Member State for that purpose.

 
Responsibility by default (Art. 3.2 Second and third paragraph): no transfer Article 3.2 second and third paragraph
When Italy cannot identify the responsible Member State, no transfer to other Member State.
 
Responsibility by default (Art. 29.2): transfer not implemented All transfers that cannot be implemented  
3.5. Statistical unit

The text of Art.4 of the Regulation (EC) 862/2007 refers in general to statistics based on the number of persons and not on the number of applications. However, the article describing the 'Dublin' statistics (Art.4.4) refers to statistics based on the number of requests. Commission services recommend that Art.4.4 (more precisely 4.4.a, 4.4.c and 4.4.d) is interpreted as referring to the number of persons concerned by each request, decision and transfer. Italy is in line with this definition.

3.6. Statistical population

Third country nationals, defined as "any person who is not a citizen of the Union within the meaning of Article 17 (1) of the Treaty, including stateless persons" (Art 2.1 (i) of the Regulation), applying for asylum at the border or in the territory. Number of persons concerned by each request, decision and transfer.

3.7. Reference area

Italy.

3.8. Coverage - Time

Regulation (EC) 862/2007 applies to Dublin statistics collected since 2008.

3.9. Base period

Not applicable.


4. Unit of measure Top

Number (number of requests, number of decisions, number of transfers, etc.).


5. Reference Period Top

2022 Calendar year.


6. Institutional Mandate Top
6.1. Institutional Mandate - legal acts and other agreements

The compilation of Dublin statistics is based on Article 4.4 of Regulation (EC) 862/2007 of 11 July 2007 which depicts in details the data provisions Italy is bound to supply Eurostat with.

6.2. Institutional Mandate - data sharing

Not applicable.


7. Confidentiality Top
7.1. Confidentiality - policy

Regulation (EC) No 223/2009 on European statistics (recital 24 and Article 20(4)) of 11 March 2009 (OJ L 87, p. 164), stipulates the need to establish common principles and guidelines ensuring the confidentiality of data used for the production of European statistics and the access to those confidential data with due account for technical developments and the requirements of users in a democratic society.

7.1.1. Information on the existence of a national policy for (not) releasing the Dublin data before a certain time after the end of reference period has passed

No national policy.

7.1.2. Required confidentiality by law and signed legal confidentiality commitments by survey staff

Not applicable.

7.1.3. Potential micro-data access for research purposes by external users and confidentiality provisions applied

Not applicable.

7.1.4. Procedures for ensuring confidentiality during collection, processing and dissemination, including rules for determining confidential cells

Application of GDPRS.

7.2. Confidentiality - data treatment

Not applicable.


8. Release policy Top
8.1. Release calendar

Not applicable.

8.2. Release calendar access

Not applicable.

8.3. Release policy - user access

In line with the Community legal framework and the European Statistics Code of Practice Eurostat disseminates European statistics on Eurostat's website respecting professional independence and in an objective, professional and transparent manner in which all users are treated equitably. The detailed arrangements are governed by the Eurostat protocol on impartial access to Eurostat data for users.

For the dissemination in Italy, not fixed.


9. Frequency of dissemination Top

Although data periodicity is annual, data is updated on a continuous basis following any new incoming data input (first or revised data). Eurostat statistics are disseminated annualy. The frequency of data transmission to Eurostat is annual and the national dissemination is not available


10. Accessibility and clarity Top
10.1. Dissemination format - News release

Data on Dublin statistics are used in the frame of the annual Release made by the Italian Ministry of Interior.

This Releases can be found under this portal: Annuario delle Statistiche Ufficiali del Ministero dell'Interno - Edizione 2020 - Ufficio centrale di statistica

10.2. Dissemination format - Publications

No Italian publications.

10.3. Dissemination format - online database

No Italian database online is available.

10.3.1. Data tables - consultations

Not applicable.

10.4. Dissemination format - microdata access

Not applicable.

10.5. Dissemination format - other

Not applicable.

10.5.1. Metadata - consultations

Not applicable.

10.6. Documentation on methodology

Please see the annex "Technical Guidelines on Dublin statistics".

Please refer as well to Article 4.4 of the Regulation (EC) No 862/2007.

10.6.1. Metadata completeness - rate

Not applicable.

10.7. Quality management - documentation

Not available.


11. Quality management Top
11.1. Quality assurance

The quality of data in both Dublinet and Vestanet databases are assured by the IT agency in charge of data quality. 

11.2. Quality management - assessment

Not available.

11.2.1. Overall quality assessment, at dataset level

 Dataset

 Quality

Details in case of Sufficient or Poor quality

Incoming 'Dublin' requests by submitting country (PARTNER), type of request, legal provision, sex and type of applicant

 Good

 

Outgoing 'Dublin' requests by receiving country (PARTNER), type of request, legal provision, sex and type of applicant

 Good

 

Incoming 'Dublin' requests based on EURODAC by submitting country (PARTNER), type of request, legal provision, sex and type of applicant

 Good

 

Outgoing 'Dublin' requests based on EURODAC by receiving country (PARTNER), type of request, legal provision, sex and type of applicant

 Good

 

Pending 'Dublin' incoming requests by submitting country (PARTNER), type of request, sex and type of applicant

 Good

 

Pending 'Dublin' outgoing requests by receiving country (PARTNER), type of request, sex and type of applicant

 Good

 

Incoming 'Dublin' requests for information by submitting country (PARTNER), legal provision, sex and type of applicant

 Good

 

Outgoing 'Dublin' requests for information by receiving country (PARTNER), legal provision, sex and type of applicant

 Good

 

Incoming responses to 'Dublin' requests for information by submitting country (PARTNER), legal provision, duration of response, sex and type of applicant

 Good

 

Outgoing responses to 'Dublin' requests for information by receiving country (PARTNER), legal provision, duration of response, sex and type of applicant

 Good

 

Unilateral 'Dublin' decisions by partner country, type of decision, sex and type of applicant

 Good

 

Decisions on incoming 'Dublin' requests by submitting country (PARTNER), type of decision, type of request, legal provision, sex and type of applicant

 Good

 

Decisions on outgoing 'Dublin' requests by receiving country (PARTNER), type of decision, type of request, legal provision, sex and type of applicant

 Good

 

Decisions on Incoming 'Dublin' requests based on EURODAC by submitting country (PARTNER), type of decision, type of request, legal provision, sex and type of applicant

 Good

 

Decisions on outgoing 'Dublin' requests based on EURODAC by receiving country (PARTNER), type of decision, type of request, legal provision, sex and type of applicant

 Good

 

Incoming 'Dublin' transfers by submitting country (PARTNER), legal provision, duration of transfer, sex and type of applicant

 Good

 

Outgoing 'Dublin' transfers by receiving country (PARTNER), legal provision, duration of transfer, sex and type of applicant

 Good

 

Pending incoming 'Dublin' transfers by submitting country (PARTNER), sex and type of applicant

 Good

 

Pending outgoing 'Dublin' transfers by receiving country (PARTNER), sex and type of applicant

 Good

 

 

  • Good quality (extensive quality) - all quality requirements are met according to the standard quality criteria and in line with the Technical Guidelines for the data collection of Dublin statistics (Annex).
  • Sufficient quality (acceptable quality) - minimum quality requirements are met: minor issues exist which need to be improved.
  • Poor quality (inadequate quality) - the data do not meet the minimum quality requirements: important/many issues exist which affect the quality of the data and which need to be solved.


12. Relevance Top
12.1. Relevance - User Needs

The statistics collected under Regulation (EC) 862/2007 are used by a wide range of users at national, European and International level to cover various usersʼ needs.

 

Users of Dublin statistics :

  • national authorities (Ministries of Interior, Ministries of Justice, Migration agencies) who use Dublin and Asylum data to monitor or project the development of their national asylum procedures
  • the European Migration Network (EMN) which uses the data as a basis for its annual EU- and national-level statistical and analytical reports
  • researchers and students conducting analysis and research in the field of asylum
  • journalists and international organisations in the area of asylum and migration

Unmet user needs (on statistics) and reasons why these needs cannot be satisfied (at national and international level) : At present all statistical user needs are met.

12.2. Relevance - User Satisfaction

Italy does not conduct user satisfaction surveys per se. Instead the users satisfaction is monitored on a constant way through informal and formal contacts and communications with users and through requests and comments received by users.

12.3. Completeness

See below.

12.3.1. Data completeness - rate

96% (some double counting and some missing data, some errors in database data registration).

12.3.2. Completeness by dataset

Completeness is the extent to which all requested Dublin statistics are provided to Eurostat, according to the data provisions foreseen by Articles 4.4. of Regulation (EC) 862/2007 (as amended by Regulation (EU) 2020/851) and by the Technical Guidelines for Dublin statistics (Annex).

 

Dataset

Completeness

Details in case of Incomplete, Not available or Not applicable

Incoming 'Dublin' requests by submitting country (PARTNER), type of request, legal provision, sex and type of applicant

 Complete

 

Outgoing 'Dublin' requests by receiving country (PARTNER), type of request, legal provision, sex and type of applicant

 Complete

 

Incoming 'Dublin' requests based on EURODAC by submitting country (PARTNER), type of request, legal provision, sex and type of applicant

 Complete

 

Outgoing 'Dublin' requests based on EURODAC by receiving country (PARTNER), type of request, legal provision, sex and type of applicant

 Complete

 

Pending 'Dublin' incoming requests by submitting country (PARTNER), type of request, sex and type of applicant

 Complete

 

Pending 'Dublin' outgoing requests by receiving country (PARTNER), type of request, sex and type of applicant

 Complete

 

Incoming 'Dublin' requests for information by submitting country (PARTNER), legal provision, sex and type of applicant

 Complete

 

Outgoing 'Dublin' requests for information by receiving country (PARTNER), legal provision, sex and type of applicant

 Complete

 

Incoming responses to 'Dublin' requests for information by submitting country (PARTNER), legal provision, duration of response, sex and type of applicant

 Complete

 

Outgoing responses to 'Dublin' requests for information by receiving country (PARTNER), legal provision, duration of response, sex and type of applicant

 Complete

 

Unilateral 'Dublin' decisions by partner country, type of decision, sex and type of applicant

 Complete

 

Decisions on incoming 'Dublin' requests by submitting country (PARTNER), type of decision, type of request, legal provision, sex and type of applicant

 Complete

 

Decisions on outgoing 'Dublin' requests by receiving country (PARTNER), type of decision, type of request, legal provision, sex and type of applicant

 Complete

 

Decisions on Incoming 'Dublin' requests based on EURODAC by submitting country (PARTNER), type of decision, type of request, legal provision, sex and type of applicant

 Complete

 

Decisions on outgoing 'Dublin' requests based on EURODAC by receiving country (PARTNER), type of decision, type of request, legal provision, sex and type of applicant

 Complete

 

Incoming 'Dublin' transfers by submitting country (PARTNER), legal provision, duration of transfer, sex and type of applicant

 Complete

 

Outgoing 'Dublin' transfers by receiving country (PARTNER), legal provision, duration of transfer, sex and type of applicant

 Complete

 

Pending incoming 'Dublin' transfers by submitting country (PARTNER), sex and type of applicant

 Complete

 

Pending outgoing 'Dublin' transfers by receiving country (PARTNER), sex and type of applicant

 Complete

 

 

  • Complete - The statistics are complete: the dataset and all requested breakdowns are available, as foreseen by Regulation (EC) 862/2007 (as amended by Regulation (EU) 2020/851) and the Technical Guidelines for the data collection of Dublin statistics (Annex)
  • Incomplete - The statistics are incomplete: the dataset is available but some of the requested breakdowns are not available, as foreseen by Regulation (EC) 862/2007 (as amended by Regulation (EU) 2020/851) and the Technical Guidelines for the data collection of Dublin statistics (Annex1)
  • Not available - The statistics are not available: the dataset is not available, that is all the requested breakdowns are missing, as foreseen by Regulation (EC) 862/2007 (as amended by Regulation (EU) 2020/851) and the Technical Guidelines for the data collection of Dublin statistics (Annex1)
  • Not applicable - The statistics are Not applicable: the concept/process is not used or it does not exist in the country


13. Accuracy Top
13.1. Accuracy - overall

Overall accuracy of the Dublin Statistics is about 99%.

13.1.1. Assessment of the accuracy of the national Dublin statistics by dataset

Accuracy is the closeness of the data to the exact or true values that the statistics were intended to measure. Reliability is the closeness of the initial provided value to the subsequent (revised) value.

 

Assessment of the accuracy of the national Dublin statistics, at dataset level

Dataset

Accuracy

Summary of main sources of error in case of Good/Low/Very low Accuracy

Incoming 'Dublin' requests by submitting country (PARTNER), type of request, legal provision, sex and type of applicant

 Good

 

Outgoing 'Dublin' requests by receiving country (PARTNER), type of request, legal provision, sex and type of applicant

 Good

 

Incoming 'Dublin' requests based on EURODAC by submitting country (PARTNER), type of request, legal provision, sex and type of applicant

 Good

 

Outgoing 'Dublin' requests based on EURODAC by receiving country (PARTNER), type of request, legal provision, sex and type of applicant

 Good

 

Pending 'Dublin' incoming requests by submitting country (PARTNER), type of request, sex and type of applicant

 Good

 

Pending 'Dublin' outgoing requests by receiving country (PARTNER), type of request, sex and type of applicant

 Good

 

Incoming 'Dublin' requests for information by submitting country (PARTNER), legal provision, sex and type of applicant

 Good

 

Outgoing 'Dublin' requests for information by receiving country (PARTNER), legal provision, sex and type of applicant

 Good

 

Incoming responses to 'Dublin' requests for information by submitting country (PARTNER), legal provision, duration of response, sex and type of applicant

 Good

 

Outgoing responses to 'Dublin' requests for information by receiving country (PARTNER), legal provision, duration of response, sex and type of applicant

 Good

 

Unilateral 'Dublin' decisions by partner country, type of decision, sex and type of applicant

 Good

 

Decisions on incoming 'Dublin' requests by submitting country (PARTNER), type of decision, type of request, legal provision, sex and type of applicant

 Good

 

Decisions on outgoing 'Dublin' requests by receiving country (PARTNER), type of decision, type of request, legal provision, sex and type of applicant

 Good

 

Decisions on Incoming 'Dublin' requests based on EURODAC by submitting country (PARTNER), type of decision, type of request, legal provision, sex and type of applicant

 Good

 

Decisions on outgoing 'Dublin' requests based on EURODAC by receiving country (PARTNER), type of decision, type of request, legal provision, sex and type of applicant

 Good

 

Incoming 'Dublin' transfers by submitting country (PARTNER), legal provision, duration of transfer, sex and type of applicant

 Good

 

Outgoing 'Dublin' transfers by receiving country (PARTNER), legal provision, duration of transfer, sex and type of applicant

 Good

 

Pending incoming 'Dublin' transfers by submitting country (PARTNER), sex and type of applicant

 Good

 

Pending outgoing 'Dublin' transfers by receiving country (PARTNER), sex and type of applicant

 Good

 

  

  • High = 100 % accuracy. The reported statistics measure accurately the target population, as foreseen by Regulation (EC) 862/2007 (as amended by Regulation (EU) 2020/851) and as defined in the Technical Guidelines for Dublin statistics (Annex)
  • Good = 95 - 99 % accuracy. The reported statistics do not cover accurately the target population and a small part of the targeted population is missing, or a small part of non-targeted (erroneous) population is included in the reported statistics; the bias/error in the reported statistics is expected to be small
  • Low 80 - 94 % accuracy. The reported statistics do not cover accurately the target population and a large part of the targeted population is missing, or a large part of non-targeted (erroneous) population is included in the reported statistics; the bias/error in the reported statistics is expected to be large
  • Very low = less than 80 % accuracy. The reported statistics do not cover accurately the target population and a very large part of the targeted population is missing, or a very large part of non-targeted (erroneous) population is included in the reported statistics; the bias/error in the reported statistics is expected to be very large
13.2. Sampling error

Not applicable.

13.2.1. Sampling error - indicators

Not applicable.

13.3. Non-sampling error

See below.

13.3.1. Coverage error

See below.

13.3.1.1. Over-coverage - rate

See the file ‘Proportion of units (persons) reported in the statistics that do not belong to the target populationʼ in annex.

 

No over-coverage (rate = 0%)

 



Annexes:
Proportion of units (persons) reported in the statistics that do not belong to the target population
13.3.1.2. Common units - proportion

Not applicable.

13.3.1.3. Assessment of potential coverage errors

Dataset

Coverage errors - Discrepancies from Eurostat target population

Summary of main sources of errors in case of errors and/or discrepancies from Eurostat practice

Incoming 'Dublin' requests by submitting country (PARTNER), type of request, legal provision, sex and type of applicant

 No

 

Outgoing 'Dublin' requests by receiving country (PARTNER), type of request, legal provision, sex and type of applicant

 No

 

Incoming 'Dublin' requests based on EURODAC by submitting country (PARTNER), type of request, legal provision, sex and type of applicant

 No

 

Outgoing 'Dublin' requests based on EURODAC by receiving country (PARTNER), type of request, legal provision, sex and type of applicant

 No

 

Pending 'Dublin' incoming requests by submitting country (PARTNER), type of request, sex and type of applicant

 No

 

Pending 'Dublin' outgoing requests by receiving country (PARTNER), type of request, sex and type of applicant

 No

 

Incoming 'Dublin' requests for information by submitting country (PARTNER), legal provision, sex and type of applicant

 No

 

Outgoing 'Dublin' requests for information by receiving country (PARTNER), legal provision, sex and type of applicant

 No

 

Incoming responses to 'Dublin' requests for information by submitting country (PARTNER), legal provision, duration of response, sex and type of applicant

 No

 

Outgoing responses to 'Dublin' requests for information by receiving country (PARTNER), legal provision, duration of response, sex and type of applicant

 No

 

Unilateral 'Dublin' decisions by partner country, type of decision, sex and type of applicant

 No

 

Decisions on incoming 'Dublin' requests by submitting country (PARTNER), type of decision, type of request, legal provision, sex and type of applicant

 No

 

Decisions on outgoing 'Dublin' requests by receiving country (PARTNER), type of decision, type of request, legal provision, sex and type of applicant

 No

 

Decisions on Incoming 'Dublin' requests based on EURODAC by submitting country (PARTNER), type of decision, type of request, legal provision, sex and type of applicant

 No

 

Decisions on outgoing 'Dublin' requests based on EURODAC by receiving country (PARTNER), type of decision, type of request, legal provision, sex and type of applicant

 No

 

Incoming 'Dublin' transfers by submitting country (PARTNER), legal provision, duration of transfer, sex and type of applicant

 No

 

Outgoing 'Dublin' transfers by receiving country (PARTNER), legal provision, duration of transfer, sex and type of applicant

 No

 

Pending incoming 'Dublin' transfers by submitting country (PARTNER), sex and type of applicant

 No

 

Pending outgoing 'Dublin' transfers by receiving country (PARTNER), sex and type of applicant

 No

 

13.3.1.4. Average lag of registering (to the national database/register) the following administrative events
Event Lag in number of days Details
An incoming Dublin request from a partner country  5 days Due to the need of controls: first control forensic police and immigration police office
An incoming decision from a partner country accepting the request to take back/charge a person  15 days  
A decision made by the national authority to accept or to reject a request from a partner country to take charge/back a person 15 days Due to the need of controls: first control forensic police and immigration police office
13.3.2. Measurement error

See concept 13.3.4 Processing Error.

13.3.3. Non response error

Not applicable.

13.3.3.1. Unit non-response - rate

Not applicable.

13.3.3.2. Item non-response - rate

Not applicable.

13.3.4. Processing error

Not available.

13.3.5. Model assumption error

Not applicable.


14. Timeliness and punctuality Top
14.1. Timeliness

Data is collected on annual basis (calendar year) and must be transmitted by Italy not later than 3 months after the end of the reference period.

14.1.1. Time lag - first result

- Number of days (on average) after the end of the reference period at which the country is able to report the first/preliminary data, at the earliest : 

Normally on time. For some past years Italy was not able to send data on time due to change of Dublin regulation and necessity to up to date the system.

Normally Italy do not send preliminary data but only consolidated data.

- Reasons for possible long production of the first/preliminary data and plans to improve the situation : 

Italy is updating the databases used to store the data. This could lead to some delays in the production of statistics.

14.1.2. Time lag - final result

- Number of days (on average) after the end of the reference period at which the country is able to report the final data, at the earliest : 

Normally on time. For some past years Italy was not able to send data on time due to change of Dublin regulation and necessity to up to date the system.

Normally Italy do not send a revision of the data.

- Reasons for possible long production of the final data and plans to improve the situation : 

Italy is updating the databases used to store the data. This could lead to some delays in the production of final results.

14.2. Punctuality

90%

14.2.1. Punctuality - delivery and publication

Not applicable.


15. Coherence and comparability Top
15.1. Comparability - geographical

See below.

15.1.1. Asymmetry for mirror flow statistics - coefficient

No asymmetry.

15.1.2. Assessment of possible sources of lack of comparability between countries

Assessment of possible sources of lack of comparability between countries, due to discrepancies from Eurostat concepts, definitions or due to differences in methods.

 

# Topic Response  Explanatory details and assessment of the magnitude of error (where applicable)
1 Does the country report all persons individually (e.g. in case of families all persons must be reported individually)?  Yes  
2 Does the country report each request/decision/transfer concerning the same person during the same year (even if multiple requests/decisions/transfers are made for the same person during the year)?  Yes  
3 For the data on “Requests based on Eurodac hit” and “Decisions based on Eurodac hit”, does the country report also children below 14 years old who are not fingerprinted?  No  
4 In case a request for a person involves more than one partner countries, does the country report all requests it sent/received to/from all the partner countries involved?  Yes  
5 Where the request is accepted based on a different legal basis from the one on which the request was sent, does the country report the data based on the article (legal basis) on which the request is accepted?  Yes  
6 Does the country report only successful incoming transfers (i.e. only those where the country has effectively received the person on its territory)?  Yes  
7 Does the country report only successful outgoing transfers (i.e. those for which the country has undertaken all appropriate measures in order to send a transferee to another Member State)?  Yes  
8 Does the country report transfers for cases where the applicant otherwise travelled back to the Member State responsible on its own within the transfer time limits (without the country organizing the actual transfer)?  No  
9 Does the country report requests sent/received by mistake (i.e. when the actual partner country should have been different than the one intended)?  No  
10 Does the country report a person as adult or minor according to the age of the person at the date of the respective administrative event (e.g. the person was minor at the date of the request, but at the date of transfer the person was not a minor anymore)?  Yes  
11 Does the country carry out the Dublin/Eurodac check before the formal registration of the asylum application?  Yes  
12 For the data of “Article 3.2 first paragraph – Responsible by default: no prior criteria applicable”, does the country report any applicant for which the Dublin criteria do not apply? This means any person who applied for protection in the reporting country, as a first Member State of application, and for whom no Dublin criteria applied for him/her to be taken charge of by another Member State.

 No

 

13 Does the country report under the data of “Decisions on incoming requests” positive decisions accepting a request implicitly?  Yes  
14 Does the country report under the data of “Decisions on outgoing requests” positive decisions accepting a request implicitly?  Yes  
15 Does the country report under the data of “Decisions on incoming requests bases on Eurodac” positive decisions accepting a request implicitly?  Yes  
16 Does the country report under the data of “Decisions on outgoing requests bases on Eurodac” positive decisions accepting a request implicitly?  Yes  
17 For the data of Transfers, in case of different legal basis between the request and the positive decision to accept the responsibility to examine the application, does the country report the legal ground (LEG_PROV) on which the decision (acceptance of request) was based on?  Yes  
18 Does the country report under 'Incoming pending transfers' cases where the partner country did not implement the transfer within the foreseen time limits (Article 29.2)?  No  
19 Does the country report under ‘Outgoing pending transfers' cases where the country did not implement the transfer within the foreseen time limits (Article 29.2)?  No  
15.2. Comparability - over time

Perfect comparabilty over time.

15.2.1. Length of comparable time series

2013-2022.

15.3. Coherence - cross domain

Asylum statistics collected under Article 4 of the Regulation (EC) 862/2007 are based on persons, while Dublin statistics may refer to requests in a few cases.

15.3.1. Coherence - sub annual and annual statistics

No sub-annual statistics.

15.3.2. Coherence - National Accounts

Not applicable.

15.4. Coherence - internal

Not applicable.


16. Cost and Burden Top

Not available.


17. Data revision Top
17.1. Data revision - policy

Not available.

17.1.1. Description of the national revision policy for Dublin statistics

Not available.

17.1.2. Number of revisions planned on average
Data revision practice National practice  Further details (if necessary)
Average number of planned revisions performed during a year (for latest reference year) Data are revised on a continuous basis   
Average number of unplanned revisions performed during a year (usually caused by the discovery of a mistake) Data are revised on a continuous basis   
Main reasons for revisions (new source data are becoming available, new methods/concepts, etc.) and extent to which the revisions improved the accuracy of the data Usually caused by the discovery of a mistake  
Where the request is accepted based on a different legal basis from the one on which the request was sent, Member States have to report their data based on the article (legal basis) on which the request is accepted.

As far it is possible, this applies also to the data on outgoing and incoming requests. In case the requests are submitted/received in a different reference year than the decision was taken, data on requests shall be revised accordingly by both countries.

Does the country revise its data according to the above guidance?

Yes  
17.1.3. Description of the main reasons for revisions

Discovery of a mistake, change of articles for acceptance/refusal, add new born child.

17.2. Data revision - practice

See below.

17.2.1. Data revision - average size

The size of revision gives an idea of the stability of the data while direction is important to understand whether preliminary data tend to overestimate or underestimate the real target population.

 

Not available.


18. Statistical processing Top
18.1. Source data

At the time of registration of a request for international protection, the officers of the Police Headquarters, competent for asylum applications, register all the relevant information in a database called Vestanet. If there is an evidence for the application of the Dublin Regulation, Dublin Unit staff receive an alert in the Dublinet application and process it by creating an "Outgoing" folder. From the same database they forward the request to the MS that is deemed to be responsible for this, via messaging certified by EULISA

The police officers of the Police Headquarters and of the Central Immigration Department, headed by the Ministry of the Interior, and those of the Dublin unit, headed by the Department for civil liberties and immigration of the Ministry of the Interior itself have access to the two communicating databases, Vestanet and Dublinet (DBMS sql-server). In addition to the police officers, officials of the territorial commissions for asylum have access to the Vestanet database, who cannot manage the application as long as it remains in the "Dublin evidence" status, i.e. until the responsible MS has been determined.

The two databases (Vestanet and Dublinet) are connected via a unique key that uniquely identifies the applicant (UNIQUE INDIVIDUAL CODE (CUI) linked to the fingerprints).

For "Incoming" requests, the Dublinet database is automatically fed by messaging (certified by EULISA). The messaging data flows into the Dublinet database and creates new folders, identified with the Eurodac code and the CUI code. The police officers of the Central Immigration Department entered in the same database any information related to identity checks and the position of the applicant on the national territory (residence permits, any crimes committed, expulsions, etc ...).

The data recorded on Dulinet is detailed (complete personal data, Eurodac/CUI code, family relationships, type of Dublinet request, date of registration, request sent, transfer, relocation, attached documents, etc.) and is subsequently aggregated for statistical use by Business Intelligence software for transmission to Eurostat.

18.2. Frequency of data collection

Daily.

18.3. Data collection

Data are daily collected by the Ministry of Interior (Police headquarters) and directly register in the database (see source data). Data are consolidated and up-to-dat by the Dublin Unit (Ministry of Interior).

18.4. Data validation

The validation process takes place through communication of the results and validation by the Dublin Unit.

18.4.1. Validation procedures
Validation activity Performed Periodicity Details (methods and tools)
Check that the population coverage is accurate, as required according to the definitions of the Technical guidelines (Annex)  Yes  Daily  
Compare the data with data of previous periods  Yes  Annual  
Check for outliers  Yes  Daily  
Investigate inconsistencies in the statistics (checking the consistency of "Total" values over each variable)  Yes  Annual  
Verify the statistics against expectations and domain intelligence  Yes  Annual  
Confront the data against other relevant data (e.g. Asylum statistics, of the mirror data from the partner countries)  Yes  Annual  
Check retrospectively (a sample of) the data in the register/database in order to confirm they are accurate  Yes  Bi-annual  
18.5. Data compilation

Data are collected from the “Dublin Unit” caseworker and registered in a database through a DBMS procedures which verifies the correctness and consistency of the data entered. Subsequently, the data is processed using specific statistical software (Business Object) that generates the reports necessary to be sent to Eurostat.

18.5.1. Imputation - rate

Not applicable.

18.6. Adjustment

See below

18.6.1. Seasonal adjustment

None.


19. Comment Top


Related metadata Top


Annexes Top
Eurostat Guidelines on Dublin statistics - v. 3.1 - 2021