'Dublin' statistics (migr_dub)

National Reference Metadata in Single Integrated Metadata Structure (SIMS)

Compiling agency: Migration and Passport Office Principality of Liechtenstein


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

Migration and Passport Office Principality of Liechtenstein
1.2. Contact organisation unit

Migration and Passport Office Principality of Liechtenstein
1.5. Contact mail address

Städtle 38 / P.O.Box 684 / 9490 Vaduz


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


3. Statistical presentation Top
3.1. Data description

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

Statistics on the application of the Dublin III Regulation for Liechtenstein: Incoming requests, outgoing requests, unilateral decisions, transfers, re-examination of requests, refused requests, accepted requests in time and by default and information-requests.
3.2. Classification system

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

Migration and international protection – Dublin statistics
3.4. Statistical concepts and definitions

See below.
3.4.1. Definitions and discrepancies
Concept / Variable Definition at national level Discrepancy from Eurostat definition
Request Request  No
Re-examination request Re-examination request  No
Request based on Eurodac Request based on Eurodac  No
Transfer Transfer  No
Responsibility by default (Art. 3.2 First paragraph): no prior criteria applicable Responsibility by default (Art. 3.2 First paragraph): no prior criteria applicable  No
Responsibility by default (Art. 3.2 Second and third paragraph): no transfer Responsibility by default (Art. 3.2 Second and third paragraph): no transfer  No
Responsibility by default (Art. 29.2): transfer not implemented Responsibility by default (Art. 29.2): transfer not implemented  No
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

Asylum seekers under the Dublin Regulation.
3.7. Reference area

Liechtenstein.
3.8. Coverage - Time

years 2011-2022.
3.9. Base period

Not applicable.


4. Unit of measure Top

Number of persons.


5. Reference Period Top

Calendar year 2022.


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

National Asylum act : AsylG from 14.12.2022 according art. 72 https://www.gesetze.li/konso/2012.29 

EU act:  Dublin III Regulation 604/2013 according art. 74
6.2. Institutional Mandate - data sharing

Not available.


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 available.
7.1.2. Required confidentiality by law and signed legal confidentiality commitments by survey staff

Data protection law according AsylG Art. 66 ff. https://www.gesetze.li/konso/2012.29
7.1.3. Potential micro-data access for research purposes by external users and confidentiality provisions applied

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

Not available.
7.2. Confidentiality - data treatment

Not available.


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 applicable.
10.2. Dissemination format - Publications

Not available.
10.3. Dissemination format - online database

Not available.
10.3.1. Data tables - consultations

Not applicable.
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 available.
10.7. Quality management - documentation

Not available.


11. Quality management Top
11.1. Quality assurance

Not applicable.
11.2. Quality management - assessment

Not applicable.
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 : Eurostat, UNHCR, Government, Office of statistics Liechtenstein, external institutions 

 

Unmet user needs (on statistics) and reasons why these needs cannot be satisfied (at national and international level) : Not applicable. 
12.2. Relevance - User Satisfaction

Not available.
12.3. Completeness

See below.
12.3.1. Data completeness - rate

99%
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

See below.
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

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 discrepancies 

 

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

 No discrepancies 

 

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

 No discrepancies 

 

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

 No discrepancies 

 

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

 No discrepancies 

 

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

 No discrepancies 

 

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

 No discrepancies 

 

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

 No discrepancies 

 

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

 No discrepancies 

 

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

 No discrepancies 

 

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

 No discrepancies 

 

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

 No discrepancies 

 

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

 No discrepancies 

 

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 discrepancies 

 

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 discrepancies 

 

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

 No discrepancies 

 

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

 No discrepancies 

 

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

 No discrepancies 

 

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

 No discrepancies 

 
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 For the statistics: All data will be registered at the end of the year  For the case management: All data will be registered in electronic file system within 2 working days. 
An incoming decision from a partner country accepting the request to take back/charge a person For the statistics: All data will be registered at the end of the year  For the case management: All data will be registered in electronic file system within 2 working 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 For the statistics: All data will be registered at the end of the year  For the case management: All data will be registered in electronic file system within 2 working 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 applicable.
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 :  30 days

 

- Reasons for possible long production of the first/preliminary data and plans to improve the situation : lack of staff.
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 : 30 days

 

- Reasons for possible long production of the final data and plans to improve the situation : lack of staff.
14.2. Punctuality
Sometimes the punctuality depends on the availability of the responsible workers.  We not have a statistical department, statistics compilation is a secondary task of the case workers.
Task is planned every month.
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?  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?  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)?  Yes  
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)?  Yes  
15.2. Comparability - over time

Comparability over time.
15.2.1. Length of comparable time series

year 2011 - 2022
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 applicable.


17. Data revision Top
17.1. Data revision - policy

Not applicable.
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 performed during a year (for latest reference year)  Not applicable  
Average number of unplanned revisions performed during a year (usually caused by the discovery of a mistake)  Not applicable  
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  Not applicable  
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?

  Not applicable  
17.1.3. Description of the main reasons for revisions

Not applicable.
17.2. Data revision - practice

See below.
17.2.1. Data revision - average size

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


18. Statistical processing Top
18.1. Source data

Asylum applications reference year 2022 - split into Dublin cases. It is our asylum division the producer and the source of data in form of Excel File where the case workers fill in the necessary data case by case. 
18.2. Frequency of data collection

Daily, working week Mo until Fry 
18.3. Data collection

The case workers fill in the data set in Excel data sheet, where all data regarding the Dublin procedure will be inputted.

For the yearly and monthly statistic tables sent to Eurostat, Liechtenstein uses a main Excel File and an electronic file system at national level. Due to the small figures of Asylum seekers (50 - 150 Person a year) we are not using a statistic program and we prepare the files "manually".
18.4. Data validation

At the end of the year we produce the Dublin statistics manually with the main Excel File of the asylum cases and the electronic case/file system. 
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)  Checked   End of the year  Manually
Compare the data with data of previous periods  Not perfomed    
Check for outliers  Yes    
Investigate inconsistencies in the statistics (checking the consistency of "Total" values over each variable)  Yes    
Verify the statistics against expectations and domain intelligence  Not performed    
Confront the data against other relevant data (e.g. Asylum statistics, of the mirror data from the partner countries)  Not performed    
Check retrospectively (a sample of) the data in the register/database in order to confirm they are accurate  Yes    
18.5. Data compilation

At the end of the year we produce the Dublin statistic manually, with the main Excel File of the asylum cases and the electronic case/file system. 
18.5.1. Imputation - rate

Not applicable.
18.6. Adjustment

Yes, manually.
18.6.1. Seasonal adjustment

Not applicable.


19. Comment Top


Related metadata Top


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