Core entity result » History » Revision 3
Revision 2 (Paolo Manghi, 27/04/2015 05:09 PM) → Revision 3/47 (Claudio Atzori, 27/04/2015 06:11 PM)
h1. 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_| |_ Property_|_Type_|_Multiplicity_|_Description_| | Result Type | [[type_qualifier|Qualifier]] | 1..1 | ??????????????????????????????? | Result | | Title | [[type_structured_property|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 1..1| | | Result | | Publisher | [[type_provenance_property|StringWithProvenance]] [[provenance_property|StringWithProvenance]] | 0..1 | | Result | | Best License | [[type_qualifier|Qualifier]] | 1..1 | The most Open License value found among the [[type_result_instance|Instances]] of a Result [1] | Result | | Embargo end-date | Date | 0..1 | empty if the licenseClass does not imply an embargo | Result | | Description | [[type_provenance_property|StringWithProvenance]] | 0..N | Contains A result is characterized by the Abstract following properties: a date of acceptance, a publisher (optional), a description (optional), and an embargo end date (empty if the licenseClass does not imply an embargo). A Result | Result | | PID | [[type_structured_property|StructuredString]] | 0..N | is characterized by the following relationships with other entities: (i) PIDS (optional): which is the list of unique and persistent identifier identifiers used to identify the result together with the relative identification agency, e.g., EPIC, CrossRef, DataCite; | Result | | Language | [[type_qualifier|Qualifier]] | 0..1 | (ii) Titles (mandatory): the language used in the description or body Titles of the Result, specified according to a given classification represented as Class entities of languages, respectively described as a Class/Scheme; | Result | Scheme entity, e.g., original, alternative, subtitle, etc. | RelevantDate | Date | 0..N | a date relevant to the Result; | Result | | Subject | [[type_structured_property|StructuredString]] | 0..N | the scientific discipline (represented as Class/Scheme) covered by the Result; | Result | | External Reference | [[type_external_reference|ExternalReference]] | 0..N | external link which might be useful to contextualize the result; | Result | | Source | [[type_provenance_property|StringWithProvenance]] | 0..N | maps the dc:source element | Result | | Format | [[type_provenance_property|StringWithProvenance]] | 0..N | maps the dc:format element | Result | | Context | [[type_context|StringWithProvenance]] | 0..N | maps the dc:format element | Result | | Journal | [[type_journal|Journal]] | 0..N | | 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; (v) languageClass and languageScheme (optional): the language used in the description or body of the Result, specified according to a given classification of languages, respectively described as a Class entity and a Scheme entity; (vi) collectedFrom (mandatory): the DataSource entity from which the information relative to the Result entity was collected; (vii) relevantDates (optional): a list of dates relevant to the Result; (viii) fundingProjects (optional): the Projects which co-funded the research underlying the Result; (ix) subjects (optional): the scientific disciplines (represented as Class entities of a Scheme entity) covered by the Result; (x) external references: a list of external links which might be useful to contextualize the result; 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.