Core Concepts

The following concepts are fundamental to working with CIVITAS/CORE. → Find more concepts in our Glossary

Platform

A Platform is the central environment in which your organization operates.

• Provides a workspace for managing your organization's data and the people who work with it
• Organizes Users, Groups, and Roles
• Contains all data-related elementsData-related elementsA collective term for Datasets, Data structures, Data pools and Data sources. within your organization
• Controls access across different scopes

Data pool

A Data poolData poolA governed, centralized collection of Datasets that are managed together within the Platform. It provides a shared place to organize, discover, and access data, including associated metadata, ownership, and access permissions. With Data pools users can cluster their Datasets according to their organizational structure (e.g., by Departments, Offices). provides a shared context for ownership, access management, and Data sourceData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. availability across multiple DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions..

• Organizes related DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions.
• Provides an additional scope for access management
• Controls Data sourceData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. availability for DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions.
• Supports shared ownership and governance
• Assigning a DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. to a Data poolData poolA governed, centralized collection of Datasets that are managed together within the Platform. It provides a shared place to organize, discover, and access data, including associated metadata, ownership, and access permissions. With Data pools users can cluster their Datasets according to their organizational structure (e.g., by Departments, Offices). is optional but recommended

Dataset

A DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. is the central data-related element where data is prepared and made available.

• Organizes Data structures, Pipelines, APIs, and access permissions
• Contains one or more Pipelines that process data
• Makes DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. Payload available through one or more APIs
• Includes Status lifecycle management

Data source

A Data sourceData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network. represents the origin of data, such as databases, APIs, files, or data streams.

• Connects external or internal data to the Platform
• Uses a Data structure to define how the data is interpreted
• Includes access permissions and Status lifecycle management

Data structure

A Data structure defines the schema of your data.

• Describes Classes, Attributes, and Relationships
• Defines how data is organized
• Is independent, reusable, and versioned
• Includes access permissions and Status lifecycle management

Pipeline

A Pipeline defines how data is ingested, processed, and prepared within a DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions..

• Runs within a DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions.
• Loads data from one or more Data sourcesData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network.
• Uses Data structures and Mappings to transform data
• Stores processed data
• Produces DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. Payload that can be accessed through APIs

API

An API provides access to the DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. Payload.

• Belongs to a DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions.
• Provides the DatasetDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions. Payload in a defined format
• Can be configured for different use cases
• Can be protected through access permissions or made publicly available using Open Data

Standard roles in CIVITAS/CORE

CIVITAS/CORE is used by different Roles, each with specific responsibilities in managing and governing data:

• TenantTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform. Admin: Manages Users, Groups, and access at Platform level
• Data Architect: Defines Data structures and technical setups
• Data Steward: Maintains Data structures, Data sourcesData sourceA data-related element that represents the origin of data. It defines how data is connected, accessed, and ingested into the Platform, such as an external database or sensor network., DatasetsDatasetA data-related element that contains processed data and makes it available for consumption. A Dataset is populated via Pipelines and carries Metadata and access permissions., and Pipelines
• Data Owner: Is responsible for data and approves its availability
• Data Gatekeeper: Reviews and releases data for use

Detailed descriptions of each role are provided in the Role Guides section.