Data Consumer

Role overview

note

Your mission: You access and use available data. Your goal is to find, understand, and consume 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..

Why your role is vital: You are the "User of data". The value of the Platform is realized when data is actually used.

Defining your scope: You access the Payload of available 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. through their APIs.

Your core responsibilities

• Understand data: You review metadata and structure to understand the data
• Consume data: You use one or more APIs of 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 retrieve and use its Payload

Outside your scope

It is not your responsibility to create, configure, or manage data-related elementsData-related elementsA collective term for Datasets, Data structures, Data pools and Data sources.. You do not modify 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., Data structures, or 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..

If you prepare or manage 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., the Data Steward role is likely the right role for you.

If you define structures or integrate data, the Data Architect role is likely the right role for you.

If you review or release data, the Data Owner or Data Gatekeeper role is likely the right role for you.

Understanding the Authorization Logic

To access data, you need the appropriate permissions.

The access logic: Access is always the result of a User being assigned to a Group, and that Group being assigned a Role at a specific Scope.

As a Data Consumer, your access is typically limited to the API of specific 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.. If 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 configured as open data, it may also be accessible without authentication.

→ Deep Dive Authorisation

Typical tasks

Your work in CIVITAS/CORE focuses on using data:

• Browse 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.: Browse and select 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.
• Select an API: Locate the API URL
• Copy the API URL: Use the copy icon
• Retrieve 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: Use the API in your tool of choice

Your permissions

Permissions / Data-related elementsData-related elementsA collective term for Datasets, Data structures, Data pools and Data sources.	READ	CREATE	UPDATE	DELETE	RELEASE
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	🟣
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.
Data structure
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).	🟣

Key terms to know

To work effectively as a Data Consumer, review these terms in our Glossary:

• 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.: A structured collection of data prepared for use.
• API: The interface used to access data.
• Payload: The data provided by 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. through one or more APIs.

Deep Dives

→ Glossary

→ Consume Data