Skip to main content

EPOS Data Model

The EPOS Data Model defines the fundamental structure of information managed and presented by the EPOS Platform. It serves as a crucial guideline for defining the inputs and outputs of various system components and ensures consistency across all data interactions. Understanding this model is key to comprehending how data is organized and utilized within the EPOS ecosystem.

Data Model Diagram

The following class diagram provides a comprehensive overview of the EPOS Data Model, illustrating the key entities and their relationships.

EPOS Data Model Overview

Core Concepts

The EPOS Data Model is built around several core concepts, each represented as a class in the diagram above:

  • DataProduct: Represents the fundamental unit of scientific data within the EPOS ecosystem. It includes metadata such as title, description, identifier, and version.
  • Distribution: Describes how a DataProduct can be accessed, including its format, license, and access URLs. A DataProduct can have multiple Distributions.
  • WebService: Represents a web service that provides access to DataProducts. It includes information about its endpoint, documentation, and supported operations.
  • Operation: Defines a specific action or query that can be performed on a WebService.
  • Mapping: Describes how data fields from an Operation are mapped to the EPOS Data Model.
  • Person: Represents individuals involved in the EPOS ecosystem, such as authors, contact points, or data providers.
  • Organization: Represents institutions or groups associated with data products, services, or facilities.
  • Facility: Describes a research facility or infrastructure.
  • Equipment: Represents scientific equipment used in data collection.
  • Service: A generic representation of a service provided by an Organization.
  • Software: Describes software components related to data processing or analysis.
  • Publication: Represents scientific publications associated with data products.

Usage within the EPOS Platform

The EPOS Data Model is central to the platform's functionality:

  • Metadata Ingestion: All metadata ingested into the platform (e.g., via .ttl files) must conform to this data model.
  • Data Discovery: The EPOS Platform GUI uses this model to enable comprehensive search and filtering of available data products and services.
  • Service Integration: The model guides how external web services are integrated and how their data is mapped for consistent presentation.
  • Data Visualization: The structure defined by the model informs how data is visualized in the GUI, ensuring that relevant information is displayed effectively.

Download the Full Data Model

For a more in-depth understanding, you can download the complete EPOS Data Model specification:

Download EPOS Data Model PDF