# Approve evolution jobs selected by the system

With the passing of time or the appearance of new file formats some file formats may end up obsolete or discontinued. LIBSAFE includes an automatic mechanism with which the status of the file formats is periodically checked. When a file format is found in a compromised status, the system will look for the objects with files with such file format and will prompt their evolution.

Even though it is considered there are no obsolete or ‘expired’ file formats used in preservation currently, preloading of evolvers for certain old formats is being contemplated (like, for example, _WordPerfect_).

In this section it is possible to review the objects that the system has prompted for evolution and to approve its evolution. For that purpose, there is a search form that will use the following fields to filter:

* **Object name**
* **LUOI**
* **Date of creation from – date of creation to**
* **Any metadata value**
* **Preservation area and plan:** the drop-down menu shown allows for the selection of complete areas, preservation plans or a combination of both
* **Ingestion job**
* **Status:** filtered by status of the evolution jobs:
  * **Mandatory evolution:** the file format has become obsolete and needs evolution
  * **Recommended evolution:** even though the file format may have not become obsolete or expired, its evolution is recommended&#x20;
  * **Pending evolution tool:** the object has to be evolved, but the system does not have the necessary evolver yet
  * **Queued:** evolution approved and waiting to start the evolution job
  * **Failed**
  * **Evolved**
  * **Discarded:** even though the object was marked for evolution initially, the user decided to discard it later on
* **Evolution type:** Manual or prompted by the system
* **File** **formats.**

{% hint style="info" %}
**Note**: it is the responsibility of the preservation administrator to decide which objects have to be evolved and to approve their evolution. The LIBNOVA consultants are available for any clarification needed.
{% endhint %}

![](https://1027461619-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MjAMV2uTheGBDHeGhtb%2F-MjZSpHpGG2jbmvi_yjq%2F-MjZYHuOhNXWS7dY8942%2Fimage.png?alt=media\&token=028a33fe-7bff-44d9-afd2-2191b03bd39c)

Once the objects have been filtered, they will be listed in a way that they can be selected as needed. By clicking on _Evolve Selected_, every object selected for evolution will generate an evolution job.

Another action can be executed from the object list. Said action is _Eliminate selected from the evolution list_, which will remove the marked objects from the evolution job (those objects with the ‘Evolved’ and ‘In Progress’ status, cannot be removed from the evolution process).

![](https://1027461619-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MjAMV2uTheGBDHeGhtb%2F-MjZSpHpGG2jbmvi_yjq%2F-MjZYQjxN8LrHFQDbjs7%2Fimage.png?alt=media\&token=9c1b80dc-7497-4e26-b474-79ff85e4b117)

{% hint style="info" %}
**Note**: Sometimes, the list of objects to evolve may show one object with a ‘failed’ state and with no possible way to access the detail of the related ingestion job. The reason is that errors were made during the preparation of the object for&#x20;evolution.
{% endhint %}
