mapping relationship from trasformed records based on oaf:relation #219

Transformed records in the aggregation system might expose relationships pointing to other entities that do exist in the graph. However, the XML element carrying this information was never defined in a uniform way, leading to the presence of several ways to express this information.

With the occasion of introducing the result-organization (affiliation) relations from the CNR Explora (aka. People) we took the opportunity to base this relation types on a common, extendible format, that could be hopefully adopted also to represent other relation types.

As for today, the XML representation for the affiliation links is based on the example below.

<oaf:relation relClass="hasAuthorInstitution"
              relType="resultOrganization"
              subRelType="affiliation">ror_________::https://ror.org/02gdcn153</oaf:relation>

This approach is almost fine, but misses an important information: the target entity type. It could be desumed by the relType attribute, but it would not be a very robust approach, it would be better to introduce yet another attribute to declare it explocitly, so that the implementation of the mapping can be straightforward.

Transformed records in the aggregation system might expose relationships pointing to other entities that do exist in the graph. However, the XML element carrying this information was never defined in a uniform way, leading to the presence of several ways to express this information. With the occasion of introducing the result-organization (affiliation) relations from the [CNR Explora (aka. People)](https://beta.services.openaire.eu/is/mvc/ui/repoApis.do#/api/openaire____::cnr_explora/api_________::openaire____::cnr_explora::oai/ALL/ALL) we took the opportunity to base this relation types on a common, extendible format, that could be hopefully adopted also to represent other relation types. As for today, the XML representation for the affiliation links is based on the example below. ``` <oaf:relation relClass="hasAuthorInstitution" relType="resultOrganization" subRelType="affiliation">ror_________::https://ror.org/02gdcn153</oaf:relation> ``` This approach is almost fine, but misses an important information: the target entity type. It could be desumed by the `relType` attribute, but it would not be a very robust approach, it would be better to introduce yet another attribute to declare it explocitly, so that the implementation of the mapping can be straightforward.

The PR can be integrated given the information in the transformed records will contain also the targetType attribute.

 @ -281,0 +298,4 @@
 				final String validationdDate = ((Node) o).valueOf("@validationDate");
 				if (StringUtils.isNotBlank(target)) {
 					final String targetType = element.attributeValue("targetType");

Labels Milestones

mapping relationship from trasformed records based on `oaf:relation` #219

Reviewers

Step 1:

Step 2:

Labels Milestones

mapping relationship from trasformed records based on oaf:relation #219

Reviewers

Step 1:

Step 2:

mapping relationship from trasformed records based on `oaf:relation` #219