Project

General

Profile

Result » History » Version 3

Claudio Atzori, 16/11/2021 05:19 PM

1 1 Claudio Atzori
h1. Result
2
3 2 Claudio Atzori
Results are intended as digital objects, described by metadata, resulting from a scientific process. 
4
5
h2. Result
6
7 1 Claudio Atzori
|_. field name |_. cardinality |_. type |_. description |
8
| id | ONE | string | Main entity identifier, created according to [[OpenAIRE_entity_identifier_and_PID_mapping_policy]] |
9
| type | ONE | string | Type of the result: one of 'publication', 'dataset', 'software', 'other' as declared in the terms from the "dnet:result_typologies":https://api.openaire.eu/vocabularies/dnet:result_typologies vocabulary |
10
| originalId | MANY | string | Identifiers of the record at the original sources |
11
| maintitle | ONE | string | A name or title by which a scientific result is known. May be the title of a publication, of a dataset or the name of a piece of software. |
12
| subtitle | ONE | string | Explanatory or alternative name by which a scientific result is known. |
13
| author | MANY | Author | The main researchers involved in producing the data, or the authors of the publication |
14
| bestaccessright | ONE | AccessRight (should be changed as it must NOT include the openaccessroute) | The most open access right associated to the manifestations of this research results. |
15
| contributor | MANY | string | The institution or person responsible for collecting, managing, distributing, or otherwise contributing to the development of the resource. |
16
| country | MANY | Country | Country associated with the result. TODO: explain or link why |
17
| coverage | MANY | string | ??? |
18
| dateofcollection | ONE | string | When OpenAIRE collected the record the last time. TODO: we should indicate the used date format |
19
| description | MANY | string | A brief description of the resource and the context in which the resource was created. |
20
| embargoenddate | ONE | string | Date when the embargo ends and this result turns Open Access. TODO: we should indicate the used date format | 
21
| instance | MANY | [[Instance]] | Specific materialization or version of the result. For example, you can have one result with three instances: one is the pre-print, one is the post-print, one is the published version |
22
| language | ONE | Object(code/label) | code: alpha-3/ISO 639-2 code of the language. Label: Language label in English. Values controlled by the "dnet:languages":https://api.openaire.eu/vocabularies/dnet:languages vocabulary |
23
| lastupdatetimestamp | ONE | long | Timestamp of last update of the record in OpenAIRE |
24
| pid | MANY | Pid | Persistent identifiers of the result. See also [[OpenAIRE_entity_identifier_and_PID_mapping_policy]] to learn more. |
25
| publicationdate | ONE | string | Main date of the research product: typically the publication or issued date. In case of a research result with different versions with different dates, the date of the result is selected as the most frequent well-formatted date. If not available, then the most recent and complete date among those that are well-formatted. For statistics, the year is extracted and the result is counted only among the result of that year. Example: Pre-print date: 2019-02-03, Article date provided by repository: 2020-02, Article date provided by Crossref: 2020, OpenAIRE will set as date 2019-02-03, because it’s the most recent among the complete and well-formed dates. If then the repository updates the metadata and set a complete date (e.g. 2020-02-12), then this will be the new date for the result because it becomes the most recent most complete date. However, if OpenAIRE then collects the pre-print from another repository with date 2019-02-03, then this will be the “winning date” because it becomes the most frequent well-formatted date. |
26
| publisher | ONE | string | The name of the entity that holds, archives, publishes prints, distributes, releases, issues, or produces the resource. |
27
| source | MANY | string | A related resource from which the described resource is derived. See definition of "Dublin Core field dc:source":https://www.dublincore.org/specifications/dublin-core/dcmi-terms/elements11/source |
28
| subjects | MANY | Subject | Subject, keyword, classification code, or key phrase describing the resource. |
29 2 Claudio Atzori
30
h2. Publication
31
32 3 Claudio Atzori
As subclass of Result, Publication inherits all its fields and extends it with the followings
33
34
|_. field name |_. cardinality |_. type |_. description |
35
| container | ONE | [[Container]] | Container has information about the conference or journal where the result has been presented or published |
36
37 2 Claudio Atzori
h2. Dataset
38
39
h2. Software
40
41
h2. Other research product