D-Net
/
openaire-graph-docs
6
1
Fork 5
Code Issues 5 Pull Requests 2 Packages Projects Releases 67 Wiki Activity
openaire-graph-docs/versioned_docs/version-6.1.1/graph-production-workflow/deduction-and-propagation/propagation.md

5.4 KiB
Raw Permalink Blame History

Propagation

This process enriches the graph by adding new links and/or new properties. The new information is added by exploiting existing semantic relationships and values between the involved entities

As of November 2022, the following procedures are in place:

  • Country propagation: updates the property “country” of a results. This happens when the result is collected from an institutional datasource or when the datasource hosting the result is inserted in a whitelist. For all the results whose hosting datasource verifies one of the conditions above, the country of the organization providing the datasource is added to the country of the result: e.g. publication collected from an institutional repository maintained by an italian university will be enriched with the property “country = IT”.

Country Propagation

  • Project propagation: adds a "isProducedBy" relationship (and its inverse) between a Project P and Result R1, if R1 has a strong semantic relationship with another Result R2 and P produces R2: e.g. publication linked to project P “is supplemented by” a dataset D. Dataset D will get the link to project P. The relationships considered for this procedure are “isSupplementedBy” and “isSupplementTo”.

Project Propagation

* Result to RC/RI through organization propagation. The manager of the RC/RI can specify a set of organizations whose product are relevant for the community. Each result having such a relation of affiliation with at least one organization relevant for the RC/RI will be linked to it.

Result to community through organization propagation

  • Result to RC/RI through semantic relation: extends the set of products linked to a RC/RI by exploiting strong semantic relationships between the results; e.g. if a result R1 is associated to the community C and is supplemented by a result R2 then the result R2 will be linked to the community. The relationships considered for this procedure are “isSupplementedBy” and “supplements”.

Result to community through semantic relation propagation

* ORCID identifiers to result through semantic relation. This propagation enriches the results by adding ORCID identifiers to authors. The added ORCID will be marked as "potential" since they have been inserted through propagation. The process considers the set of overlapping authors between results (R1 and R2) linked with a strong semantic relationship (IsSupplementedBy, IsSupplementTo). For each author A in the overlapping set, if R1 provides the ORCID value for A and R2 does not, then the author A in R2 will be enriched with the information of the ORCID found in R1.

Orcid propation through semantic relation

  • affiliation to organization through institutional repository. This propagation adds one "hasAuthorInstitution" relationship (and its inverse) between a Result R and Organization O, if R was collected from a datasource D with type institutional repository, and D was provided by O.

Affiliation propagation through institutional repository

  • affiliation to organization through semantic relation. This propagation adds one "hasAuthorInstitution" relationship (and its inverse) between a Result R and an Organization O, if R has an affiliation relation with an organization O1 that is in relation "isChildOf" with O.

Affiliation propagation through semantic relation

The algorithm exploits only the organization leaves that are in a "IsChildOf" relation with another organization. So far one single step is done

propagation strategy