# 2.4 View Browser

The View Browser contains all views associated with the module currently selected in the navigation menu. In the context of the **Qsee** platform, views refer to all types of tables and lists, including data models, tables, custom views, and matrices.

## Data Models

A Data Model is a category of entities that share a common set of properties, functional purpose, and intended use.

> Example: Examples of data models include entities such as Building Elements, Materials, and Worksets.

{% hint style="info" %}
Note: In simple data models, all entities share the same set of properties (Common parameters).
{% endhint %}

> For example, in the **Rooms** data model, all rooms are described using an identical set of parameters.
>
> **In complex data models,** the set of properties may vary depending on the class of the entity within the model.
>
> For instance, a **Pump** and a **Chiller** within the same Building Elements data model may have different sets of parameters (Specific parameters) based on their classification.

{% stepper %}
{% step %}
**Data model** management takes place in the <mark style="background-color:blue;">Account Admin</mark> module. To create a new data model, the navigation menu is used to access the corresponding module. In the **View Manager**, under the **Data Models** section, a table is presented containing the list of all data models associated with the account.

<p align="center"><em><mark style="background-color:blue;">Account Admin</mark> → Data Models</em></p>

<figure><img src="https://3746132422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwdK8VSug5GZiR80csCiD%2Fuploads%2FVtJmnrEcCXei8C9BIpCh%2F2.4%20Data%20Models.png?alt=media&#x26;token=e29117ce-9688-411f-9228-fca1bea0b0a5" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Editing mode is activated using the **Edit** button in the toolbar at the top right corner of the screen.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXftRHBt6pyJh_GJ5sA80gn6HoaRcANUYJXmzF7ZoWt2QE2osT0cZh8rmQihkC56G7V5HZqmJ_R_oTep_H57BcyKSZYp54ibzhZVRVX7s0lR0eTd2dXEN7W3qQVykA1d6c4l2PMG?key=PaUHeX9cwK6ohPhOGvTmfA" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
After editing mode is activated, a menu appears in the left section of the panel with a "**+**" button available for creating a new entry.

<figure><img src="https://3746132422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwdK8VSug5GZiR80csCiD%2Fuploads%2FBY14t6hluR34j2EEODj3%2F4.1%20Toolbar%20-%20Active%20-%20Add.png?alt=media&#x26;token=d3edb891-5884-4db0-82bf-60fb7dda33fd" alt="" width="375"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
The data model name is entered and the required properties are defined.

<figure><img src="https://3746132422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwdK8VSug5GZiR80csCiD%2Fuploads%2Fg1cCno9fJdXuof30eOdh%2F%D0%9E%D0%B3%D0%BB%D0%B0%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5%20Data%20Models.png?alt=media&#x26;token=79b44f2f-a6c6-42ce-9c94-cca40f6face5" alt=""><figcaption></figcaption></figure>

* **Name** – The name of the data model.
* **Description** – A user-defined description of the data model.
* **Classifiers** – A classifier assigned to the data model, if applicable.
* **Parameters** – Parameters assigned to the data model.
* **Modules** – Sections in which the data model will be placed. If needed, the model can be added to multiple sections at once.
* **GUID** – A unique identifier for the data model. It is assigned automatically and does not require manual input.
  {% endstep %}

{% step %}
After all required properties of the data model are completed, editing mode is exited. The changes are saved automatically upon exit.
{% endstep %}
{% endstepper %}

***

## Tables

Tables in Qsee represent a database structure that contains rows of values, where each cell corresponds to a named column. A grid icon is displayed before the name of each table in the platform. Standard table operations are available, including selecting rows and columns using Shift and Ctrl keys, copying, cutting, pasting, and autofilling values by dragging across a range.

> Example: Examples of tables may include standard Qsee entities, such as lists of worksets or project levels. In a levels table, each row represents a specific level, while the columns correspond to characteristics such as Level Name, Type, Project Base Point, Survey Point, Revit File, and Building Story.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfaitfbgqwt1lRHWoBEFMGENu-Vg2o25syWTpja_oAoNOjV5gtLOSQxFg-ApFqC_UeyNZD3guvm72upUb78WX69ny50eRsouB8dLf7oDX2V19wdqmDwS5lxZhIpN-KWVUN-xs9JNQ?key=PaUHeX9cwK6ohPhOGvTmfA" alt=""><figcaption></figcaption></figure>

***

## Custom Views

Custom views are user-defined views created for Qsee tables. They allow you to configure personalized representations of a table—by applying sorting or filtering—without affecting the main table's display.

When rows or elements are deleted from a custom view, or when its values are edited, those changes are also reflected in the main table.

A custom view is created through the table’s context menu by selecting the Create View command.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdGFFLqqvKmDQ6Dqk303qRgV8-h9zUQpFr1PZc8fHF9y0ISpRJ9z8OxyfqLEwLvSXV8yDwiUepO5ezDkavZ6V6uSAEJvkdGT5YGKKiJxAGzlDxKygIC1Kz9ICLfjQPvLa1pX9NwEw?key=PaUHeX9cwK6ohPhOGvTmfA" alt=""><figcaption></figcaption></figure>

***

## Matrices

Matrices are a type of view generated from a classifier by assigning parameters to it. Each matrix name in Qsee is accompanied by a grid icon enclosed in curly brackets. The main difference between matrices and tables is that each matrix cell is defined by two values — one from the row and one from the column.

To modify or add a value to a matrix cell, a context menu is used, which is accessed via right-click. The menu provides two assignment options:

**Mark as Instance** — the value is assigned at the instance level

<figure><img src="https://3746132422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwdK8VSug5GZiR80csCiD%2Fuploads%2FSEd2yrnF7ND1eFFmyKGv%2F2.4%20View%20Browser%20-%20Matrices%20-%20Mark%20as%20Instance.png?alt=media&#x26;token=8374c92d-4cf5-4bf1-8a9c-02068df1b6dc" alt=""><figcaption></figcaption></figure>

**Mark as Type** — the value is assigned at the type level<br>

<figure><img src="https://3746132422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwdK8VSug5GZiR80csCiD%2Fuploads%2FMe2LNE5JnSTeCSzvsHJA%2F2.4%20View%20Browser%20-%20Matrices%20-%20Mark%20as%20Type.png?alt=media&#x26;token=23918e68-2f61-4fd6-bec2-67bd18813647" alt=""><figcaption></figcaption></figure>

> Example: An example of a matrix is Building Elements. This matrix is used to define the mapping between classifier positions and project parameters. Such a configuration helps predefine, for example, a specific set of parameters for all elements classified as Wall.

To achieve this, a data model named *Building Elements* is created. In its **Classifiers** property, a preconfigured classifier that includes the ***Wall*** category is assigned. In the **Parameters** property, all required parameters are added. Once the data model is created, the corresponding matrix is opened and the mapping between classifier positions and project parameters is defined, with an indication of whether the assignment should be instance-based or type-based.

<figure><img src="https://3746132422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwdK8VSug5GZiR80csCiD%2Fuploads%2F5v6T1doUrvOZmGvBPBhE%2F2.4%20View%20Browser%20-%20Matrices.png?alt=media&#x26;token=8e2e11e5-da78-4d0f-851a-65b182abed71" alt=""><figcaption></figcaption></figure>
