Internationalization : redesign the architecture to handle metadatablocks

[JayanthyChengan]

Have to figure out, how internationalization will be handled for the files under scripts/api/data/metadatablocks, so that new dynamic content, like domain metadata fields, can be added to the application and available in all languages.

[pameyer]

@JayanthyChengan It may make sense to have internationalization handled separately, but I'd be curious to have your input on how it might fit into something like #4451.

[4tikhonov]

I've managed to get all metadata fields translated in French

I can share my solution if the same functionality isn't coming with new release.

[JayanthyChengan]

Hi @4tikhonov : Thanks.
I was able to get the output and I committed the code to
https://github.com/scholarsportal/dataverse/tree/4684-metadatablock-internationalization

Will do PR soon after committing french metadata files.

[4tikhonov]

Hi @JayanthyChengan, thanks, I see, it's good idea to have a separate folder for translated properties. I'm looking forward to see it in the master branch, we'll use it for DataverseEU as well.

[4tikhonov]

Hi @4tikhonov : Thanks.
I was able to get the output and I committed the code to
https://github.com/scholarsportal/dataverse/tree/4684-metadatablock-internationalization

Will do PR soon after committing french metadata files.

@JayanthyChengan, we've introduced ISO codes in DataverseEU for all languages we're supporting, can you please also test this properties with current release?
https://github.com/IQSS/dataverse-docker/tree/master/dataversedock/dataverse-property-files
fr-CA here is coming from Scholarsportal, other translations were done by our community.

Also we modified
https://github.com/IQSS/dataverse-docker/blob/master/dataversedock/lang.templates/metadataFragment.xhtml to get translated properties for metadata fields. I don't know if it will be incorporated in the master branch soon so just in the case.

[scolapasta]

@JayanthyChengan thoughts on removing columns from db? It's not ideal to have duplicate info. (alternatively, the code could expect to use the db if the primary language and only use the bundle otherwis; but that seems like possible overkill in logic)