> 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/multilanguage.md).
# Multilanguage
It is possible to store descriptive metadata in different languages and automatically bring it to OpenAccess through the Transfer Connector to the right language tab. The required configuration is detailed below.
### In OpenAccess
In Configuration and Settings/Languages/General, toggle on all the different languages the discovery platform is going to offer in the front end. It is important to define this option first, as the multilingual metadata fields will only be populated correctly if OpenAccess has those different profiles activated.
{% hint style="info" %}
No extra metadata fields need to be defined for the multilanguage option, as the platform will show the desired language when this is selected by the user.
{% endhint %}
### In LIBSAFE
For the language to be identified, a new metadata field needs to be created holding the translated information, and the IEcode needs to be defined with a specific prefix. If not, the Transfer Connector will treat each metadata field as the default language. The prefix needs to be followed by a separator ('..' by default) and the name of the metadata field it is translated.
> \[language prefix]..\[default metadata iecode]
For instance, if we have the object *The Last Supper* by Leonardo DaVinci and we want to display it in both English (our default language) and Spanish in our OpenAccess, our metadata fields would be as follows:
Below is a list of the different languages supported by the platform and the correct prefix for each:
| LANGUAGE | PREFIX |
| :------------------: | :----: |
| Arabic | ar |
| Armenian | hy |
| Basque | eu |
| Brazilian Portuguese | pt |
| Bulgarian | bg |
| Catalan | ca |
| Chinese | zh |
| Czech | cs |
| Danish | da |
| Dutch | nl |
| English | en |
| Finnish | fi |
| French | fr |
| Galician | gl |
| German | de |
| Greek | el |
| Hindi | hi |
| Hungarian | hu |
| Indonesian | id |
| Irish | ga |
| Italian | it |
| Norwegian | no |
| Iranian | fa |
| Portuguese | pt |
| Romanian | ro |
| Russian | ru |
| Spanish | es |
| Swedish | sv |
| Thai | ty |
| Turkish | tr |
---
# 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/multilanguage.md?ask=&goal=
```
`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.