Option for multilingual metadata

[pvgenuchten]

Metadata models (such as DCAT, ISO19139. MCF) support translation options for various elements (title, abstract, organization).

Storing translations

For backwards compatibility it could be interesting to keep the current, single language model and store translations in a linked table as:

record-id	key	value	language
a3e55-12ec-463	title	Distribución de especies exóticas en los bosques del Mediterráneo.	es

This will cause a challenge in translations within nested elements, such as keywords, distributions, contacts. Maybe here the translations can be included in the nested structure.

Dialects

Following the language header conventions, we best support the main langauge as well as the dialects en-us, en-uk, en-ca.

OGCAPI - Records

In OGCAPI - Records typically a record is returned in a single language. The language requested (via accept-language header) would be selected from the available translations. With a ?lang=en users would be able to override the language header provided by the browser.