Multilingual entity titles

[floriangantner]

References

Add references/links to any related issues or PRs. These may include:

• Fixes #[issue-number]
• Requires DSpace/DSpace#[pr-number] (if a REST API PR is required to test this)

Description

Working state of our implementation of multilingualism as presented and discussed at the Cris working group meeting 2022-04-05 (https://docs.google.com/document/d/1NJvUtDwKymY1hhxtcT_wjQvzx4pZlJcf0xICz5LRsq0) Not sure, if multilingualism is the correct term in this context to distinguish it from the i18n translation. Still a draft, because tests are missing.

Instructions for Reviewers

List of changes in this PR:

• dso-name-service: changed behaviour how the displaying title is being determined
  • get the first dc.title starting with same language as the current UI locale
  • get the first dc.title starting with the first language as the default UI locale
  • get the first dc.title in any language
• component textmultilingual for cris layout: similiar behaviour for the single metadatafield being shown
  • get the first metadatafield value starting with same language as the current UI locale
  • get the first metadatafield value starting with the first language as the default UI locale
  • get the first metadatafield value in any language

Include guidance for how to test or review your PR. This may include: steps to reproduce a bug, screenshots or description of a new feature, or reasons behind specific changes.

• create entities with dc.title in several languages
• add dc.title metadata with textmultilingual rendering For Example given (place of Metadata should matter): dc.title::it_IT
  dc.title::en_EN
  dc.title::de_DE

locale	defaultlocale	shown value
it	en	dc.title::it_IT
de	en	dc.title::de _DE
ru	en	dc.title::en_EN

dc.title::it_IT dc.title::en_EN dc.title	locale	defaultlocale	shown value
it	en	dc.title::it_IT
ru	en	dc.title::en_EN
de	en	dc.title::en_EN

dc.title dc.title ::it_IT	locale	defaultlocale	shown value
it	en	dc.title::it_IT
ru	en	dc.title
en	en	dc.title

Effects / Use Cases:

• Display of general Search-Result-Lists (and possible other benefits like the breadcrumb, page title etc...)

• locale de: (first result has dc.title in de_DE and en_EN)

• locale en:

• Display of Cris Layout (f.e. leading tab)

• locale de:

• locale en:

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

• [ ] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• [ ] My PR passes TSLint validation using yarn run lint
• [ ] My PR doesn't introduce circular dependencies
• [ ] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
• [ ] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
• [ ] If my PR includes new, third-party dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.

[corrad82-4s]

Hello @floriangantner , thank you very much for this interesting PR and for the work done for this feature. We are working on a similar feature, supported by TUHH. However, after some analysis, we have decided to and are implementing our logic, returning only metadata values in required language (or in a fallback one, if required is not available), on REST side instead of angular. Thank you again.