> For the complete documentation index, see [llms.txt](https://docs.libnova.com/libsafe-advanced-preservation-administrator-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.libnova.com/libsafe-advanced-preservation-administrator-manual/preservation-configuration-basic-sections/metadata-filters/metadata-filter-creation.md).

# Metadata filter creation

The creation of a metadata filter can be accessed from the main screen of ‘Ingestion Controls’, by means of the link *Create a new import filter*.

In order to create an import filter, we must fill out the information related to name, description, status (active / inactive) and the mandate to request a metadata file pattern from the user.   

In the *Filter files* section, we must include all the files needed for the correct execution of the metadata filter. **LIBSAFE** lets us do that by a convenient drag & drop system, whereby we will only have to *drag and drop* the necessary files, or by the link *Drag files or select them here*, where a Windows file selection window will open.

{% hint style="info" %}
**Note**: there is a limit as for the number of files and the total size of the same that may be added simultaneously when we create a metadata filter. LIBSAFE will consult the server’s internal configuration and apply set guidelines. It will be the system administrators’ responsibility to configure said server parameters (in the example of the figure below, LIBSAFE is limited to 20 files and a maximum file size of 128 MB).
{% endhint %}

The added files are listed as shown in the following figure. We can remove from the list any file that has been added, but later deemed not needed. It is possible to add a description for every file.

In case the ingestion control has more than one file, we will have to select which one will be the main or executable file for the ingestion control. **LIBSAFE,** by default, will select the first file to be added.

If the metadata filter includes an XSLT or XML file for the parsing of the descriptors, we must select the XSLT/XML check related to the corresponding file.

![](/files/-MjjUNxH_1La3CWB4Ovx)

Next, the metadata filter parameters are configured, if needed. By means of the link ***Add*** in the *Metadata filter parameters* section, we will see a form with the information needed to be filled out, such as:

* **Description**: a brief description of the parameter, syntax, possible values, etc.
* **Type of parameter**: as previously explained, on creating a preservation plan, the value entered for the parameter will be validated when a metadata filter is associated. Besides, if the type of data selected is numeric, we shall be able to assign the parameter value to a range and to specify said range.
* **Recommended Value:** we can indicate a value in order to facilitate the configuration of the metadata filter later on. This value will be modifiable when we apply a metadata filter to a preservation plan.
* **Default value**: in case a metadata filter will always need a value for the parameter, but there are situations where due to either the functionality of the metadata filter or because the user should not be forced to enter the value, this field can be filled with the value applied if the parameter value is left blank when configuring a metadata filter in a preservation plan.
* **Mandatory**: it is a check indicating whether it is mandatory to put a value to the metadata filter parameter or not.

{% hint style="info" %}
**Note**: Metadata filters will admit the configuration of up to five parameters.
{% endhint %}


---

# 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://docs.libnova.com/libsafe-advanced-preservation-administrator-manual/preservation-configuration-basic-sections/metadata-filters/metadata-filter-creation.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.