Multilingual support

[ddeboer]

Features

• For now, support only NL and EN.
• Offer terminology source metadata in both languages.
• Filter by language dynamically (instead of hardcoded NL, as it is now).

Overview of sources

Which sources support multiple languages?

• AAT: NL, EN, ES, FR, ZH
• Eurovoc: many languages
• RKD: NL, EN
• Uitvoeringsmedium: DE, EN, ES, FR, IT, NL
• Wikidata: many languages

All other sources are NL only, except Iconclass, which is EN only.

Tasks

• [ ] Require EN catalog metadata.
• [ ] Extend the catalog with EN metadata.
• [ ] For the sources GraphQL endpoint, return both NL and EN; clients can then filter by language. Do we want name_nl, name_en or rather name as an object with language and value properties for more flexibility? Clients can then filter. Try to keep BC here.
• [ ] If the demonstrator’s language is EN, show catalog in EN.
• [x] Extend the catalog with supported languages inLanguage per source.
• [ ] On https://termennetwerk.netwerkdigitaalerfgoed.nl/sources, show the supported languages for each source.
• [ ] Parameterise the GraphQL terms query with a property languages which takes an array of preferred search/result languages: e.g. [nl], [nl, en].
• [ ] Return the language of each result in the terms query endpoint. Clients can then either show all results, hide non-preferred languages or optionally show them.