> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pentaho-data-mastering/sourcing-data/viewing-source-records.md).

# Viewing source records

View source records to review the data elements in the source record or to obtain information for tracing the record. For example, a Data Steward can trace a source record by using the Source Record Table Key and a Source Application Identifier.

Source records contain the raw data that you collect from specified data locations, such as CRMs, ERPs, and SCMs. The raw data in Source Records is cleaned, standardized, and stored as unmastered data in a data lake or data warehouse so that it can be processed into Master Records.

Perform the following steps to view source records:

1. On the left navigation menu, click **Master Data**. The Master Data page opens with the Master Records listed in a table.
2. Click the **Source** tab. The Source Data page appears with the source records listed in a table. Each source record has a Source Record Table Key and a Source Application Identifier, which are unique values that the data steward can use to trace the record. All other data elements in the source data table are configured by the user.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pentaho-data-mastering/sourcing-data/viewing-source-records.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.