'Dublin' statistics (migr_dub)

National Reference Metadata in Single Integrated Metadata Structure (SIMS)

Compiling agency: National Statistics 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

National Statistics Office

1.2. Contact organisation unit

Population and Migration Statistics 

1.5. Contact mail address

National Statistics Office

Lascaris

Valletta VLT 2000

Malta


2. Metadata update Top
2.1. Metadata last certified 25/11/2022
2.2. Metadata last posted 25/11/2022
2.3. Metadata last update 09/12/2022


3. Statistical presentation Top
3.1. Data description

The data within this domain is provided by the authorities of Malta 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

Dublin Statistics have been collected and published in line with requirements stipulated within Regulation (EC) No. 862/2007, amended by Regulation (EC) No. 851/2020 as from reference year 2008. As of reference year 2018, the Dublin Unit within the International Protection Agency is the national unit responsible for operating the Dublin procedure and, in turn, is the source for data reported to Eurostat. 

3.2. Classification system

Classification system applied is that specified by Eurostat within the guidelines unless otherwise indicated in section 3.2.1.

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 breakdown
Decision on request Total, Positive decision, Negative decision, Unknown   Same as Eurostat breakdown
Legal provision (Dublin criteria) Please consult the latest Technical Guidelines documentation (in Annex)   Same as Eurostat breakdown
Duration of transfer Total, From 1 to 6 months, From 7 to 12 months, From 13 to 18 months   Same as Eurostat breakdown
Duration of response to a request for information Total, 5 weeks or less, Over 5 weeks, Unknown   Same as Eurostat breakdown
Sex Total, Males, Females, Unknown   Same as Eurostat breakdown
Applicant Total, Adult, Unaccompanied minor, Accompanied minor, Unknown   Same as Eurostat breakdown
3.3. Coverage - sector

Migration and international protection – Dublin statistics

3.4. Statistical concepts and definitions

Statistical concepts and definitions applied are those specified by Eurostat within the guidelines unless otherwise indicated in section 3.4.1.

3.4.1. Definitions and discrepancies
Concept / Variable Definition at national level Discrepancy from Eurostat definition
Request A request to take back/charge of an asylum applicant sent from a Member State.  No discrepancy
Re-examination request A further request to take back/charge of an applicant following the receipt of a negative reply on the original request to the same MS and has to be made within three weeks following the receipt of the negative reply. No discrepancy
Request based on Eurodac A request based on a Eurodac hit to take back/charge of an asylum applicant sent from a Member State and also includes family members below 14 who are not fingerprinted themselves. No discrepancy
Transfer A successful transfer where the receiving country has effectively received the person on its territory. A transfer is also considered successful if the applicant otherwise travelled back to the Member State responsible on its own within the transfer time limits, without the national authorities organising the actual transfer.   No discrepancy
Responsibility by default (Art. 3.2 First paragraph): no prior criteria applicable It covers any applicant for which either no request was sent to other countries because no Dublin criteria applied at the first place, or if a request was sent it was rejected as it was proved a posteriori that the Dublin criteria did not apply.  No discrepancy
Responsibility by default (Art. 3.2 Second and third paragraph): no transfer This category of unilateral decision will cover all persons who were not transferred to the partner country due to application of Article 3.2 2nd and 3rd paragraph of the Dublin Regulation. No discrepancy
Responsibility by default (Art. 29.2): transfer not implemented This category will cover all transfers that could not be implemented (whatever the reason) within the foreseen time limits. In such case, according to Article 29.2 the reporting country will be responsible to examine the application of that person. No discrepancy
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

Population on which data collected refers to requests, decisions and transfers processed through the Dublin procedure by Dublin Unit in Malta within the reference year. 

3.7. Reference area

Malta.

3.8. Coverage - Time

2008-2021

3.9. Base period

Not applicable.


4. Unit of measure Top

Administrative event depending on data output.


5. Reference Period Top

2021 Calendar year.


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

All work carried out by NSO is regulated by the Malta Statistics Authority Act, 2000: https://nso.gov.mt/national-legislation/.


Dublin Statistics have been collected and published in line with Regulation (EC) No. 862/2007, amended by Regulation (EC) No. 851/2020 as from reference year 2008.

6.2. Institutional Mandate - data sharing

Not applicable.


7. Confidentiality Top
7.1. Confidentiality - policy

All data collected, processed and disseminated by the NSO is done so in terms of the Malta Statistics Authority Act and in line with the provisions of the General Data Protection Regulations allowing for data to be shared for statistical purposes.

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.  Only aggregate tables are collected from the source.

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

Data is collected in terms of the Malta Statistics Authority, in which Part VIII - Use of Records of Public Authorities and protection of collected information stipulates that:

  • All information furnished by any person, undertaking or public authority under this Act shall be used only for the purpose of statistical compilation and analysis.
  • No information obtained in any way under this Act which can be related to an identifiable person or undertaking shall, except with the written consent of that person or undertaking or the personal representative or next-of-kin of that person, if he be deceased, be disseminated, shown or communicated to any person or body except -
    1. for the purposes of a prosecution for an offence under this Act, or
    2. to officers of statistics in the course of their duties under this Act.

Furthermore, all data that is requested and collected is done so in line with the provisions of the General Data Protection Regulations allowing for data to be shared for statistical purposes.

7.2. Confidentiality - data treatment

Not applicable as only total aggregate figure is published therefore small count rules do not apply.


8. Release policy Top
8.1. Release calendar

NSO is a member of the Special Data Dissemination Standards (SDDS) Committee, which sets dissemination standards set by the International Monetary Fund with a view of enhancing the availability of timely and comprehensive statistics in order to support macroeconomic policies.  As a member of the SDDS Committee, NSO satisfies a number of criteria, which also entails the provision of an advanced news release calendar. 

8.2. Release calendar access

NSO news release calendar is available on: http://nso.gov.mt/en/News_Releases/Release_Calendar/Pages/News-Release-Calendar.aspx.

8.3. Release policy - user access

NSO adheres to internal policies directly related to the user's access to statistical data; one of which being a Dissemination Policy. Due to the importance of the area of demographic statistics, it is imperative that statistics are made available to all users, as soon as possible. In some cases, these statistics are provided on provisional basis and are therefore subject to revisions.


9. Frequency of dissemination Top

Annual


10. Accessibility and clarity Top

Data can be downloaded directly via the Eurostat website or users can contact the National Statistics Office.

10.1. Dissemination format - News release

Not applicable.

10.2. Dissemination format - Publications

Not applicable.

10.3. Dissemination format - online database

Detailed information can be downloaded from Eurostat's online database:  http://ec.europa.eu/eurostat/data/database

10.3.1. Data tables - consultations

Not applicable.

10.4. Dissemination format - microdata access

Micro-data is not available.

10.5. Dissemination format - other

Not applicable.

10.5.1. Metadata - consultations

Not applicable.

10.6. Documentation on methodology

NSO follows the methodological recommendations stipulated by Eurostat and the relevant Regulation/Directives in order to ensure harmonisation of results.  NSO also documents all work processes involved in the compilation of these statistics, which are currently available for internal purposes.

10.6.1. Metadata completeness - rate

Not applicable.

10.7. Quality management - documentation

Refer to 10.6


11. Quality management Top
11.1. Quality assurance

Consistency checks on the aggregate data between related tables. Aggregate time-series comparisons are conducted to outline any trends which may need to be reviewed and validated with the source.  

11.2. Quality management - assessment

Statistics within the domain are assessed to be of 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, amended by Regulation (EC) No. 851/2020 are used by a wide range of users at national, European and International level to cover various usersʼ needs. 

 

Users of Dublin statistics : Users of Dublin statistics include the European Migration Network (EMN), UNHCR, national entities, press, students and researchers. 

 

Unmet user needs (on statistics) and reasons why these needs cannot be satisfied (at national and international level) : Currently, all requirements stipulated by the regulation, are being met.

12.2. Relevance - User Satisfaction

Not available.

12.3. Completeness

All requirements stipulated by the relevant regulation are being fulfilled.

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

Derogation on breakdown by sex applies up until reference year 2022.

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

Overall accuracy for the domain is said to be high.

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

See below.

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

 None

 

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

 None

 

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

 None

 

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

 None

 

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

 None

 

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

 None

 

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

 None

 

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

 None

 

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

 None

 

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

 None

 

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

 None

 

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

 None

 

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

 None

 

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

 None

 

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

 None

 

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

 None

 

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

 None

 

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

 None

 

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

 None

 

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  Less than 1 day Event is registered upon receiving the request. 
An incoming decision from a partner country accepting the request to take back/charge a person  Less than 1 day Event is registered upon receiving the notification that the decision has been taken.
A decision made by the national authority to accept or to reject a request from a partner country to take charge/back a person  Less than 1 day Event is registered upon receiving the notification that the decision has been taken.
13.3.2. Measurement error

Not applicable.

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

Such errors may be possible due to human error but are likely negligible. 

13.3.5. Model assumption error

Not applicable.


14. Timeliness and punctuality Top
14.1. Timeliness

Deadline stipulated by the regulation has generally always been met.

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

 

- Reasons for possible long production of the first/preliminary data and plans to improve the situation : Not applicable. Data provided within the deadline. 

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

 

- Reasons for possible long production of the final data and plans to improve the situation : Not applicable. Data provided within the deadline. 

14.2. Punctuality

Minimal delay in provision of data. Data is provided within the deadline. 

14.2.1. Punctuality - delivery and publication

Not applicable.


15. Coherence and comparability Top
15.1. Comparability - geographical

Data provided follows all Eurostat guidelines.  Data covers entire geographic territory for Malta.

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 Data is based on requests/decision/transfer and not persons.
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 Information on name, gender and date of birth are available.
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)? 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)? No Age in any subsequent events remains as was recorded in the first administrative event registered in the system.
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.

Yes

 The data does not include accompanied children.

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? 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

Data is compiled in line with Regulation (EC) No. 862/2007, amended by Regulation (EC) No. 851/2020 and therefore the time-series is considered comparable over time.

15.2.1. Length of comparable time series

2008-2021

15.3. Coherence - cross domain

Coherence checks across domains are not possible as no other sources or outputs capture the data related to Dublin. 

15.3.1. Coherence - sub annual and annual statistics

Only annual figures provided.

15.3.2. Coherence - National Accounts

Not applicable.

15.4. Coherence - internal

Figures are compared with previous years data and any fluctuations are discussed with the source. Coherence checks across other sources are not possible as no other sources or outputs capture the data related to Dublin.


16. Cost and Burden Top

Dublin data tables are numerous and complex requiring a comprehensive understanding of the Dublin legislation and system to complete.  The Dublin Unit, which provides the data, has limited human resources and therefore, despite the data collection only occurring once a year, still constitutes a considerable workload on the national authorities involved.


17. Data revision Top
17.1. Data revision - policy

The manner with which figures are revised, if necessary, follows the guidelines of the European Statistics Code of Practice (https://nso.gov.mt/code-of-practice/) and Regulation (EC) No. 862/2007.

17.1.1. Description of the national revision policy for Dublin statistics

The manner with which figures are revised, if necessary, follows the guidelines of the European Statistics Code of Practice (https://nso.gov.mt/en/nso/About_NSO/Documents/Code_of_Practice/Code_of_Practice_November_2017.pdf) and Regulation (EC) No. 862/2007.

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)  None Any revisions are conducted on an ad-hoc basis when it is deemed necessary.
Average number of unplanned revisions performed during a year (usually caused by the discovery of a mistake)  Ad-hoc, if deemed necessary.  
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 Revisions are conducted when required if new data sources or methods are indicated to improve the accuracy and/or quality of data.  
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?

 No  
17.1.3. Description of the main reasons for revisions

Following the identification of errors, change in policy and the identification of new sources revisions may be undertaken.

17.2. Data revision - practice

Revisions are conducted on an ad-hoc basis, when required, if new data sources or methods are said to improve the accuracy and/or quality of data.

17.2.1. Data revision - average size

Not applicable.


18. Statistical processing Top
18.1. Source data

Dublin Unit, International Protection Agency 

18.2. Frequency of data collection

Annual.

18.3. Data collection

Data is collected from the Dublin Unit within the International Protection Agency. The data is provided in tables required to satisfy Regulation (EU) No. 862/2007 amended by Regulation (EU) 851/2020.

18.4. Data validation

Aggregate data tables are requested from the Dublin Unit within the International Protection Agency. Validation checks are therefore conducted on aggregate data and queries are made to the source if required.

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

Complete aggregate tables are provided by the source and compiled through their administrative records.

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