# December 2022 release

##  **General improvements**

* Up until now you couldn't **change entity names** in your project settings. This was only possible from document type settings. This **limitation has been lifted**. (don't worry the name change will not overwrite the document type settings).<br>
* We introduced a new suggestion for your training tasks. When a new training is finished, you will notice **suggestions for document types** for documents where the model thinks the document type was wrong.<br>
* **Enrichments** can now be **enabled and disabled** in the project settings.

<figure><img src="/files/3H5ZHjH1TuBprRZfYg1j" alt=""><figcaption></figcaption></figure>

## **Features channels**

<figure><img src="https://ucarecdn.com/99e75d1a-337b-410b-bc1a-cd8c48ed4892/" alt=""><figcaption></figcaption></figure>

During the partner event, we announced that it would be possible to assign projects to different feature channels. This allows us to release features in a staged way and offer the possibility to contribute to the development of features.

**What does it mean for you?**

You can assign projects to a release channel:

* 🏭 **Stable** - contains only a feature set that should work at all times
* 👁️ **Preview** - contains a feature set that has been tested by users and has been improved through user feedback
* **🔬 Experimental** - contains a feature set that has been developed and tested internally

By default all projects are configured to follow the stable channel.

{% embed url="<https://docs.app.metamaze.eu/project/project-settings/feature-channels>" %}

<figure><img src="/files/3H5ZHjH1TuBprRZfYg1j" alt=""><figcaption></figcaption></figure>

## &#x20;**Model analytics \[**�� **Stable]**&#x20;

<figure><img src="https://ucarecdn.com/61778078-24ff-418d-b16b-5099549aa837/" alt=""><figcaption><p>A clear graph showing how the document classification is performing</p></figcaption></figure>

<figure><img src="https://ucarecdn.com/a1348fed-107b-46c8-8df3-ad763695efa3/" alt=""><figcaption><p>A graph showing that can help you to define thresholds</p></figcaption></figure>

Did you ever wonder "I wish I could look into more detail how a training of a model went and how I can improve my model or adjust project settings"?

You won't have to wonder anymore, you can look right into the analytics yourself! We have expanded the model management screen to include some advanced analytics to help you on your quest of finetuning your model. The above images are just a few screenshots of the many components that have been introduced!

{% embed url="<https://docs.app.metamaze.eu/project/training/model-management>" %}

<figure><img src="/files/3H5ZHjH1TuBprRZfYg1j" alt=""><figcaption></figcaption></figure>

## &#x20;**Table annotation \[🔬 Experimental]**

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

The past couple of months we received a lot of feedback about annotating composites taking a lot of effort. We heard you and we improved the way you can annotate tables.&#x20;

{% content-ref url="/pages/BcGsa1ZjCJlQBZd2uGg1" %}
[Table annotation](/getting-started/processing-documents/labelling-of-training-data/entity-extraction/table-annotation.md)
{% endcontent-ref %}

<figure><img src="/files/3H5ZHjH1TuBprRZfYg1j" alt=""><figcaption></figcaption></figure>

## **Parsing \[🔬 Experimental]**

&#x20;

<figure><img src="https://ucarecdn.com/8f3adb4c-c51b-4d03-a186-f94a7d4c42a5/" alt=""><figcaption></figcaption></figure>

When handling documents, more specifically numbers and dates, the default parsing in Metamaze was sometimes not sufficient. There was a default parser with all kind of rules, we have exposed the whole parsing logic. You can now finetune the parsing for each of your projects.

{% content-ref url="/pages/s2f87QxlgHSaRr7Jzpil" %}
[Parsing](/project/project-settings/parsing.md)
{% endcontent-ref %}

<figure><img src="/files/3H5ZHjH1TuBprRZfYg1j" alt=""><figcaption></figcaption></figure>

## **Favorite projects \[**�� **Stable]**

<figure><img src="https://ucarecdn.com/46582385-ec69-4e4a-a961-689b5b16f115/" alt=""><figcaption></figcaption></figure>

When working in Metamaze with a lot of projects and organisations, it became cumbersome to always look for your projects which you use a lot. We have introduced favorite projects. You can simply mark a project card and they will always show up at the top of the page.

<figure><img src="/files/3H5ZHjH1TuBprRZfYg1j" alt=""><figcaption></figcaption></figure>

## **Project analytics improvement \[**�� **Stable]**

<figure><img src="https://ucarecdn.com/06da170e-5bd8-4170-934a-734af84e73c4/" alt=""><figcaption></figcaption></figure>

&#x20;The project analytics validated status has been split into "Validated **without** corrections" & "Validated **with** corrections". This should give you a better idea of the documents that had to be corrected vs documents that required input but didn't need any corrections from the user.

{% content-ref url="/pages/YmENNR4Qa4a01lqaaNQM" %}
[Analytics](/project/production/analytics.md)
{% endcontent-ref %}


---

# 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://docs-old.app.metamaze.eu/release-notes/release-archive/release-archive-pre-2023/december-2022-release.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.