> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/consume/understand/assets/inputs.md).

# Inputs

Inputs are the source datasets a data product reads from. They tell you where the product starts, which systems or datasets feed it, and what raw fields are available before any transformation.

In `Orders Analytics Platform`, the inputs include external source datasets like `CUSTOMERS_EXT` that feed the curated outputs and semantic models.

## Open an input

From the data product page, open **Assets**, expand **Inputs**, and click an input dataset.

The detail view shows the source name and location, a summary row with **Kind** and **Schedule**, a **Source metadata** toggle, a **View lineage** link, and the **Columns** and **Dependencies** tabs.

![Input detail showing kind, schedule, and the columns tab](/files/QFQTDAQMQ46UxI3podJ6)

## What to review

<table><thead><tr><th width="157.47271728515625">Area</th><th>Why it matters</th></tr></thead><tbody><tr><td>Source name</td><td>Which source system or external table the product depends on. Use it to judge trustworthiness.</td></tr><tr><td>Kind</td><td>Whether the data comes from an external source or another supported input type.</td></tr><tr><td>Schedule</td><td>How current the source data is, based on how often it's read.</td></tr><tr><td>Columns</td><td>Raw fields available before transformation, with Tags and Quality so you can gauge meaning and reliability.</td></tr><tr><td>Dependencies</td><td>What the input feeds. Lets you assess the blast radius of a source change.</td></tr></tbody></table>

## Source fields

Use the columns list to see what raw fields are on offer. `CUSTOMERS_EXT`, for example, lists `customer_id`, `region_id`, `name`, `email`, and `signup_date`.

Inputs often have shorter business descriptions than curated outputs or semantic models. If a field's meaning isn't clear, follow it downstream to see how it's transformed and exposed.

## Dependencies

Open the **Dependencies** tab to see the upstream and downstream models tied to the input. Useful before you query or consume a governed asset, because a source change could ripple through.

![Input dependencies tab showing upstream and downstream models](/files/HqJiC0g81nTLvKqGwRcF)

## Lineage

Click **View lineage** to open the full dependency graph from the source input through curated outputs, semantic models, and metrics. Use it to understand the path a field follows across the data product.

![Lineage graph showing the source input flowing through tables and semantic models to downstream metrics](/files/dc4n9LZ4QoxJL031qYnW)

The graph runs left to right: base input on the left, downstream tables, semantic models, and metrics on the right. Each node shows the model name, domain and tier, and an expandable column count. Use the zoom and fit controls for bigger graphs.

### Column-level lineage

Turn on the **Columns** toggle to expand each node into its individual columns and trace lineage at the column level. This shows how a specific field (`customer_id`, say) flows into and is used by downstream models. Use the search box inside a node to find a column in bigger models.

![Column-level lineage with the Columns toggle on, expanding nodes into their individual columns](/files/ajZ7wmCV6CV5WEDNVWju)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/consume/understand/assets/inputs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.