Linking entity resultResult » History » Version 1
Alessia Bardi, 28/04/2015 05:39 PM
1 | 1 | Alessia Bardi | h1. Linking entity: Result_Result |
---|---|---|---|
2 | |||
3 | |_Property_|_Type_|_Multiplicity_|_Description_| |
||
4 | | Provenance | [[type_provenance|Provenance]] | 1..1 | | |
||
5 | | Qualifier | [[type_qualifier|Qualifier]] | 1..1 | | |
||
6 | |||
7 | Currently, only one Qualifier.Scheme is available for Result_Person relationship named "dnet:result_result_relations", whose values are: |
||
8 | * hasAmongTopNSimilarDocuments: @r1 hasAmongTopNSimilarDocuments r2@ means that Results @r1@ and @r2@ are similar and that @r2 isAmongTopNSimilarDocuments of r1@; |
||
9 | * isAmongTopNSimilarDocuments: @r1 isAmongTopNSimilarDocuments r2@ means that Results @r1@ and @r2@ are similar and that @r2 hasAmongTopNSimilarDocuments of r1@; |
||
10 | * isRelatedTo: two results are somehow related to each other. OpenAIRE may further refine the semantics of possible types of "relatedness" by adding new classes in the Qualifier.scheme "dnet:result_result_relations"; |
||
11 | * isMergedIn: relationships with this Qualifier.class are generated by the de-duplication system. A Result @r1 isMergedIn r2@ means that @r2@ has been selected as representative record for a group of records that describe the same real-world object described by @r1@. In other words, if @r1 isMergedIn r2@ and @r3 isMergedIn r2@, then @r1@ and @r3@ are duplicates; |
||
12 | * merges: inverse relationship of "isMergedIn". |