> 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/transforming-master-records-into-golden-records/determining-status-of-master-records.md).

# Determining status of Master Records

View the list of Master Records to determine that status of Master Records, including which records must be edited to resolve match or merge conflicts.

You must have data steward privileges to edit Master Records.

Perform the following steps to determine the status of Master 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 one of the following tabs to view Master Records that have the corresponding status:
   * **Draft:** Master Records with match or merge conflicts that a data steward must edit to resolve, and then submit for review as a merge request. Match and merge conflicts are found during data curation. **Draft** is the default status assigned to Master Records when the records are created.
   * **In Review:** Master Records with a pending merge request that a reviewer must evaluate to determine whether those Master Records can be transformed into Golden Records. The reviewer evaluates only the Master Records that have the **In Review**status.
   * **Accepted:** Master Records with an approved merge request. Accepted Master Records are transformed into Golden Records.
   * **Rejected:** Master Records with a merge request that was rejected by the reviewer. Rejected Master Records are sent back to the data steward for additional edits.
3. In the tab that you selected, at the end of a Master Record row, click the more actions icon and select **View Details**. The Master Record details, along with Golden Record and source record information, are shown.


---

# 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://docs.pentaho.com/pentaho-data-mastering/transforming-master-records-into-golden-records/determining-status-of-master-records.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.