'Dublin' statistics (migr_dub)

National Reference Metadata in Single Integrated Metadata Structure (SIMS)

Compiling agency: Ministry of Migration and Asylum


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

Ministry of Migration and Asylum

1.2. Contact organisation unit

General Directorate of Information and Communication Technology

1.5. Contact mail address

196-198 Thivon Av., Ag. Ioannis Rentis, 18233, Athens, Greece


2. Metadata update Top
2.1. Metadata last certified 31/05/2023
2.2. Metadata last posted 16/06/2023
2.3. Metadata last update 16/06/2023


3. Statistical presentation Top
3.1. Data description

This metadata information is provided by the authorities of Greece to ensure compliance with the requirements of Article 4.4 (Dublin statistics) of the Regulation (EC) 862/2007 on Migration and International Protectionas 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

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  Same as Eurostat
Decision on request Total, Positive decision, Negative decision, Unknown  Same as Eurostat
Legal provision (Dublin criteria) Please consult the latest Technical Guidelines documentation (in Annex)  Same as Eurostat
Duration of transfer Total, From 1 to 6 months, From 7 to 12 months, From 13 to 18 months  Same as Eurostat
Duration of response to a request for information Total, 5 weeks or less, Over 5 weeks, Unknown  Same as Eurostat
Sex Total, Males, Females, Unknown  Same as Eurostat
Applicant Total, Adult, Unaccompanied minor, Accompanied minor, Unknown  Same as Eurostat
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  Same as Eurostat  
Re-examination request  Same as Eurostat  
Request based on Eurodac  Same as Eurostat  
Transfer  Same as Eurostat  
Responsibility by default (Art. 3.2 First paragraph): no prior criteria applicable  Same as Eurostat  
Responsibility by default (Art. 3.2 Second and third paragraph): no transfer  Same as Eurostat  
Responsibility by default (Art. 29.2): transfer not implemented  Same as Eurostat  
3.5. Statistical unit

The text of Art.4 of the Regulation (EC) 862/2007 on Migration and international protection 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.

3.6. Statistical population

Member States shall examine the application of any third country national who applies for asylum at the border or in their territory of any one of them.
The application shall be examined by a single Member State, which shall be the one which the criteria set out in Chapter III of Council Regulation (EC) 604/2013 indicates is responsible.
Under certain circumstances, each Member State may examine an application for asylum lodged by a third-country national even if such examination is not its responsibility according to the criteria laid down in Council Regulation (EC) 604/2013.
In such cases, this Member State shall become the Member State responsible for the examination of the application.
The Member State conducting a procedure for determining the Member State responsible or the Member State which has been requested to take charge of or to take back the applicant shall inform the Member State previously responsible.

Requests: 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)).

Total number of requests: Total number of requests to take back and to take charge of an asylum applicant.

Total number of taking charge requests: Total number of taking charge requests
This category is split in three categories based on the Regulation (EC) 604/2013.

Taking charge requests: Family reasons (Art.6, Art.7, Art.8, Art.14): Number of taking charge requests for family reasons. See Regulation (EC) 604/2013 for more details on Art.6,7,8 and 14.

Taking charge requests: Documentation and entry reasons (Art.9, Art.10, Art.11, Art.12):Number of taking charge requests for documentation and entry reasons. See Regulation (EC) 604/2013 for more details on Art.9,10 and 11.

Taking charge requests: Humanitarian reasons (Art.15): Number of taking charge requests for humanitarian reasons. See Regulation (EC) 604/2013 for more details on Art.15.

Total number of taking back requests: Total number of taking back requests
This category is split in four categories based on the Regulation (EC) 604/2013.

Taking back requests: Withdrawal of application during Dublin procedure (Art.4.5):Number of taking back request due to the withdrawal on application during Dublin procedure. Regulation (EC) 604/2013 for more details on Art.4.5.

Taking back requests: Under examination - no permission to stay  (Art.16.1.c):Number of taking back request due to the presence of the asylum applicant in a country without permission to stay when this country differs from the country where his application is under examination. Regulation (EC) 604/2013 for more details on Art.16.1.c.

Taking back requests: Withdrawal - new application  (Art.16.1.d): Number of taking back request due to the withdrawal of an application under examination in a country while lodging a new application in another country. See Regulation (EC) 604/2013 for more details on Art.16.1.d.

Taking back requests: Rejection - no permission to stay  (Art.16.1.e): Number of taking back request due to the withdrawal due to the presence of asylum applicant in a country without permission to stay and whose application has been rejected in the country where his application was examined.

Total EURODAC: Number of incoming (resp. incoming accepted, incoming refused, outgoing, outgoing accepted, outgoing refused) requests based on Eurodac hits.

Taking charge requests based on EURODAC: Number of incoming (resp. incoming accepted, incoming refused, outgoing, outgoing accepted, outgoing refused) taking charge requests based on Eurodac hits.

Taking back requests based EURODAC: Number of incoming (resp. incoming accepted, incoming refused, outgoing, outgoing accepted, outgoing refused) taking back requests based on Eurodac hits.

Total number of pending requests at the end of reference period: Number of requests for take charge and take back addressed by other Member States to which a response is pending at the end of the reference period.

Total number of requests for information: Number of request for information submitted by the Member States (Partner) to the declaring Member State (Geo).

Number of answers to requests for information: Number of request for information provided by the Member States (Partner) to the declaring Member State (Geo).

3.7. Reference area

Greece.

3.8. Coverage - Time

Available data since 2014.

3.9. Base period

Not applicable.


4. Unit of measure Top

The unit of measure is the absolute number of persons (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 Member States are bound to supply Eurostat with.

All the Dublin Statistics are produced by the Greek Asylum Service database and mirror the procedures followed in compliance with the Dublin Regulation III.

6.2. Institutional Mandate - data sharing

Not available.


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

Not applicable.

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

Not applicable.

7.2. Confidentiality - data treatment

Not applicable.


8. Release policy Top
8.1. Release calendar

Non applicable.

8.2. Release calendar access

Non applicable.

8.3. Release policy - user access

Not applicable.


9. Frequency of dissemination Top

Although data periodicity is annual, data is updated following any data revision.


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

Non applicable.

10.2. Dissemination format - Publications

Data on Dublin Statistics are used for Ministry ad-hoc publications under this portal: http://migration.gov.gr/en/

10.3. Dissemination format - online database

Not applicable.

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

100%

10.7. Quality management - documentation

See annexes.


11. Quality management Top

The quality of statistical products and processes is ensured by regularly updating our organization database.

11.1. Quality assurance

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.

11.2. Quality management - assessment

Good quality

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:

  • various policy DGs in the European Commission, like DG Migration and Home Affairs and European Union Asylum Agency for designing, funding and implementing asylum related policies in the EU
  • European Parliament
  • national authorities (Ministries of Interior, Ministries of Justice, Migration agencies) that use Dublin and Asylum data to monitor or develop their national asylum procedures
  • European Migration Network (EMN) that 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) : Unknown

12.2. Relevance - User Satisfaction

Unknown.

12.3. Completeness

All the data requested are available.

12.3.1. Data completeness - rate

100%

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 (Annex)
  • 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 (Annex)
  • 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

High accuracy.

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

 High

 

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

 High

 

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

 High

 

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

 High

 

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

 High

 

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

 High

 

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

 High

 

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

 High

 

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

 High

 

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

 High

 

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

 High

 

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

 High

 

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

 High

 

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

 High

 

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

 High

 

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

 High

 

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

 High

 

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

 High

 

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

 High

 

  

  • 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

Not available.

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.



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  30 days  
An incoming decision from a partner country accepting the request to take back/charge a person  30 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  30 days  
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

See below concepts 14.1.1 and 14.1.2.

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:

One month after the end of the reference period.

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

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 : 

On average, the earliest we can report final data is 70 days after the end of the reporting period.

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

14.2. Punctuality

The punctuality of the data is overall good.

14.2.1. Punctuality - delivery and publication

Not applicable.


15. Coherence and comparability Top

According to the guidelines, Dublin statistics refer to individuals.

15.1. Comparability - geographical

Not applicable.

15.1.1. Asymmetry for mirror flow statistics - coefficient

Not available.

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?  Yes  
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)?  Yes  
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?  No  
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?  No  
14 Does the country report under the data of “Decisions on outgoing requests” positive decisions accepting a request implicitly?  No  
15 Does the country report under the data of “Decisions on incoming requests bases on Eurodac” positive decisions accepting a request implicitly?  No  
16 Does the country report under the data of “Decisions on outgoing requests bases on Eurodac” positive decisions accepting a request implicitly?  No  
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?  No  
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

Dublin data is comparable over the years.

15.2.1. Length of comparable time series

Since 2014 - onwards.

15.3. Coherence - cross domain

Not applicable.

15.3.1. Coherence - sub annual and annual statistics

Not applicable.

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

Data are revised on a continuous basis according to the most recently updated data provided by other countries.

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) 12 per year  
Average number of unplanned revisions performed during a year (usually caused by the discovery of a mistake) Unknown  
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 New source data are becoming available  
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, the data is reviewed based on the above guidelines  
17.1.3. Description of the main reasons for revisions

Data are revised on a continuous basis according to the most recently updated data provided by other countries.

When we receive new information from another Member State about changes to data we have already created, we proceed to update it.

17.2. Data revision - practice

We check the data periodically, taking into account any new information that has been given to us, and proceed to revise the statistical data.

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.

We are unable to provide a specific number of revisions in a period of time. However, a possible average of revisions could be at least ten revisions per year.


18. Statistical processing Top
18.1. Source data

Greece Asylum Service Database (Administrative source).

18.2. Frequency of data collection

The collection of information/data for the production of Dublin statistics is done on a monthly basis by the Greece Asylum Service Database.

18.3. Data collection

The information for Dublin Statistics is collected from the Greece Asylum Service Database in Excel format which is processed in order to produce the required datasets.

18.4. Data validation

The Dublin data is entered through a management application into the Hellenic Asylum Service Database by the service's employees.

Data reports are drawn from it on a monthly basis in excel format and processed and validated to produce the final reports in order to satisfy the statistical requests of internal and external stakeholders.

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  Monthly  
Compare the data with data of previous periods  Yes  Quarterly  
Check for outliers  Yes  Monthly  
Investigate inconsistencies in the statistics (checking the consistency of "Total" values over each variable)  Yes  Monthly  
Verify the statistics against expectations and domain intelligence  No    
Confront the data against other relevant data (e.g. Asylum statistics, of the mirror data from the partner countries)  Yes  Annually  
Check retrospectively (a sample of) the data in the register/database in order to confirm they are accurate  Yes  Annually  
18.5. Data compilation

The Dublin data is entered through a management application into the Hellenic Asylum Service Database by the service's employees.

Data reports are drawn from it on a monthly basis in excel format and processed according to the given set of rules to produce the final reports in order to satisfy all possible statistics requests.

18.5.1. Imputation - rate

Not applicable.

18.6. Adjustment

Not applicable.

18.6.1. Seasonal adjustment

Not applicable.


19. Comment Top


Related metadata Top


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