---
title: "Data Catalog Glossary"
slug: "catalog-glossary-v1"
updated: 2024-08-15T09:33:06Z
published: 2024-08-15T09:33:06Z
canonical: "documents.trocco.io/catalog-glossary-v1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documents.trocco.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Data Catalog Glossary

## summary

This page provides definitions of each term in TROCCO's Data Catalog.

## datastore

**A Data Store is** the unit that manages [assets](/docs/en/catalog-glossary-v1#%E3%82%A2%E3%82%BB%E3%83%83%E3%83%88) in TROCCO's Data Catalog. Data Catalog can manage two types of data stores: BigQuery and Snowflake. Data Catalog [automatically pulls in assets for](/docs/automatic-assets-update-v1) each federated data store.

For more information on how to link data stores, see [Data Store Linkage Management](/docs/datastore-integrations-v1).

### Asset List

The **asset list** refers to the hierarchically structured group of data displayed on the left side of the [table information](/docs/table-information-v1) screen. Individual [assets are](/docs/en/catalog-glossary-v1#%E3%82%A2%E3%82%BB%E3%83%83%E3%83%88) stored under the Asset List.

### Data Catalog Manager

The **Data Catalog administrator** is the user who first linked the respective data store. TROCCO's Data Catalog retrieves [assets](/docs/en/catalog-glossary-v1#%E3%82%A2%E3%82%BB%E3%83%83%E3%83%88) using the credentials of the account used by **the Data Catalog administrator** when linking data stores.

## asset

An **asset is** each element stored under the [asset list](/docs/en/catalog-glossary-v1#%E3%82%A2%E3%82%BB%E3%83%83%E3%83%88%E4%B8%80%E8%A6%A7). The data is stored in a manner consistent with the hierarchical structure of each data store. Specifically, the following are defined as assets, which are stored in the asset list in a hierarchical structure from top to bottom. (The former is BigQuery and the latter is Snowflake.)

- Projects / Databases
- Dataset / Schema
- table
- column (esp. in chemistry, file, equipment, etc.)

## metadata

**Metadata** refers to the related data associated with each table column. [Column references and](/docs/column-reference-v1)[column linage are also](/docs/table-information-v1#%E3%82%AB%E3%83%A9%E3%83%A0%E3%83%AA%E3%83%8D%E3%83%BC%E3%82%B8) treated as a type of metadata.

#### Viewing and Editing Metadata

Data Catalog users can view and edit all [assets](/docs/en/catalog-glossary-v1#%E3%82%A2%E3%82%BB%E3%83%83%E3%83%88) under the data store linked to their account, as well as all metadata associated with tables and columns.

### column reference

**A column reference** refers to the correspondence between columns. Tables with Column Setting can be [JOINed to each other in the ER Diagram](/docs/erd-and-join-v1). For information on how to define a column reference, see [Manual Column Setting](/docs/table-information-v1#%E3%82%AB%E3%83%A9%E3%83%A0%E5%8F%82%E7%85%A7%E3%81%AE%E6%89%8B%E5%8B%95%E5%AE%9A%E7%BE%A9).

### logical name

**A logical name is** an alias-like concept defined for [an asset](/docs/en/catalog-glossary-v1#%E3%82%A2%E3%82%BB%E3%83%83%E3%83%88). Defining logical names serves to make it easier to identify assets. Logical names appear at various points in the Data Catalog.

              where logical name is displayed

              

- Right next to the asset name in the **table information**
- Right next to the asset name in the **search results**
- List of assets for **table information** and **ER diagrams**
- Value of logical name column in **column information**
- Directly below the column name **in the preview**
- Directly below the table name in **the ER diagram**
- Within **Query Editor's** input completion function

              Value treated as logical name

              

- **If the** logical name of the [basic metadata](/docs/en/table-information-v1#1-%E5%9F%BA%E6%9C%AC%E3%83%A1%E3%82%BF%E3%83%87%E3%83%BC%E3%82%BF)**is entered**
  - The logical name of the basic metadata is treated as the logical name.
- **If the** logical name of the [basic metadata](/docs/en/table-information-v1#1-%E5%9F%BA%E6%9C%AC%E3%83%A1%E3%82%BF%E3%83%87%E3%83%BC%E3%82%BF) is **not entered**
  - For assets containing [metadata about the](/docs/automatic-metadata-fetched-v1#%E3%83%87%E3%83%BC%E3%82%BF%E3%82%BD%E3%83%BC%E3%82%B9%E3%81%AB%E9%96%A2%E3%81%99%E3%82%8B%E3%83%A1%E3%82%BF%E3%83%87%E3%83%BC%E3%82%BF) following [data sources](/docs/automatic-metadata-fetched-v1#%E3%83%87%E3%83%BC%E3%82%BF%E3%82%BD%E3%83%BC%E3%82%B9%E3%81%AB%E9%96%A2%E3%81%99%E3%82%8B%E3%83%A1%E3%82%BF%E3%83%87%E3%83%BC%E3%82%BF), the values of the following fields are treated as logical names
  - For assets that do not contain [metadata about the](/docs/automatic-metadata-fetched-v1#%E3%83%87%E3%83%BC%E3%82%BF%E3%82%BD%E3%83%BC%E3%82%B9%E3%81%AB%E9%96%A2%E3%81%99%E3%82%8B%E3%83%A1%E3%82%BF%E3%83%87%E3%83%BC%E3%82%BF) following [data sources](/docs/automatic-metadata-fetched-v1#%E3%83%87%E3%83%BC%E3%82%BF%E3%82%BD%E3%83%BC%E3%82%B9%E3%81%AB%E9%96%A2%E3%81%99%E3%82%8B%E3%83%A1%E3%82%BF%E3%83%87%E3%83%BC%E3%82%BF), the logical name is NULL.

| Data Source Name | Field name (table) | Field name (column) |
| --- | --- | --- |
| Metadata about kintone | App Name | Field Name |
| Metadata about Salesforce | Label (singular system) | Japanese column name |
| Metadata about Yahoo! Search Ads | - | Japanese display name |

## live data

**Real data** refers to any of the following values

- Actual value stored in table
- Various data generated by executing queries against the table

              Examples of various data treated as real data

              

- Summary statistics and data preview of [column information](/docs/table-information-v1#%E3%82%AB%E3%83%A9%E3%83%A0%E6%83%85%E5%A0%B1)
- [preview](/docs/table-information-v1#%E3%83%97%E3%83%AC%E3%83%93%E3%83%A5%E3%83%BC)
- JOIN key for JOIN [analysis](/docs/erd-and-join-v1#join%E5%88%86%E6%9E%90), number of rows tied to Venn diagram, tables generated
- Query [Editor](/docs/query-editor-v1) Query Execution Results

              Query execution and billing

              

**Various types of data that are treated as real data** are displayed by executing queries on the [data store managed by the customer](/docs/about-data-catalog-v1#%E5%AF%BE%E5%BF%9C%E3%83%87%E3%83%BC%E3%82%BF%E3%82%B9%E3%83%88%E3%82%A2). Therefore, **you will be charged for your data store based on the size of the query execution**. Please understand that we are not responsible for any loss or damage to your property.

              Sampling when using BigQuery data store

              

If you are using BigQuery's data store, we **will run the query after sampling the data** if the amount charged per query exceeds **10 yen** ( **approximately 15.5 GB in** file size).

### Viewing Actual Data

**The viewing rights to the actual data are managed by the data store managed by the customer, not by the Data Catalog. ** This is because the real data is generated by executing queries on the [data store managed by the customer](/docs/about-data-catalog-v1#%E5%AF%BE%E5%BF%9C%E3%83%87%E3%83%BC%E3%82%BF%E3%82%B9%E3%83%88%E3%82%A2). Therefore, if the account used for data store linking does not have the authority to execute queries on the tables in the data store managed by the customer, the actual data cannot be viewed. In this case, please ask the person who manages the data store to grant permissions to the table you wish to browse.