An organization that uses Dataverse, CIMMYT, will be adding to or changing the contributor types in the citation metadata block:

That list comes from DataCite's metadata schema. CIMMYT plans to add contributor types that aren't on that list because they don't think that list represents all types of their dataset contributors and they would rather not use DataCite's "Other" contributor type.
Dataverse's OpenAIRE metadata export, based on the DataCite schema, includes contributor metadata (example OpenAIRE xml from Demo Dataverse). I think when the code that creates the exports was written, it was assumed that the contributor types that depositors can choose from will always be one of DataCite's contributor types.
When an installation lets depositors choose contributor types that aren't one of DataCite's contributor types, will contributor metadata appear in the OpenAIRE metadata export? If so, would the installation's custom contributor type term be used, which would produce metadata that doesn't validate against the DataCite schema?:
<contributor contributorType="TermNotInDataCiteSchema">
<contributorName>Starr, Joan</contributorName>
</contributor>
When an installation lets depositors choose contributor types that aren't one of DataCite's contributor types, that contributor type should be mapped to "Other" in the OpenAIRE export (and/or the DataCite export (#5889)) and in the metadata that's sent to DataCite (#2917):
<contributor contributorType="Other">
<contributorName>Starr, Joan</contributorName>
</contributor>
Definition of done for this issue:
Make sure that if a dataset depositor chooses a contributor type that is not one of DataCite's contributor types, the OpenAIRE metadata export code maps that contributor type to DataCite's "Other" contributor type.