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.

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.

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