# Libraries

## What are libraries in Qonic?

Libraries contain definitions of items that can be used across models within the project. Qonic currently supports the following library types:

* [Codes](https://help.qonic.com/documentation/qonic-dashboard/libraries/codes-libraries)
* [Materials](https://help.qonic.com/documentation/qonic-dashboard/libraries/material-libraries)
* [Properties](https://help.qonic.com/documentation/qonic-dashboard/libraries/property-libraries)
* [Locations](https://help.qonic.com/documentation/qonic-dashboard/libraries/location-libraries)
* [Types](https://help.qonic.com/documentation/qonic-dashboard/libraries/type-libraries)

## Project Libraries vs Model Libraries

When importing models in Qonic, it is possible to specify per library type whether to import the data into a shared project library or create a separate model-specific library. This can be specified by the project owners under project settings (1) in the preferences tab (2). By default, the 'project library' toggle will be disabled for each of the library types (3), meaning that for each newly imported model, a new model library for each library type will be created (if the imported model contains items of that library type). If you want to ensure that a certain type of data (e.g. materials) is shared across the models in the project,  enable the related toggle and choose which project library you want the newly imported data to be imported in. If there are no project libraries yet, you may need to create one first. You will find more information about defining project libraries below.

When using shared libraries and importing multiple models that contain library items with identical names and properties, these library items will be merged. For example, when importing two models that both contain a material called 'Concrete C50/60' and this material has the same properties in both models, these materials will be merged into one single library item. If you now modify this material in the library, the change will be visible in both models. 

{% hint style="info" %}
**Note:** at this time, model libraries for *properties* are not supported. Custom property definitions created in Qonic will always be in a shared project library. Custom property definitions imported through a model import are limited to that model and cannot be edited; therefore they are not shown in the dashboard library overview.
{% endhint %}

<figure><img src="https://929210962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZKeCFTBZzqUt4lpmhUdS%2Fuploads%2FydQsO1zUmbOn8p1pXrTG%2FFrame%204413.png?alt=media&#x26;token=29b08592-f5b5-4bd7-ac1c-075f7541916b" alt=""><figcaption></figcaption></figure>

The video below shows a graphical example of the difference between model libraries and project libraries.

{% embed url="<https://qonic.wistia.com/medias/b5tlngrwk2/>" fullWidth="false" %}

## Defining project libraries

To view your project libraries, open a project in the dashboard and go to the Libraries tab (4) at the top of the screen. On the left hand side (5) you can cycle between the different library types. Within the selected library type you will see an overview of current libraries (6), grouped in Project Libraries and Model Libraries. If you are not seeing the libraries you expect to see, make sure both project and model libraries are displayed using the view filter in the top-right corner (7).

To define a new project library, click the <kbd>+</kbd> button in the bottom-right corner (8).&#x20;

<figure><img src="https://929210962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZKeCFTBZzqUt4lpmhUdS%2Fuploads%2FvVw8ypS753dGsWik4gnF%2FFrame%204414.png?alt=media&#x26;token=4eca9902-8e95-4e8d-91b0-2cbf10c78925" alt=""><figcaption></figcaption></figure>

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Codification Libraries</strong></td><td>A guide to creating and managing classification systems in your project.</td><td><a href="https://929210962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZKeCFTBZzqUt4lpmhUdS%2Fuploads%2Facj4TvLAoEPWBWl0zoIP%2FFrame%204230.png?alt=media&#x26;token=25fa84a5-6716-4a2c-a65d-c8ff4493173a">Frame 4230.png</a></td><td><a href="libraries/codes-libraries">codes-libraries</a></td></tr><tr><td><strong>Material Libraries</strong></td><td>A guide to creating and managing material libraries in your project.</td><td><a href="https://929210962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZKeCFTBZzqUt4lpmhUdS%2Fuploads%2F1NeQk4BF4g6rVEZ9T9md%2FFrame%204231.png?alt=media&#x26;token=78917925-312d-47d7-ab25-6a784b95fa51">Frame 4231.png</a></td><td><a href="libraries/material-libraries">material-libraries</a></td></tr><tr><td><strong>Property Libraries</strong></td><td>A guide to creating and managing custom properties in your project.<br></td><td><a href="https://929210962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZKeCFTBZzqUt4lpmhUdS%2Fuploads%2FPewiLhaCT3WdrjvpzQvz%2FFrame%204232.png?alt=media&#x26;token=75b0ed49-723f-4227-9ec8-25c3a50ea94d">Frame 4232.png</a></td><td><a href="libraries/property-libraries">property-libraries</a></td></tr><tr><td><strong>Location Library</strong></td><td>A guide to creating and managing spatial locations in your project.</td><td><a href="https://929210962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZKeCFTBZzqUt4lpmhUdS%2Fuploads%2FwxIZxZhz8JcUrqqITmq7%2FFrame%204233.png?alt=media&#x26;token=dd8eae9f-38ad-46b1-a129-4a3571fd3922">Frame 4233.png</a></td><td><a href="libraries/location-libraries">location-libraries</a></td></tr></tbody></table>


---

# 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://help.qonic.com/documentation/qonic-dashboard/libraries.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.