Core entity result » History » Version 5

« Previous - Version 5/47 (diff) - Next » - Current version
Alessia Bardi, 27/04/2015 18:55


Result

A Result is here intended as the (metadata) description/representation of a scientific output (possibly) resulting out of one or more projects.

Property Type Multiplicity Description Belongs to
Result Type Qualifier 1..1 ??????????????????????????? Result
Title StructuredString 1..N the Titles of the Result, represented as Class/Scheme, e.g., original, alternative, subtitle, etc. Result
Date of acceptance Date 1..1 Result
Publisher StringWithProvenance 0..1 Result
Best License Qualifier 1..1 The most Open License value found among the Instances of a Result [1] Result
Embargo end-date Date 0..1 empty if the licenseClass does not imply an embargo Result
Description StringWithProvenance 0..N Contains the Abstract of the Result Result
PID StructuredString 0..N unique and persistent identifier used to identify the result together with the relative identification agency, e.g., EPIC, CrossRef, DataCite Result
Language 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 Class/Scheme Result
RelevantDate Date 0..N a date relevant to the Result Result
Subject StructuredString 0..N the scientific discipline (represented as Class/Scheme) covered by the Result Result
External Reference ExternalReference 0..N external link which might be useful to contextualize the Result Result
Source StringWithProvenance 0..N maps the dc:source element Result
Format StringWithProvenance 0..N maps the dc:format element Result
Context StringWithProvenance 0..N Information about the fundings and/or research initiatives related to the Result Result
Journal Journal 0..N Journal where the publication has been published. Attributes refer to electronic, printed and linking (ISSN-L) ISSN. Publication
Resource Type Qualifier 0..1 It expresses the nature of the dataset Dataset
Device StringWithProvenance 0..1 Information about the device used to generate the dataset Dataset
Size StringWithProvenance 0..1 Dataset
Version StringWithProvenance 0..1 Information about the version of the dataset Dataset
Last Metadata Update DateWithProvenance 0..1 The last update date of the metadata of the dataset Dataset
Metadata Version StringWithProvenance 0..1 Information about the version of the metadata of the dataset Dataset
Relationship Target Type Multiplicity Description Belongs to
Collected From Datasource ? 1..N A Datasource from which this Result has been collected (e.g. an aggregator of institutional repositories) Result
Hosted By Datasource ? 1..N A Datasource that hosts the Results (e.g. an institutional repository) Result
Funding Project Datasource ? 0..N The Project that co-funded the research underlying the Result Result
? Person Person_Result 0..N Link to Person entities (e.g. authors, contributors) Result

(iii) Creators (mandatory): the creators of the Result, which are Person entities connected to the result through relative Person_Result entities;
(iv) Instances (mandatory): the Instances of the Result, which represent the locations (DataSource entities) where the Result files (web resources entities, e.g., DOIs) can be found;

Note that the difference betweem collectedFrom and hostedBy is introduced to encode the peculiar notion of Aggregation data sources, whose entities are obtained by federating a set of DataSource entities. In OpenAIRE aggregators are DataSources from which entities are “collected”, while the DataSources they aggregate “host” instead such entities. As such, Aggregators 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. In the case of other DataSources, e.g., repositories, collectedFrom and hostedBy refer to the same DataSource.