Core entity result » History » Version 32

Alessia Bardi, 29/04/2015 17:48

1 1 Paolo Manghi
h1. Result
2 1 Paolo Manghi
3 12 Paolo Manghi
A Result is here intended as the (metadata) description/representation of a scientific output (possibly) resulting out of one or more projects. Results has the following sub-entities: [[core_entity_publication|Publication]] and [[core_entity_dataset|Dataset]].
4 1 Paolo Manghi
5 14 Paolo Manghi
|_Property_|_Type_|_Multiplicity_|_Description_|
6 21 Alessia Bardi
| Title | [[type_structured_property|Structured(String,Qualifier,Provenance)]] |  1..N | the Titles of the Result, each with a typology represented by a Qualifier and Provenance information; for example Qualifier.Class = {original, alternative, subtitle, etc.} |
7 14 Paolo Manghi
| Date of acceptance | Date | 1..1 |
8 26 Alessia Bardi
| Publisher | [[type_structured_property|Structured(String,-,Provenance)]] | 0..1 | |
9 25 Alessia Bardi
| Description | [[type_structured_property|Structured(String,-,Provenance)]] | 0..N | Contains the Abstract of the Result |
10 24 Alessia Bardi
| PID | [[type_structured_property|Structured(String,Qualifier,Provenance)]] | 0..N | unique and persistent identifier used to identify the result together with the relative identification agency, e.g., EPIC, CrossRef, DataCite |
11 28 Alessia Bardi
| Language | [[type_structured_property|Structured(-, Qualifier, -)]]| 0..1 |  the language used in the description or body of the Result, specified according to a given classification of languages, respectively described as a Qualifier |
12 14 Paolo Manghi
| RelevantDate | Date | 0..N | a date relevant to the Result |
13 28 Alessia Bardi
| Subject | [[type_structured_property|Structured(String,Qualifier,Provenance)]] | 0..N | the scientific discipline covered by the Result |
14 14 Paolo Manghi
| Instance | [[type_result_instance|Instance]] | 1..N | An Instance of the Result, which represents a physical location where the Result files (web resources entities, e.g., DOIs) can be found |
15 14 Paolo Manghi
| External Reference | [[type_external_reference|ExternalReference]] | 0..N | external link which might be useful to contextualize the Result |
16 24 Alessia Bardi
| Source | [[type_structured_property|Structured(String,-,Provenance)]] | 0..N | maps the dc:source element |
17 24 Alessia Bardi
| Format | [[type_structured_property|Structured(String,-,Provenance)]] | 0..N | maps the dc:format element |
18 14 Paolo Manghi
| Context | [[type_context|Context]] | 0..N | Information about the fundings and/or research initiatives related to the Result |
19 6 Alessia Bardi
20 30 Alessia Bardi
|_Relationship_|_Target_|_Multiplicity_|_Description_|
21 30 Alessia Bardi
|[[linking_entity_resultProject|Result_Project]] | Project |0..N| The Project that co-funded the research underlying the Result |
22 30 Alessia Bardi
|[[linking_entity_personResult|Person_Result]] | Person |0..N| Link to Person entities (e.g. authors, contributors)  |
23 30 Alessia Bardi
|[[linking_entity_resultResult|Result_Result]]| Result|0..N| Link to Result entities (e.g. similar publications, related datasets)  |
24 3 Claudio Atzori
25 16 Paolo Manghi
[1] The difference betweem collectedFrom and hostedBy relationships is introduced to model the concept of Aggregator data sources. Aggregator data sources are themselves aggregating information packages from a set of data sources; they differ from the data sources they aggregate, but play an equally important role in delivering the entities to OpenAIRE, and should therefore be given visibility. Accordingly, in order to guarantee visibility and ROI to all data sources involved in this chain, when OpenAIRE collects information packages from Aggregators such packages are characterised by the data source from which they were “collected”, i.e. the aggregator itself, and the data sources where they were originally "hosted". Note that in the case of other typologies of data sources (e.g. repositories) collectedFrom and hostedBy refer to the same data source.