# OpenAccess Configuration

### Collections <a href="#collections" id="collections"></a>

Any object can be published in OA as individual content. However, **collections** are an OA-exclusive feature that can be used for grouping records of the same nature, allowing smoother navigation throughout the published records. This step can only be configured through the OA platform, and this is done either before or after the objects are published. Nevertheless, it is recommended to design and create the collections before publishing, as this would help make better sense of the content and structure the final display.

![](https://1695872106-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FP5yg7kkoji8UODGQBrMs%2Fuploads%2FDgvf0V24643TruBkB0FC%2FOA_collections.png?alt=media\&token=427a8ed4-eba6-4017-8cad-a49d8420a95a)

Different attributes can be selected to further define features like additional metadata, descriptors, and other visual elements such as thumbnails and positioning within the platform when creating a collection. All of these features are completely optional, - except the title, and a guide for their configuration can be found [here](https://docs.libnova.com/libsafe-openaccess/).

### OpenAccess Metadata Schema

Another step that can only be done in OA is the configuration of the OA metadata schemas, which will compose the information section in each object. This schema will indicate which metadata fields are going to be displayed in the **Information** section in the published content.

Therefore, two specific schemas are at stake when publishing objects: the schema in Go with the specific OA descriptors plus the additional ones, and the schema created in OA which will output the Information content.

The OA schema has to replicate the descriptors (including the same title, type, and iecode) that are already defined in the Go schema. None of the OA-specific descriptors (profile, link, collection, etc.) have to be replicated in the Discovery area, as this is information handled by the Transfer Connector only.

![](https://1695872106-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FP5yg7kkoji8UODGQBrMs%2Fuploads%2F18pXR9zMYRASlf5rgvv8%2Foa_metadata2.png?alt=media\&token=be8b1c90-b9df-44c6-81d9-40289fbd70d4)

When creating the schema in OA, select **visible** to yes:

![](https://1695872106-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FP5yg7kkoji8UODGQBrMs%2Fuploads%2FMMyZ9aHFA91Gws5uOonJ%2Foa_metadata3.png?alt=media\&token=e215ae56-165a-454a-bb65-abfe0c0bb121)

The descriptors then have to match those created in Go. Each descriptor can be configured to be hidden or visible, as well as other characteristics like being marked as a mandatory field, the display order, or any parent-child relationship.

![](https://1695872106-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FP5yg7kkoji8UODGQBrMs%2Fuploads%2Fj3XMSQt8vPWGmGMw754n%2Foa_metadata4.png?alt=media\&token=a4190065-dee5-4851-93e7-b7bb12e48c66)

Once the schema is ready, an OA object can be created in the preservation area, applied to the schema, and populated:

![](https://1695872106-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FP5yg7kkoji8UODGQBrMs%2Fuploads%2FBOpVt0j4n3qT38crYIpf%2Foa_metadata5.png?alt=media\&token=7cb0548f-d27b-4d1b-9535-fbb80b448b8e)

After some time, the object is available in OpenAccess, where a schema can be applied for the information fields to be displayed. The title and other features can also be modified from the OA dashboard.

Below is the final result of the above process. The OA object **Information Test** has been successfully published in OA, with the correct visible metadata in the information area and with the three content files displayed appropriately:

![](https://1695872106-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FP5yg7kkoji8UODGQBrMs%2Fuploads%2F50RoecK5DGoy2MQKwywz%2Foa_metadata6.png?alt=media\&token=33320612-df44-4745-abbd-38f128321c75)

{% hint style="info" %}
Be patient! It takes around **five minutes** for the Transfer Connector to publish any changes in OpenAccess.
{% endhint %}

### Other tools

**Update objects:** when the metadata of a published OA object changes, it is necessary to perform an update. After the metadata has been changed, the metadata field OpenAccess Status has to be set from the current option to “Publish in OpenAccess”. Despite the OA object being updated (and even relocated to a different collection), the OpenAccess link field should not be altered or removed, as this will be done automatically by the system.

**Delete objects:** if an OA object needs to be removed from the discovery platform, the option “Un-Publish from OpenAccess” should be selected from the OpenAccess Status metadata field. This way, the object remains in the preservation area but is no longer visible for discovery.

**Objects with errors:** if the OA object publication fails during the process, the OpenAccess Status will display as “OpenAccess publication error” and the OpenAccess Log will contain a message specifying the error.

![](https://1695872106-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FP5yg7kkoji8UODGQBrMs%2Fuploads%2FSBDodEo60rJapPmWXRYS%2FOA_error.png?alt=media\&token=2041434f-9a16-493d-8819-a2376b58ec9a)
