EN-TRACK and DEEP mapping to BEDES

The current document provides a summary of the work for mapping the EN-TRACK data model to the BEDES specification of common terms and to the DEEP database fields. The work has been done within the task of standardisation of data and interoperability assuring of EN-TRACK.

The document describes the approach and procedures followed in the process of mapping and provides some examples of this in the text. The initial mapping files have been uploaded in the open repository Zenodo and links to them have been provided in the document.

The mapping to BEDES has required considerable effort both in terms of gaining sufficient familiarisation with the BEDES terminology and its mapping procedures, and also in consultation and collaboration with the BEDES developing team. The work has revealed some limitations for the full mapping of the EN-TRACK data model to BEDES. These relate to a lack of capability of BEDES to describe the structure of data, and insufficient expressive power to describe timeseries data and taxonomies, among others. Consequently, the pragmatic solution has been to develop a partial mapping document and to reconsider the initial idea of mapping the full EN-TRACK model. This reconsideration, in collaboration with the BEDES team, has led to the idea of a more targeted mapping, focusing particularly on the fields necessary for data exchange and omitting the mapping of the internal fields. Despite the limited scope, the initial mapping was considered very beneficial for facilitating future data exchange between BEDES compliant applications and European tools. The work will continue with the objective to achieve official BEDES compliance.

The mapping to DEEP has been successfully completed in first version and has been achieved without substantial difficulties due to the early alignment during the design of the EN-TRACK data model. This first version provides a sufficiently solid base for implementation of data exchange between both platforms. The mapping will be reviewed and updated towards the end of the EN-TRACK project in the light of any possible changes that might be made in the EN-TRACK model during the implementation and testing, as any changes that might be made in DEEP during the same period.