How To Deliver My Data?

ESPON M4D

Revision History
Revision 2svn rev 2420 build 2014-12-19 17:32:48

Abstract

This technical report proposes a description of the expectations for the integration of different ESPON projects data.


Table of Contents

Introduction
1. The Key Indicators
1.1. Concepts behind the key indicators delivery
1.1.1. Rule 1 – Limited number of indicators
1.1.2. Rule 2 – Innovative indicators
1.1.3. Rule 3 - High level of metadata
1.1.4. Rule 4 - Promote the core database strategy
1.1.5. Rule 5 - A good completeness of the indicator
1.2. Key Indicators Delivery
1.2.1. ESPON Data and Metadata Specifications
1.3. The Data Delivery Process
1.3.1. Automatized Checks
1.3.1.1. Online Checks at Upload
1.3.1.2. Offline Syntactic Check
1.3.2. Semantic check
1.3.3. Quality control
1.3.4. Integration into the database
2. The Case-study delivery
2.1. The Case-study Delivery Strategy
2.2. Expected delivery
2.2.1. Data file
2.2.2. Case-study data and metadata
2.2.2.1. The dataset sheet
2.2.2.2. The indicator sheet
2.2.3. Geometry file (optional)
2.3. What happens to my data? The case-study integration process
3. The Background Data of the Database
3.1. Strategy for the Background Data
3.2. Expected delivery
3.2.1. How structuring the background data .zip file? General recommendations
3.2.2. A .xls template available for filling quickly background metadata
3.3. What happens to my Data?
4. Resources of interest and advices for data creation in ESPON
4.1. Resources of interest
4.1.1. XLS Template with Examples
4.1.2. Frequently Asked Questions (FAQ)
4.1.3. M4D Presentation (ESPON Seminar in Cyprus, December 2012)
4.1.4. M4D Newsletters
4.2. Advice for a perfect management of the data process
4.3. A good practice for filling data and metadata
A. References
B. Data Flow Process of the Key Indicators
B.1. Syntactic Check
B.2. Semantics Check
B.3. Semantic Check Approval
B.4. Outliers Check
B.5. Outliers Check Approval
B.6. ESPON CU Approval
C. About

List of Figures

1. Three possibilities to deliver my data
1.1. Header of the ESPON Data and Metadata Specification
1.2. Excel Data Model for Key indicators
1.3. Example of the Label field description
1.4. Dataset Integration Tracking Details
1.5. Syntactic check: example of an invalid input
1.6. Spatial check: example of invalid spatial units
1.7. Syntactic check: example of a valid input despites warnings
1.8. Indicator code/name/abstract Triplet Conflict
1.9. Access to the executable version of the Syntactic check
1.10. Execute the DatasetCheck.jar
1.11. Example of a Semantic Check Report
1.12. Semantic Check Example: Input Information
1.13. References for a Semantic Check Expertise
1.14. Semantic Check Example: Fixed Information
1.15. Outlier check output
2.1. Overview page of Case Studies
2.2. Information Page of a Case Study
2.3. Data Model Example for Zoom-in projects
2.4. Case Study Dataset Sheet
2.5. Several strategies for locating the flag of a case-study
2.6. Case Study Indicator Sheet
2.7. Example of a Case Study Geometries Input
2.8. Mapping of Geometries Codes in Data
2.9. Case-study dataset file upload page
2.10. Case-study geometry file upload page
2.11. Tracking tool activation and database administrator functions
2.12. Case-study integration
3.1. Background data part of the ESPON Database Portal
3.2. Project Database Metadata Sheet
3.3. Background Data upload
4.1. On-line availability of the xls templates
4.2. Header of the FAQ
4.3. Starting point: a table with empty values
4.4. Resulting dataset with estimated values and associated labels
4.5. Description of the label 1 in the metadata
4.6. Description of the label 13 in the metadata
4.7. Description of the label TE6b in the metadata
B.1. Upload Form
B.2. Tracking Overview: SYNTAX_CHECKED checked
B.3. Semantics check form
B.4. Tracking Overview: SEMANTICS_CHECKED state
B.5. Dataset details: SEMANTICS_CHECKED state
B.6. Form for the semantics check approval
B.7. New state for the dataset: "SEMANTICS_ACCEPTED"
B.8. Outliers check form
B.9. New state for the dataset: OUTLIERS_CHECKED
B.10. Tracking Overview: OUTLIERS_CHECKED state
B.11. Dataset details: OUTLIERS_CHECKED state
B.12. Form for the outliers check approval
B.13. New state of the dataset: OUTLIERS_APPROVED
B.14. Tracking Overview: OUTLIERS_APPROVED state
B.15. Dataset Details: OUTLIERS_CHECKED state
B.16. Tracking - Step 4 - ESPON CU Approval Form
B.17. Tracking - Dataset Details Page After an Integration Attempt