# Exporting OAIS AIP Packages

The platform provides the capability of exporting any folder (or group of folders) as an OAIS AIP package, encoded in a JSON file. Once configured, the JSON file will include all required all required AIP elements according to the OAIS.

## Configuring your OAIS mapping

The OAIS AIP definition classifies the information that is related to an AIP package in Representation Information and Preservation Description Information. Additionally, each group contains additional elements. For instance, the Structure Information is part of the Representation Information:

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

The platform allows the administrator to map the metadata fields used to contain each information type, to its corresponding type according the OAIS AIP definition. For instance, if your "Title" metadata field is part of the Reference Information (which is part of the Preservation Description Information), you can map both elements in the platform in the **OAIS AIP Packages** configuration section:

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

And then in the **AIP sections field mapping** section:&#x20;

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

In the left column (1) you have the IECODE of the Metadata field in your platform, and in the right column (2) you have the OAIS section it belongs to.

Using the **Add** button (3), you can create additional entries:

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

Organizations can better explain the semantics of their OAIS AIP packages, or even define semantics that apply to the whole AIP package, to better explain OAIS Representation Information Networks or to simply add semantics to the AIP Packaging. In the **AIP Packaging information** section, the Administrator can provide additional information that will be included in every AIP package generated. This is a good place to include information that will help future users to understand your AIP Packages. Information can be formatted using the Markdown markup language.&#x20;

## Generating a JSON AIP Package

Once the platform has been configured, the user can simply select one or more folders in the File Browser and call the OAIS AIP Generation function:

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

This function will create the corresponding JSON file including the whole AIP package details and its related elements:

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

The Function will create a log, like any other function:

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

And can be called programmatically. Please review the **Functions** section for additional information.

Finally, you can download your JSON file and their associated folders like any other file in the platform.


---

# 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.libnova.com/labdrive/cookbook/exporting-oais-aip-packages.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.