# Dataset Management Dataset Management lets you review the object types a source collects and control how the source aggregates those objects into SailPoint. Use Dataset Management to view and manage resource attributes, datasets and their resources, enable dataset aggregation schedules, perform manual aggregation, and view aggregation history. > [!NOTE] > > Datasets are also available in SailPoint Agentic Fabric. Contact your Customer Success team and refer to [SailPoint Agentic Fabric]() for more information. For more information, refer to [Managing Datasets and Resources]() for datasets, resources, owner correlation, and aggregation. ## Datasets A *dataset* is a named group of one or more related resources that the source aggregates together. When aggregation runs for a dataset, the source collects all resources in that dataset from the managed system in one aggregation job. Activate or deactivate aggregation at the dataset level, not for individual resources. > [!NOTE] > > Each resource belongs to exactly one dataset for that source. The source defines which resources belong to each dataset. You can enable aggregation and review associated resources, but you cannot create or delete datasets or move resources between them. ### Dataset Aggregation Configure aggregation on the **Dataset Aggregations** tab for each dataset. Configure each dataset separately. During aggregation, your owner correlation rules are automatically applied to link machine identities to their human owners. For more information, refer to [Configuring Dataset Aggregations](). ## Resources A resource defines an object type from the managed system. It specifies the kind of object, the attributes the source collects, and how the source identifies and displays each object. Resources form the building blocks of the data model. In the UI, each resource appears under **Dataset Management** \> **Resources** with its schema. A resource does not run aggregation by itself. The dataset that owns the resource collects it during aggregation. For more information, refer to [Managing Resources](). ### Owner Correlation Configure owner correlation on each resource to link aggregated objects to human owners. If you do not configure owner correlation, or if the mapping produces no match, an owner is not assigned. For more information, refer to [Configuring Owner Correlation](). ## Supported Datasets Go to **Dataset Management \> Datasets** on your JFrog source to view the datasets the connector aggregates. Select a dataset to review its associated resources and configure aggregation. > [!NOTE] > > Configure aggregation for each dataset separately. For more information, refer to [Dataset Aggregation](). | Dataset name | Associated resources | Dataset ID | | --- | --- | --- | | **Access Tokens** | Access Token | `jfrog:access-tokens` | For schema attribute definitions, refer to [Access Token Attributes](<#access-token-attributes>). ### Dataset Aggregations Dataset aggregation collects resource objects from the managed system and loads them into SailPoint. Repeat the configuration for each dataset on the source. ### Configuring Dataset Aggregation To configure dataset aggregation for a dataset: 1. Go to **Admin \> Connections \> Sources**, and open your source. 2. Go to **Dataset Management \> Datasets**. 3. Select the dataset you want to configure. 4. Select the **Dataset Aggregations** tab. On the **Dataset Aggregations** tab, configure how resource objects from the selected dataset are aggregated into SailPoint. The tab contains **Scheduled Aggregations**, **Manual Aggregation**, and **Latest Aggregation**. #### Scheduled Aggregations Scheduled aggregations run on a schedule to keep the dataset synchronized with the managed system. 1. On the **Dataset Aggregations** tab, select **Enable Schedule** to turn on scheduled aggregations. When scheduled aggregations are enabled, SailPoint aggregates all resource objects in the dataset on the configured schedule. #### Manual Aggregation Manual aggregation runs once and collects all resource objects in the dataset. 1. On the **Dataset Aggregations** tab, select **Start Aggregation**. SailPoint starts the aggregation immediately. When the run completes, results appear in the **Latest Aggregation** section. #### Viewing Aggregation Results After an aggregation completes, review its status in the **Latest Aggregation** section on the **Dataset Aggregations** tab. The **Latest Aggregation** section shows: - **Start Time** - when the aggregation started - **Resource Objects Scanned** - the number of resource objects the aggregation processed - **Status** - whether the aggregation succeeded or failed Select **Details** to view additional information about the most recent run. To view prior runs, select **Aggregation History**. ## Supported Resources For more information, refer to [Managing Resources](). > [!NOTE] > > When you enable dataset aggregation for a selected dataset, all resources in that dataset are collected at once. Activate or deactivate aggregation at the dataset level, not for individual resources. Under **Dataset Management** \> **Resources**, the JFrog source lists each object type that is aggregated. Select a resource to review its schema on the **Schema** tab. | Resource name | Resource type | Resource ID | | --- | --- | --- | | **[Access Token](<#access-token-attributes>)** | `std:credential` | `jfrog:access-token` | Each access token that JFrog returns becomes one credential object. The source identifies the credential by its token ID and displays the description entered in JFrog. > [!NOTE] > > JFrog does not return the token secret, so the source cannot read or store it. Only token metadata is aggregated. ### Owner Correlation On the **Owner Correlation** tab of the **Access Token** resource, map the token to the identity that owns it. By default, the source matches the `username` attribute, parsed from the token subject, to the identity email address. For more information, refer to [Owner Correlation](). ## Access Token Attributes The **Access Token** resource is in the **Access Tokens** dataset. | Field | Value | | --- | --- | | Resource ID | `jfrog:access-token` | | Resource type | `std:credential` | | Identity attribute | `token_id` | | Display attribute | `description` | The following table lists the schema attributes for the Access Token resource: | Attribute Name | Description | | --- | --- | | token\_id | Unique identifier of the access token in JFrog. SailPoint uses this value as the resource ID. | | description | Label entered for the access token in JFrog. SailPoint displays this value as the resource name. | | audience | JFrog services that accept the access token. | | expiry | Date and time when the access token expires, in ISO-8601 UTC format. A value of `0` means that the access token never expires. | | issued\_at | Date and time when the access token was created, in ISO-8601 UTC format. | | issuer | Identifier of the JFrog service that created the access token. | | last\_used | Date and time when the access token was last used, in ISO-8601 UTC format. Absent when the JFrog instance does not track token usage. | | project | Project key, present when a project administrator created the access token. | | refreshable | Indicates whether the access token can be refreshed. | | scope | Access scope granted by the access token. | | subject | Identity the access token is associated with. | | username | JFrog username parsed from a user-token subject. Used for owner correlation to a human identity. |