COAR based resource & irish tender fields #25

This PR introduces the support for

a new instance level instanceTypeMapping field meant to host

the original types mapped from the transformed records
the relative coar-based type mapped by using the new vocabulary openaire::coar_resource_types_3_1
the resource type corresponding to the coar-based one, from the vocabulary openaire::user_resource_types

a new result level result meta type metaResourceType, to be populated using the new coar-based instance type using the vocabulary openaire::meta_resource_types
new result level fields to support the activities in the Irish tender

isGreen
openAccessColor
isInDiamondJournal
publiclyFunded

Provided that those 4 fields will be calculated in the context of the stats workflow that, working on the post-dedup graph will then export them as an actionset. As consequence, they should never be merged with another record that include the same information. Therefore, the logic for merging them has been defined as follows

for all the boolean flags (isGreen, isInDiamondJournal, publiclyFunded), the merge operation produces true only when at least one of the two records being merged contain a true value;
for the openAccessColor field, the merge operation is permitted only when the value comes only from one of the two records being merged, or when both expose the same value. In case of discordant value, null is produced as result of the merge operation.

This PR introduces the support for 1. a new instance level `instanceTypeMapping` field meant to host * the original types mapped from the transformed records * the relative coar-based type mapped by using the new vocabulary `openaire::coar_resource_types_3_1` * the resource type corresponding to the coar-based one, from the vocabulary `openaire::user_resource_types` 2. a new result level result meta type `metaResourceType`, to be populated using the new coar-based instance type using the vocabulary `openaire::meta_resource_types` 3. new result level fields to support the activities in the Irish tender * `isGreen` * `openAccessColor` * `isInDiamondJournal` * `publiclyFunded` Provided that those 4 fields will be calculated in the context of the stats workflow that, working on the post-dedup graph will then export them as an actionset. As consequence, they should never be merged with another record that include the same information. Therefore, the logic for merging them has been defined as follows * for all the boolean flags (`isGreen`, `isInDiamondJournal`, `publiclyFunded`), the merge operation produces true only when at least one of the two records being merged contain a true value; * for the `openAccessColor` field, the merge operation is permitted only when the value comes only from one of the two records being merged, or when both expose the same value. In case of discordant value, null is produced as result of the merge operation.

The PR can be merged. Just verify if in the enumerator for the open access colours green was missing by mistake

The PR can be merged. Just verify if in the enumerator for the open access colours green was missing by mistake

We do not need green in the enumerator because a publication can be gold/hybrid/bronze AND green (or not green if the post print is not available in Open Access). As explained by Ioanna, the color and the "green" are in fact orthogonal.

> The PR can be merged. Just verify if in the enumerator for the open access colours green was missing by mistake We do not need green in the enumerator because a publication can be gold/hybrid/bronze AND green (or not green if the post print is not available in Open Access). As explained by Ioanna, the color and the "green" are in fact orthogonal.

Labels Milestones

COAR based resource & irish tender fields #25

Reviewers

Step 1:

Step 2: