> For the complete documentation index, see [llms.txt](https://docs.videc.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videc.de/june5-3.7/en/webanwendung/sichten/datenbasis-handling.md).

# Data Basis Handling

## Database Selection

This setting can be accessed in the toolbar using the selection button labeled *Database*. The following configuration options are available under this entry:

* Database selection for measurements via defined time ranges
* Database selection for all measurements
* Database selection for specific measurements

The entries under the selection *Defined Time Ranges* are composed of the configuration for the *Time Ranges*. These were previously set in the [Settings](/june5-3.7/en/webanwendung/einstellungen.md) view. Each entry consists of the database name followed by the configured duration. Additionally, the time range that results from the configuration for the respective selection is displayed. If one of these entries is selected, the database and timestamp are set for the current object.

The entries under the selection *Apply to All* allow you to change the desired database for all measurements simultaneously.

The remaining entries relate to individual measurements. The database selection can be set individually for each measurement.

## Database Types

In JUNE5, both identical and different databases can be displayed in one chart. A distinction is made between the database for acron measurements and the database for non-acron measurements.

### Database for acron Measurements

| Database  | Description                          |
| --------- | ------------------------------------ |
| PROCESS   | Process data                         |
| INTERVAL1 | Interval data 1 \*                   |
| INTERVAL2 | Interval data 2 \*                   |
| INTERVAL3 | Interval data 3 \*                   |
| INTERVAL4 | Interval data 4 \*                   |
| INTERVAL5 | Interval data 5 \*                   |
| INTERVAL6 | Interval data 6 \*                   |
| INTERVAL7 | Interval data 7 \*                   |
| INTERVAL8 | Interval data 8 \*                   |
| DAY1      | Daily data from main interval        |
| DAY2      | Daily data from secondary interval 2 |
| DAY3      | Daily data from secondary interval 3 |
| DAY4      | Daily data from secondary interval 4 |
| DAY5      | Daily data from secondary interval 5 |
| DAY6      | Daily data from secondary interval 6 |
| DAY7      | Daily data from secondary interval 7 |
| DAY8      | Daily data from secondary interval 8 |
| WEEK      | Weekly data                          |
| MONTH     | Monthly data                         |
| YEAR      | Annual data                          |

### Database for Non-acron Measurements

Here the interval levels are fixed in interval width and thus cannot be changed.

| Database  | Description    |
| --------- | -------------- |
| PROCESS   | Process data   |
| INTERVAL1 | 1-minute data  |
| INTERVAL2 | 5-minute data  |
| INTERVAL3 | 15-minute data |
| INTERVAL4 | 30-minute data |
| INTERVAL5 | 1-hour data    |
| INTERVAL6 | 2-hour data    |
| DAY       | Daily data     |
| WEEK      | Weekly data    |
| YEAR      | Annual data    |


---

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

```
GET https://docs.videc.de/june5-3.7/en/webanwendung/sichten/datenbasis-handling.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.