> For the complete documentation index, see [llms.txt](https://learn.coremodels.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.coremodels.io/getting-started/relations-and-taxonomies-part-2.md).

# Relations and Taxonomies (Part 2)

In this section we'll learn about the default relations, create another type <mark style="color:$success;">Scientific Post</mark>, and a taxonomy for the <mark style="color:blue;">StudyType</mark>.

***

#### Step 1: Inheritance

Let's start by Creating the <mark style="color:$success;">Scientific Post</mark> type, but since this is a 'Post' type which shares all the elements that already existed in the <mark style="color:$success;">Blog Post</mark>, we can simply 'Inherit' this type.

1. Open the 'Create New Type' modal.
2. Type in the type name <mark style="color:$success;">Scientific Post</mark>, and choose the <mark style="color:$success;">Blog Post</mark> in the SubClass Of dropdown.
3. Now click on 'Create and Add Elements'
4. Add the <mark style="color:blue;">StudyType</mark>, which is a unique element to this type

You now have created a type and learnt about the inheritance relation or 'SubClass Of' as in the Schema.org terms.

***

#### Step 2: Create a new taxonomy

Let's create a new taxonomy to limit the options of the <mark style="color:blue;">StudyType</mark>.

1. From the feature tray, click on 'Taxonomies', then click on 'Taxonomies Grid'.\
   (You'll notice that it'll open up a new grid in a new CoreModels tab for the Taxonmies)&#x20;
2. Click on the plus icon, and type in <mark style="color:purple;">Study Type Taxonomies</mark>.
3. Click on 'Create and Add Child'.
4. Add the following Taxonomies as children for the <mark style="color:purple;">Study Type Taxonomies</mark>:
   1. <mark style="color:purple;">Experimental</mark>
   2. <mark style="color:purple;">Observational</mark>
   3. <mark style="color:purple;">Theoretical</mark>

You now have created a taxonomy with its children

***

Step 3: Link the taxonomy to the element using the 'Controlled list' relation.

1. Open the Types Grid (or simply navigate back to it, by clicking on the CoreModels Tab 'Types Grid')
2. Open the 'Configuration' Side panel (by clicking the vertical configuration  button on the far right)
3. Select 'Controlled List' from the 'Elements Columns' dropdown
4. Expand or open the Elements grid at the <mark style="color:$success;">Scientific Post</mark> row (by clicking either icons in the 'Elements' column next to the type)
5. Double click on the 'Controlled List' cell (at the <mark style="color:blue;">StudyType</mark> row under the 'Controlled List' column)
6. Add the taxonomies <mark style="color:purple;">Experimental</mark>, <mark style="color:purple;">Observational</mark>, and <mark style="color:purple;">Theoretical</mark> from the dropdown.

Now the element is linked to the taxonomies.

Optional: Click on the <mark style="color:$success;">Scientific Post</mark> type to see the type card with all the relations and elements, you can click on the nodes in the graph or change the visualization 'Tree (Dendrogram)' to explore more options\
check out the 'Hierarchical (Dagre)' option.


---

# 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://learn.coremodels.io/getting-started/relations-and-taxonomies-part-2.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.