Open cjhak opened 8 years ago
The issue is caused by the fact that there are two fields about language: the common optional language field, and the community-specific required language field.
the record in question is https://b2share.eudat.eu/records/b1092be3cd4844e0bffd7b669521ba3c. The problem is that the community-specific metadata has a language field which is different than the general metadata language field. OAI-PMH exports the general metadata language, which is set to 'en'. We should either upgrade the community specific metadata set to remove the language field, or find a way to automatically harmonise the languages.
Reported in helpdesk issue 10429:
==Request info== Type: Issue Service: B2SHARE Subject: wrong language code exported via OAI-PMH Message: It seems that the language code of http://hdl.handle.net/11304/31c0d886-b988-11e3-8cd7-14feb57d12b9 (Middle Dutch = ISO-639-3 code "dum") is not correctly exported via OAI-PMH but instead the (default?) English is taken, see:
https://vlo.clarin.eu/data/others/oai-pmh/B2SHARE/oai_b2share_eudat_eu_30.xml
Please note that this is a different problem than the one reported at https://github.com/EUDAT-B2SHARE/b2share/issues/104 - since only 1 language is currently supported per record, I chose "dum" for this one.