zenodo and zenodo sandbox have less complex license objects in their md, making it impossible to differentiate between text, code, data, md and uibindings as we desigend it for the o2r md schema.
the mapping file needs to be adjusted to take only one license. it should always take the text license as it is most likely to reflect the main license given the wide spread publisher opinion of code and data being merely supplements.
note that this will back fire in ercs that are "data publications" instead of "papers with data"
zenodo and zenodo sandbox have less complex license objects in their md, making it impossible to differentiate between text, code, data, md and uibindings as we desigend it for the o2r md schema.
the mapping file needs to be adjusted to take only one license. it should always take the text license as it is most likely to reflect the main license given the wide spread publisher opinion of code and data being merely supplements.
note that this will back fire in ercs that are "data publications" instead of "papers with data"