diff --git a/docs/data-provision/enrichment/enrichment.md b/docs/data-provision/enrichment/enrichment.md index 0604141..16ff94e 100644 --- a/docs/data-provision/enrichment/enrichment.md +++ b/docs/data-provision/enrichment/enrichment.md @@ -24,13 +24,13 @@ As of November 2022, three procedures are in place to relate a research product * subjects: it is possible to specify a list of subjects that are relevant for the RC/RI. Every time one of the subjects is found among the subjects of a result, the result is linked to the RC/RI.

- Bulktagging Subject + Bulktagging Subject

* data sources: it is possible to list a set of data sources relevant for the RC/RI. All the results collected from these data sources will be linked to the RC/RI

- Bulktagging Data source + Bulktagging Data source

When only some results collected from a datasource are relevant for the RC/RI, it is possible to specify a set of selection constraints (SC) that have to be verified before linking the result to the @@ -46,7 +46,7 @@ A possible selection criteria can be: “All the products whose contributor cont

- Bulktagging Zenodo Community + Bulktagging Zenodo Community

@@ -59,35 +59,50 @@ relationships and values between the involved entities As of November 2022, the following procedures are in place: -* Country propagation: updates of the property “country” of a results. This happen when the result is collected from an institutional datasource or when the datasource hosting the result in 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: 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 + Country Propagation

-* Project propagation: adds a "isProducedBy" relationship (and its inverse) between a Project P and Result R, if R has a strong semantic relationship with another Result R1 and R1 is linked to P: 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: 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. This kind of propagation exploits the hasAuthorInstitution relation between results and organizations, -Each result having such a relation with at least one organization relevant for the RC/RI will be linked to it. +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 community through organization propagation

-* Result to RC/RI through semantic relation: e.g. publication associated to community C is supplemented by a dataset D. Dataset D will get the association to C. The relationships considered for this procedure are “isSupplementedBy” and “supplements”. +* 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 organization propagation + Result to community through semantic relation propagation

-* ORCID identifiers to result through semantic relation related products, if the products have the same authors: e.g. publication has ORCID for its authors and is supplemented by a dataset D. Dataset D has the same authors as the publication. Authors of D are enriched with the ORCIDs available in the publication. The relationships considered for this procedure are “isSupplementedBy” and “supplements”. +* 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. +

- Result to community through organization propagation + Orcid propation through semantic relation

-* affiliation to organization through institutional repository + +* 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.

- Result to community through organization propagation + Affiliation propagation through institutional repository

-* affiliation to organization through semantic relation + +* 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. +

- Result to community through organization propagation + 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 +

\ No newline at end of file diff --git a/static/img/docs/enrichment/bulktagging_datasource.png b/static/img/docs/enrichment/bulktagging_datasource.png index 4a54800..2ba8e96 100644 Binary files a/static/img/docs/enrichment/bulktagging_datasource.png and b/static/img/docs/enrichment/bulktagging_datasource.png differ diff --git a/static/img/docs/enrichment/bulktagging_subject.png b/static/img/docs/enrichment/bulktagging_subject.png index 3ee4784..9b2ea76 100644 Binary files a/static/img/docs/enrichment/bulktagging_subject.png and b/static/img/docs/enrichment/bulktagging_subject.png differ diff --git a/static/img/docs/enrichment/bulktagging_zenodo.png b/static/img/docs/enrichment/bulktagging_zenodo.png index 64aee75..cae4e24 100644 Binary files a/static/img/docs/enrichment/bulktagging_zenodo.png and b/static/img/docs/enrichment/bulktagging_zenodo.png differ diff --git a/static/img/docs/enrichment/organization_tree.png b/static/img/docs/enrichment/organization_tree.png new file mode 100644 index 0000000..c251676 Binary files /dev/null and b/static/img/docs/enrichment/organization_tree.png differ diff --git a/static/img/docs/enrichment/propagation_affiliationistrepo.png b/static/img/docs/enrichment/propagation_affiliationistrepo.png index 63cf757..c4f4141 100644 Binary files a/static/img/docs/enrichment/propagation_affiliationistrepo.png and b/static/img/docs/enrichment/propagation_affiliationistrepo.png differ diff --git a/static/img/docs/enrichment/propagation_country.png b/static/img/docs/enrichment/propagation_country.png index 70aa96f..43c5c2b 100644 Binary files a/static/img/docs/enrichment/propagation_country.png and b/static/img/docs/enrichment/propagation_country.png differ diff --git a/static/img/docs/enrichment/propagation_orcid.png b/static/img/docs/enrichment/propagation_orcid.png index cabfc2d..6b698db 100644 Binary files a/static/img/docs/enrichment/propagation_orcid.png and b/static/img/docs/enrichment/propagation_orcid.png differ diff --git a/static/img/docs/enrichment/propagation_organizationsemrel.png b/static/img/docs/enrichment/propagation_organizationsemrel.png index d6e55a9..e25d10f 100644 Binary files a/static/img/docs/enrichment/propagation_organizationsemrel.png and b/static/img/docs/enrichment/propagation_organizationsemrel.png differ diff --git a/static/img/docs/enrichment/propagation_resulttocommunitythroughorganization.png b/static/img/docs/enrichment/propagation_resulttocommunitythroughorganization.png index 68aa116..3a20718 100644 Binary files a/static/img/docs/enrichment/propagation_resulttocommunitythroughorganization.png and b/static/img/docs/enrichment/propagation_resulttocommunitythroughorganization.png differ diff --git a/static/img/docs/enrichment/propagation_resulttocommunitythroughsemrel.png b/static/img/docs/enrichment/propagation_resulttocommunitythroughsemrel.png index 2a8a785..d9ec931 100644 Binary files a/static/img/docs/enrichment/propagation_resulttocommunitythroughsemrel.png and b/static/img/docs/enrichment/propagation_resulttocommunitythroughsemrel.png differ diff --git a/static/img/docs/enrichment/propagation_resulttoproject.png b/static/img/docs/enrichment/propagation_resulttoproject.png index 750b691..7a28ffd 100644 Binary files a/static/img/docs/enrichment/propagation_resulttoproject.png and b/static/img/docs/enrichment/propagation_resulttoproject.png differ