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

# Browse the catalog

> Find DataX entities by name, source, type, tag, or deployment status.

The Catalog is the inventory of data entities available in your workspace. Use it to find blueprints, transformations, and imported data before you write a query or create a downstream asset.

## Open the catalog

In the K16 Platform navigation, open **Documentation**, then select **Catalog**.

The page has two coordinated views:

* **Source explorer** groups entities by source. Expand a folder, search the tree, or select an entity.
* The catalog table shows the entity's status, type, source, version information, and description.

Selecting an entity in either view opens its detail page.

## Search and filter

Enter part of an entity name in **Filter catalog…**. Add one or more filters to narrow the result set.

| Filter      | Use it to find                                 |
| ----------- | ---------------------------------------------- |
| **Type…**   | Blueprints, transformations, or client imports |
| **Source…** | Entities from one source system                |
| **Tags…**   | Entities with a shared classification          |
| **Status…** | Entities at a specific deployment stage        |

Select **Clear all** to remove the type, source, tag, and status filters. Clear **Filter catalog…** separately if it contains text.

Common status values include:

* **Upgrade Available**: a newer version can replace the live version.
* **In Progress**: DataX is staging or applying a change.
* **Ready to Apply**: a target version is staged.
* **Applied**: the published version is live.
* **Canceled**: a staged change was discarded.

<Tip>
  Start with a source or type filter, then search by name. This works better than scanning a long,
  mixed result set.
</Tip>

## Understand entity types

* A **Blueprint** is a documented SQL definition that produces a reusable entity. Client blueprints can be created and versioned in the K16 Platform.
* A **Transformation** is a managed transformation supplied through the connected DataX environment.
* A **Client Import** is an entity created from uploaded CSV data.

The actions you can take depend on the type. For example, only supported client-managed entities show **Edit**.

## Create a blueprint

If you have blueprint management access, select **New Blueprint**. You can also use the source explorer while creating a blueprint to insert entity and column names into the SQL editor.

See [Create a blueprint](/datax/catalog/create-a-blueprint) for the full workflow.

## When an entity is missing

1. Select **Clear all** and clear the text search.
2. Check the **Source explorer** for the expected source.
3. Confirm that you are in the correct workspace.
4. Ask a workspace administrator whether your role can view the entity.

An access rule can hide an entity entirely. Column-level rules can instead leave the entity visible while masking protected values.

Next, learn how to [review entity details](/datax/catalog/entity-details) or [trace lineage](/datax/catalog/lineage).

## Organize catalog folders

You need blueprint management access to organize editable folders in **Source explorer**.

1. Open a folder's menu under blueprints or imports and select **New folder**.
2. Enter **Name**. Start with a letter or underscore, and use only letters, numbers, underscores, or `$`.
3. Select **Create** and confirm the folder appears beneath the intended parent.

Use **Rename** on a child folder to change its name. **Delete** is unavailable while the folder contains entities. Review the folder name in the confirmation before deleting it.