> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/bi-similarity/compare-similar-assets.md).

# Compare Similar Assets

## Overview

Datalogz' Control Tower provides the essential tools for a thorough comparison of similar assets. Once you see the overlaps, you can make informed decisions about their future. For example:

* If both assets serve a unique purpose, simply **Accept** their similarity.
* If it's safe to deprecate one of the assets, choose the best version and archive the redundant one.
* If both assets are similar, but can be consolidated, merge both assets to create a single, unified source.

The dedicated comparison interface facilitates informed decision-making and streamlines stakeholder outreach for efficient resolution.&#x20;

## How to compare assets

1. In the Cluster Map, select a node that you are interested in. The graph will show you its similarity cluster.
2. Click **View Analysis** to get details on the asset and other similar assets in the same cluster.

<figure><img src="/files/mGthMYE0oHKfeJ5k9GEB" alt=""><figcaption></figcaption></figure>

3. Click **View in BI Environment** to open the asset directly in its source tool, like Power BI.
4. Click **Compare** in the table with similar assets.
5. Review similar parameters. Optionally, you can click the icon behind "Source" and "Target" to see the asset in its source tool.&#x20;

   <figure><img src="/files/FjlrqkQhovEtzsfblOAL" alt=""><figcaption></figcaption></figure>
6. Click **Keep Both** if you decide the assets should co-exist.
7. Click **Notify Owners** if you want the owners to receive the recommendation to archive the assets.


---

# 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.datalogz.io/guides/bi-similarity/compare-similar-assets.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.
