> For the complete documentation index, see [llms.txt](https://docs.turium.ai/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.turium.ai/home/algoreus/turium-connector-documentation/turium-fabriq-overview/how-to-guides/engram-metadata-user-guide/discovery-and-lineage.md).

# Discovery and Lineage

* [Discovery](#discovery)
* [Lineage](#lineage)

### Discovery  <a href="#discovery" id="discovery"></a>

Metadata can be applied to various Algoreus components to enhance their discoverability and management efficiency. This facilitates the process of locating specific components within Engram.

For instance, a dataset might be marked as experimental, or an application might be designated as a production unit. These tagged entities can be easily found by implementing search queries with the associated metadata.

With the search feature, it's possible to locate entities:

* possessing a certain value for any key within their properties;
* having a specific key paired with a particular value in their properties; or
* containing a unique tag.

You could, for instance, locate a dataset that contains a "field with a certain name" or a "field with a designated name and a specific type".

To facilitate metadata searches, the Algoreus Engram can be utilized.

***

### Lineage  <a href="#lineage" id="lineage"></a>

Lineage can be extracted for dataset entities. A lineage illustrates all data interactions related to the entity within a specified timeframe and provides information about the origin of these interactions.

In the case of datasets, lineage can denote whether a dataset access was for read, write, or both actions, provided the methods within the dataset carry the right annotations. If such annotations are lacking, the lineage merely indicates that a dataset access occurred without specifying if it was for reading or writing.

***


---

# 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.turium.ai/home/algoreus/turium-connector-documentation/turium-fabriq-overview/how-to-guides/engram-metadata-user-guide/discovery-and-lineage.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.