> For the complete documentation index, see [llms.txt](https://docs.libnova.com/libsafe-advanced-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-manual/get-started/openaccess-integration/transfer-connector.md).

# Transfer Connector

{% hint style="info" %}
Before understanding how the content is going to be published from the preservation to the discovery platform, it is important to outline the differences when we talk about an **object** in both Go and OA
{% endhint %}

* An object in LIBSAFE can be either a file or a folder, and it must be placed inside a data container
* An object which is going to be published in OpenAccess has to be defined as a folder only, which is the entity receiving the metadata needed for its publication. The folder should then include the content (which can be one or more files) that will be displayed. It is also placed inside a data container and contains special OA metadata fields. To avoid confusion, this manual will refer to the object intended to be published in OpenAccess as **OA object** or **published object**
* OA also introduces the concept of **collections** as discovery entities. This feature can only be configured from the OA platform and can group the different published objects brought into the discovery area

### Other considerations

There are certain rules to have in mind when configuring the schemas and collections for the discovery:

* The **IECODE** has to be unique across the platforms. However, when we are dealing with OA-specific descriptors, they can be present in different metadata schemas
* If an object is deleted from the preservation platform before it is unpublished, it will remain visible in OA. For it to disappear, it has to be manually hidden or deleted from the discovery platform
* Be patient if an object is not published and visible right away: it takes approximately five minutes for it to be accessible from the discovery area (both front and back end)

### Preparation

When it comes to publishing preserved content from LIBSAFE Advanced to OpenAccess (OA), some steps have to be configured to assure a successful publication. There is no specific order when it comes to some of these steps, as well as a need for replicating schemas and descriptors across platforms which makes the task sometimes simultaneous. The below image is intended as an illustration of how the steps interact before completing a successful publication.

![](/files/6ma9aQjIYNKQqTeSPxZK)


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.libnova.com/libsafe-advanced-manual/get-started/openaccess-integration/transfer-connector.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.