Do not concatenate contributor role (text value) with contributor role (code) in Dublic Core published to public XML

[andrewjbtw]

Reported by @aeschweik via purl-feedback:

re: https://purl.stanford.edu/qx302xn7101

When you click on the 3-bar menu to the left of the viewer, the roles of the contributors appear to mash together two metadata fields. The first contributor is listed as "Hailey, Kim (intervieweeive)," when it should read "interviewee." The viewer seems to be concatenating the metadata fields contributor1.role1.value ("interviewee") and contributor1.role1.code ("ive"). The curator flagged this as a typo but I confirmed the values are separated into these two fields in Argo. I'm in Firefox if that is relevant. Thanks!

Even though the problem is visible in the viewer, I think it traces back to the Dublin Core generated when the Purl is published. The viewer is reading the IIIF manifest, which I believe is generated from the Dublin Core, which is embedded in the Purl public XML, which is generated from the Cocina.

The Dublin Core in the Purl XML has the following data:

<dc:contributor>Hailey, Kim (intervieweeive)</dc:contributor>
<dc:contributor>Hailey, Ashawna (intervieweeive)</dc:contributor>

I think we probably only want to publish the value "interviewee" here. Does that sound right @arcadiafalcone ? It seems like if someone wanted to parse the code, they would use the MODS. The Dublin Core, as published, makes it impossible to separate the two anyway.

[aeschweik]

I noticed today (while working on a different object) that the values for language are also concatenated in the viewer. It's published in the PURL XML as

<dc:language>Englisheng</dc:language>

Noting here because it seems like the same issue.

[andrewjbtw]

Hi @aeschweik, that's been ticketed separately: #4728