Open allanaaa opened 1 year ago
When a Dataverse import happens, it imports language metadata in the wrong format. In this case, "English" instead of a two-letter IETF language tag:
I think it's just pulling from the "Language" identifier of the object, here: https://dataverse.dartmouth.edu/dataset.xhtml?persistentId=doi:10.21989/D9/E6LW9H
Rather than the specific language values for each metadata property. So, maybe we can turn that bit off it's not really accurately representing data, instead of trying to do a language tag lookup and conversion as I was originally going to suggerst.
It's ported from the DSpace importer, which I suppose had more standardization to their language encoding, yeah. I can pull it out here.
When a Dataverse import happens, it imports language metadata in the wrong format. In this case, "English" instead of a two-letter IETF language tag:
I think it's just pulling from the "Language" identifier of the object, here: https://dataverse.dartmouth.edu/dataset.xhtml?persistentId=doi:10.21989/D9/E6LW9H
Rather than the specific language values for each metadata property. So, maybe we can turn that bit off it's not really accurately representing data, instead of trying to do a language tag lookup and conversion as I was originally going to suggerst.