'Dublin' statistics (migr_dub)

National Reference Metadata in Single Integrated Metadata Structure (SIMS)

Compiling agency: Ministry of Interior of the Slovak Republic, Migration Office


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 Interior of the Slovak Republic, Migration Office

1.2. Contact organisation unit

Dublin Unit

1.5. Contact mail address

Pivonkova 6, 812 72 Bratislava


2. Metadata update Top
2.1. Metadata last certified 15/06/2023
2.2. Metadata last posted 15/06/2023
2.3. Metadata last update 15/06/2023


3. Statistical presentation Top
3.1. Data description

This metadata information is provided by the authorities of the Slovak Republic 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

In 2010 a new information system on migration and international protection (hereinafter referred to as "MIGRA IS") was developed in order to improve the quality of information on illegal migration and asylum procedures and thereby providing statistical information at the national and European levels and helping to boost analytical processes. The project was carried out between 2009-2010 with the use of EU funds. It is a joint system of the Migration Office of the Ministry of Interior (MO) and Bureau of Border and Alien Police of the Presidium of the Police Forces (BBAP). The system was launched in 2010.

MIGRA IS is the basic source of information concerning asylum procedures in the Slovak Republic, which are used to produce statistical outputs on the national and European levels.

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
Decision on request Total, Positive decision, Negative decision, Unknown Total, Positive decision, Negative decision,
Legal provision (Dublin criteria) Please consult the latest Technical Guidelines documentation (in Annex) Latest Technical Guidelines documentation
Duration of transfer Total, From 1 to 6 months, From 7 to 12 months, From 13 to 18 months 6 months, 12 months, 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
Sex Total, Males, Females, Unknown Total, Female, Male
Applicant Total, Adult, Unaccompanied minor, Accompanied minor, Unknown Total, Adult, Unaccompanied minor
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 Outgoing /incoming request 

None

Re-examination request It means a further request to take back/charge of an applicant following the receipt of a negative reply on the original request to the same Member State

None

Request based on Eurodac Outgoing / incoming request based on a Eurodac hit  None
Transfer Incoming / outgoing transfer effectively carried out  None
Responsibility by default (Art. 3.2 First paragraph): no prior criteria applicable When an applicant applies for international protection  and there cannot identify the responsible Member State on the basis of one of the responsibility criteria None

Responsibility by default (Art. 3.2 Second and third paragraph): no transfer When the transfer is impossible to be carried out because there are substantial grounds for believing that there are systemic flows in the asylum procedures and in the receptions conditions. None
Responsibility by default (Art. 29.2): transfer not implemented Transfers that cannot be implemented (whatever the reason), shifting of responsibility as result of non-implementation of the transfer None

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

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), who apply for asylum under the scope of Dublin Regulation.

3.7. Reference area

Slovak Republic.

3.8. Coverage - Time

Since 2008.

3.9. Base period

Not applicable.


4. Unit of measure Top

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.

The reporting unit convention of the Dublin statistics follows two main principles:

1. Each person is to be reported individually i.e. in case a request/re-examination request/decision covers several family members each family member shall be reported individually 

2. Each submitted or received request/re-examination request/decision and transfer concerning the same person during the same reference year shall be reported.This implies that one person can be reported more than once during the reference year by the same Member State in the same dataset.


5. Reference Period Top

2022 Calendar year.


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

EU level  - Regulation (EU) No 604/2013 of the European Parliament and of the Council of 26 June 2013 establishing the criteria and mechanisms for determining the Member State responsible for examining an application for international protection lodged in one of the Member States by a third-country national or a stateless person (recast)

Ministry level – Internal Regulation related to Organisational structure

6.2. Institutional Mandate - data sharing

Not applicable.


7. Confidentiality Top
7.1. Confidentiality - policy

See below.

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

Not applicable.

8.2. Release calendar access

Not applicable.

8.3. Release policy - user access

Not applicable.


9. Frequency of dissemination Top

Annual


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

Not available.

10.2. Dissemination format - Publications

Not available.

10.3. Dissemination format - online database

Not applicable.

10.3.1. Data tables - consultations

Not available.

10.4. Dissemination format - microdata access

Not available.

10.5. Dissemination format - other

Not available.

10.5.1. Metadata - consultations

Not applicable.

10.6. Documentation on methodology

Not available.

10.6.1. Metadata completeness - rate

Not applicable.

10.7. Quality management - documentation

Not available.


11. Quality management Top
11.1. Quality assurance

MIGRA IS is a joint information system of Migration office (MO) and Bureau of Border and Alien Police of the Presidium of the Police Forces (BBAP), which integrates all data concerning illegal migration and international protection into one single information system.

BBAP is in charge of giving permission to entry the personal information and data about an alien. The initial information recorded by BBAP is also available to MO.

Dublin Unit and Procedural department as departments of MO, are entitled to make changes concerning personal information (date of birth, citizenship, nationality). Procedural department is entitled to conduct asylum procedure. Dublin Unit is entitled to conduct Dublin procedure. Procedural department and Dublin Unit are responsible for correctness, quality, accuracy and complexity of input data.

The Organisational and Legal department and Procedural department of MO are entitled to enter the applicants data regarding the appeal process (before a court).

MO employees dealing with asylum statistics are the only people entitled to provide the asylum data to the third parties. All newcomers at MO (new users) are instructed and trained how to work with MIGRA IS. MO has a technical (user's) guideline to MIGRA IS, which includes comprehensive description of particular working procedures within the MIGRA IS information system.

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

Sufficient

In our legislation we do not issue decisions in cases according to Art. 17.1 or 3.2 paragraphs 1st/2nd/3rd

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 : The main users of Dublin statistics are Eurostat and EUAA. The statistics are used in several publications of the Commission, as well as in the preparation of regular reports, policy proposals and analysis. The statistics also provide an input to the EMN studies and reports that address specific issues of current policy importance.

 

Unmet user needs (on statistics) and reasons why these needs cannot be satisfied (at national and international level) : Not available.

12.2. Relevance - User Satisfaction

Not available.

12.3. Completeness

See below.

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

We proceed exactly according to the Technical Guidelines for Dublin statistics and in case of discrepancies and doubts, we resolve the case by individual assessment (on bilateral level).

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

Not applicable.

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  The same day In case of  weekend  or holliday it is next working day
An incoming decision from a partner country accepting the request to take back/charge a person  The same day In case of  weekend  or holliday it is next working day
A decision made by the national authority to accept or to reject a request from a partner country to take charge/back a person  The same day  
13.3.2. Measurement error

See concept 13.3.4 Processing Error.

13.3.3. Non response error

Not available.

13.3.3.1. Unit non-response - rate

Not available.

13.3.3.2. Item non-response - rate

Not available.

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 :  60 days

 

- Reasons for possible long production of the first/preliminary data and plans to improve the situation : double - checking provided data in system and comparing the data with other available sources of data due to absence of relevant information system.

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 : within 75 days 

 

- Reasons for possible long production of the final data and plans to improve the situation : double - checking provided data in system and comparing the data with other available sources of data due to absence of relevant information system. Plans to improve the situation as following:  update of the functionality of MIGRA IS.

14.2. Punctuality

15 days before deadline for delivery.

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

Not applicable.

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

If it is TB articles then is report the sent (for example 18.1.b) article and accepted article (for example 18.1.d) separate. If it is TCH articles then is report the cent article and accepted article separate.

But when Member State X sends a take back request to Member State Y, based on Art. 18.1.b. Member State Y, after undertaking the necessary checks, concludes that the person did not apply for asylum on its territory before (therefore it cannot accept the take back request), but instead it has entered its territory irregularly. Therefore, Member State Y accepts to take charge of that person, based on Art. 13(1). In such cases, both submitting and receiving countries may need to revise their initially reported data on requests accordingly (by subtracting that request from Art. 18.1.b and reporting it under Art. 13(1) instead).

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)?  Yes  
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?  The same day  
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.

 Yes

We do not have legal decision for these cases

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  

Incoming transfer that is pending to be carried out from the reporting country to any partner country at the end of the reference year.

It will cover any person whose transfer was accepted by the partner country, but still not effectively carried out by the reporting country within the time limits of Article 29.2

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

Outgoing transfer that is pending to be carried out from the reporting country to any partner country at the end of the reference year.

It will cover any person whose transfer was accepted by the partner country, but still not effectively carried out by the reporting country within the time limits of Article 29.2

15.2. Comparability - over time

Slovak Dublin Unit process the statistics according to relevant Technical Guideline therefore since 2014 the Dublin statistics are comparable.

15.2.1. Length of comparable time series

2014-2022

15.3. Coherence - cross domain

Not available.

15.3.1. Coherence - sub annual and annual statistics

Not available.

15.3.2. Coherence - National Accounts

Not applicable.

15.4. Coherence - internal

Not available.


16. Cost and Burden Top

Not available.


17. Data revision Top
17.1. Data revision - policy

The Dublin Unit carries out the revision policy in line with the Technical Guidelines for Data Collection under Art. 4.4 of Regulation 862/2007 "Dublin Statistics" - v. 3.1, January 2022: 

Member States must apply the initial validation checks of the Dublin statistics before providing data to Eurostat. These validation checks shall ensure the internal consistency of the datasets at the level of each aggregation, consistency of data between relevant tables as well as consistency of the data between different reporting periods.

The contain validation is meant to check the value inside of the file and eventually to make comparison with historical data (credibility checks).

A common issue triggered by ConVal is the detection of the errors in total consistency present in the file. It is expected that an aggregate (a total) to be consistent with its components. For example, the EU Aggregate is expected to reflect the sum of all EU Member States, else an error is triggered.

17.1.1. Description of the national revision policy for Dublin statistics

Not applicable.

17.1.2. Number of revisions planned on average
Data revision practice National practice  Further details (if necessary)
Average number of planned revisions perfomed during a year (for latest reference year) Annually  
Average number of unplanned revisions performed during a year (usually caused by the discovery of a mistake) Only in case of discovered mistake  
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  Human failure  
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

Human/manual errors in the system. Invalid data formats or empty strings. 

17.2. Data revision - practice

Not applicable.

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

MIGRA IS national database.

18.2. Frequency of data collection

Frequency of the data collection is continuous.

18.3. Data collection

The data are entered into MIGRA IS either manually (by filling in the predefined items - personal information, information about the case) or electronically (uploading the pictures, copies of ID/travel/other documents).

The data are extracted from MIGRA IS´s Eurostat report (which are not actual due to last version of the system from 2010). They are checked and entered manually in the Excel and Excel templates provided by Eurostat and transformed into csv. format. Finally, the csv. files are transferred via Edamis to Eurostat.

18.4. Data validation

The Migration Office in cooperation with Bureau of Border and Alien Police of the Presidium of the Police Forces directly performs regular second level checks of all data inputs into the system in terms of correctness, accuracy and complexity of input data. Logical checks of statistical outputs from this system are performed. There are checks of data uploaded to MIGRA IS at the national level being done in the end of the reference period or in meantime.

Functionality and accuracy of statistical outputs from MIGRA IS are monitored continuously. The checks of the data are aimed to eliminate all registered defects made during the data uploading for specific time. Defects are identified and corrected individually.

Data from the system are checked with the data provided in physical registry diary.

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

Data are collected from one institution - Dublin Unit of the Migration Office of the Ministry of the Interior of the Slovak Republic where all data examined and processes before transmitted to Eurostat.

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