# Sample Description of I-Flows

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

### Extract

Extraction is the first phase of “extract, transform, load.” Data is collected from one or more data sources. It is then held in temporary storage, where the next two steps are executed.

During extraction, validation rules are applied. This tests whether data meets the requirements of its destination. Data that fails validation is rejected and doesn’t continue to the next step.

### Transform

In the transformation phase, data is processed to make its values and structure conform consistently with its intended use case. The goal of transformation is to make all data fit within a uniform schema before it moves on to the last step.

Typical transformations include aggregators, data masking, expression, joiner, filter, lookups, XML, Normalizers and web services. This helps to normalize, standardize and filter data. It also makes the data fit for consumption for analytics, business functions and other downstream activities.

### Load

Finally, the load phase moves the transformed data into a permanent target system. This could be a target database, data warehouse, data store, data hub or data lake — on-premises or in the cloud. Once all the data has been loaded, the process is complete.

### Various types of Flow

<details>

<summary><a href="https://oresund-integration-platform.gitbook.io/oresund-integration-platform/about/product-and-developer-guide/sample-description-of-i-flows/api-api-iflow">API - API FLOW</a></summary>

</details>

<details>

<summary><a href="https://oresund-integration-platform.gitbook.io/oresund-integration-platform/about/product-and-developer-guide/sample-description-of-i-flows/api-file-iflow">API - FILE FLOW</a></summary>

</details>

<details>

<summary><a href="https://oresund-integration-platform.gitbook.io/oresund-integration-platform/about/product-and-developer-guide/sample-description-of-i-flows/db-api-iflow">DB - API FLOW</a></summary>

</details>


---

# Agent Instructions: 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:

```
GET https://oresund-integration-platform.gitbook.io/oresund-integration-platform/about/product-and-developer-guide/sample-description-of-i-flows.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
