@ -17,6 +17,67 @@ For example, the organizations supporting a research infrastructure fall in the
### id
_Type: String • Cardinality: ONE_
Main entity identifier, created according to the [OpenAIRE entity identifier and PID mapping policy](entity-identifiers).
The OpenAIRE id for the community/research infrastructure, created according to the [OpenAIRE entity identifier and PID mapping policy](entity-identifiers).
Description of the research community/research infrastructure
```json
"description": "This portal provides access to publications, research data, projects and software that may be relevant to the Corona Virus Disease (COVID-19). The OpenAIRE COVID-19 Gateway aggregates COVID-19 related records, links them and provides a single access point for discovery and navigation. We tag content from the OpenAIRE Research Graph (10,000+ data sources) and additional sources. All COVID-19 related research results are linked to people, organizations and projects, providing a contextualized navigation."
```
### name
_Type: String • Cardinality: ONE_
The long name of the community.
```json
"name": "Corona Virus Disease"
```
### subject
_Type: String • Cardinality: MANY_
The list of the subjects associated to the research community (only appies to research communities).
```json
"subject": [
"COVID19",
"SARS-CoV",
"HCoV-19",
...
]
```
### type
_Type: String • Cardinality: ONE_
The type of the community; one of `{ Research Community, Research infrastructure }`.
```json
"type": "Research Community"
```
### zenodo_community
_Type: String • Cardinality: ONE_
The URL of the Zenodo community associated to the Research community/Research infrastructure.
OpenAIRE entity instances are created out of data collected from various data sources of different kinds, such as publication repositories, dataset archives, CRIS systems, funder databases, etc. Data sources export information packages (e.g., XML records, HTTP responses, RDF data, JSON) that may contain information on one or more of such entities and possibly relationships between them. For example, a metadata record about a project carries information for the creation of a Project entity and its participants (as Organization entities). It is important, once each piece of information is extracted from such packages and inserted into the OpenAIRE information space as an entity, for such pieces to keep provenance information relative to the originating data source. This is to give visibility to the data source, but also to enable the reconstruction of the very same piece of information if problems arise.
OpenAIRE entity instances are created out of data collected from various data sources of different kinds, such as publication repositories, dataset archives, CRIS systems, funder databases, etc. Data sources export information packages (e.g., XML records, HTTP responses, RDF data, JSON) that may contain information on one or more of such entities and possibly relationships between them.
<spanclassName="todo">Definitions for the re3data specific elements from: https://gfzpublic.gfz-potsdam.de/rest/items/item_758898_6/component/file_775891/content</span>
For example, a metadata record about a project carries information for the creation of a Project entity and its participants (as Organization entities). It is important, once each piece of information is extracted from such packages and inserted into the OpenAIRE information space as an entity, for such pieces to keep provenance information relative to the originating data source. This is to give visibility to the data source, but also to enable the reconstruction of the very same piece of information if problems arise.
---
@ -16,127 +15,280 @@ OpenAIRE entity instances are created out of data collected from various data so
### id
_Type: String • Cardinality: ONE_
Main entity identifier, created according to the [OpenAIRE entity identifier and PID mapping policy](entity-identifiers).
The OpenAIRE id of the data source, created according to the [OpenAIRE entity identifier and PID mapping policy](entity-identifiers).
The datasource type (e.g. pubsrepository::institutional, Institutional Repository) as in the vocabulary [dnet:datasource_typologies](https://api.openaire.eu/vocabularies/dnet:datasourceCompatibilityLevel).
The datasource type; see the vocabulary [dnet:datasource_typologies](https://api.openaire.eu/vocabularies/dnet:datasource_typologies).
```json
"datasourcetype": {
"scheme": "pubsrepository::journal",
"value": "Journal"
}
```
### openairecompatibility
_Type: String • Cardinality: ONE_
The OpenAIRE compatibility of the ingested results, indicates which guidelines they are compliant to the vocabulary [dnet:datasourceCompatibilityLevel](https://api.openaire.eu/vocabularies/dnet:datasourceCompatibilityLevel).
The OpenAIRE compatibility of the ingested results, indicates which guidelines they are compliant according to the vocabulary [dnet:datasourceCompatibilityLevel](https://api.openaire.eu/vocabularies/dnet:datasourceCompatibilityLevel).
```json
"openairecompatibility": "collected from a compatible aggregator"
```
### officialname
_Type: String • Cardinality: ONE_
The official name of the datasource.
```json
"officialname": "Recent Patents and Topics on Medical Imaging"
```
### englishname
_Type: String • Cardinality: ONE_
The English name of the datasource.
```json
"englishname": "Recent Patents and Topics on Medical Imaging"
The date of validation against the guidelines for the datasource records.
The date of validation against the OpenAIRE guidelines for the datasource records.
```json
"dateofvalidation": "2016-10-10"
```
### description
_Type: String • Cardinality: ONE_
The description for the datasource.
```json
"description": "Recent Patents on Medical Imaging publishes review and research articles, and guest edited single-topic issues on recent patents in the field of medical imaging. It provides an important and reliable source of current information on developments in the field. The journal is essential reading for all researchers involved in Medical Imaging."
```
### subjects
_Type: String • Cardinality: ONE_
_Type: String • Cardinality: MANY_
List of subjects associated to the datasource
The subjects of the contents provided by the datasource.
```json
"subjects": [
"Medicine",
"Imaging",
...
]
```
### languages
_Type: String • Cardinality: MANY_
The languages of the contents provided by the datasource (OpenDOAR only).
The languages present in the data source's content, as defined by OpenDOAR.
```json
"languages":[
"eng",
...
]
```
### contenttypes
_Type: String • Cardinality: MANY_
The typologies of the contents provided by the datasource (OpenDOAR only).
Types of content in the data source, as defined by OpenDOAR
```json
"contenttypes": [
"Journal articles",
...
]
```
### releasestartdate
_Type: String • Cardinality: ONE_
<spanclassName="todo">TODO</span>
Releasing date of the data source, as defined by re3data.org.
```json
"releasestartdate": "2010-07-24"
```
### releaseenddate
_Type: String • Cardinality: ONE_
<spanclassName="todo">TODO</span>
Date when the data source went offline or stopped ingesting new research data. As defined by re3data.org
```json
"releaseenddate": "2016-03-28"
```
### accessrights
_Type: String • Cardinality: ONE_
Open, restricted or closed.
Type of access to the data source, as defined by re3data.org. Possible values: `{ open, restricted, closed }`.
```json
"accessrights": "open"
```
### uploadrights
_Type: String • Cardinality: ONE_
Open, restricted or closed.
Type of data upload, as defined by re3data.org; one of `{ open, restricted, closed }`.
```json
"uploadrights": "closed"
```
### databaseaccessrestriction
_Type: String • Cardinality: ONE_
All existing access restrictions to the research data repository. Allowed values are: feeRequired, registration, other (re3data only).
Access restrictions to the research data repository. Allowed values are: `{ feeRequired, registration, other }`.
This field only applies for re3data data source; see [re3data schema specification](https://gfzpublic.gfz-potsdam.de/rest/items/item_758898_6/component/file_775891/content) for more details.
```json
"databaseaccessrestriction": "registration"
```
### datauploadrestriction
_Type: String • Cardinality: ONE_
All existing restrictions to the data upload. (re3data only).
Upload restrictions applied by the datasource, as defined by re3data.org. One of `{ feeRequired, registration, other }`.
This field only applies for re3data data source; see [re3data schema specification](https://gfzpublic.gfz-potsdam.de/rest/items/item_758898_6/component/file_775891/content) for more details.
The research data repository supports versioning of research data. (re3data only).
Whether the research data repository supports versioning:
`yes` if the data source supports versioning, `no` otherwise.
This field only applies for re3data data source; see [re3data schema specification](https://gfzpublic.gfz-potsdam.de/rest/items/item_758898_6/component/file_775891/content) for more details.
```json
"versioning": true
```
### citationguidelineurl
_Type: String • Cardinality: ONE_
The URL of the research data repository providing information on how to cite its research data. The DataCite citation format is recommended (http://www.datacite.org/whycitedata). (re3data only)
The URL of the data source providing information on how to cite its items. The DataCite citation format is recommended (http://www.datacite.org/whycitedata).
This field only applies for re3data data source; see [re3data schema specification](https://gfzpublic.gfz-potsdam.de/rest/items/item_758898_6/component/file_775891/content) for more details.
"description": "Horizon 2020 Framework Programme - Research and Innovation action",
"id": "EC::H2020::RIA"
}
```
### jurisdiction
_Type: String • Cardinality: ONE_
Geographical jurisdiction (e.g. for European Commission is EU, for Croatian Science Foundation is HR).
```json
"jurisdiction": "EU"
```
### name
_Type: String • Cardinality: ONE_
The name of the funder.
```json
"name": "European Commission"
```
### shortName
_Type: String • Cardinality: ONE_
The short name of the funder.
```json
"shortName": "EC"
```
## FundingStream
Description of a funding stream.
### id
_Type: String • Cardinality: ONE_
The identifier of the funding stream.
```json
"id": "EC::H2020::RIA"
```
### description
_Type: String • Cardinality: ONE_
Short description of the funding stream.
```json
"description": "Horizon 2020 Framework Programme - Research and Innovation action"
```
## GeoLocation
Represents the geolocation information.
@ -370,6 +432,57 @@ The name of a specific place.
"place": "Tübingen, Baden-Württemberg, Southern Germany"
```
## Grant
The money granted to a project.
### currency
_Type: String • Cardinality: ONE_
The currency of the granted amount (e.g. EUR).
```json
"currency": "EUR"
```
### fundedamount
_Type: Number • Cardinality: ONE_
The funded amount.
```json
"fundedamount": 1.0E7
```
### totalcost
_Type: Number • Cardinality: ONE_
The total cost of the project.
```json
"totalcost": 1.0E7
```
## H2020Programme
The H2020 programme funding a project.
### code
_Type: String • Cardinality: ONE_
The code of the programme.
```json
"code": "H2020-EU.1.4.1.3."
```
### description
_Type: String • Cardinality: ONE_
The description of the programme.
```json
"description": "Development, deployment and operation of ICT-based e-infrastructures"
```
## Instance
An instance is one specific materialization or version of the result. For example, you can have one result with three instances as result of deduplication:
"description": "Development, deployment and operation of ICT-based e-infrastructures"
}
]
```
### keywords
_Type: String • Cardinality: ONE_
```json
"keywords": [
"Open Science",
...
]
```
### openaccessmandatefordataset
_Type: Boolean • Cardinality: ONE_
```json
"openaccessmandatefordataset": true
```
### openaccessmandateforpublications
_Type: Boolean • Cardinality: ONE_
```json
"openaccessmandateforpublications": true
```
### startdate
_Type: String • Cardinality: ONE_
The start year of the project.
```json
"startdate": "2018-01-01"
```
### enddate
_Type: String • Cardinality: ONE_
The end year pf the project.
```json
"enddate": "2021-02-28"
```
### subject
_Type: String • Cardinality: MANY_
The subjects of the project
```json
"subject": [
"Data and Distributed Computing e-infrastructures for Open Science",
...
]
```
### summary
_Type: String • Cardinality: ONE_
Short summary of the project.
```json
"summary": "OpenAIRE-Advance continues the mission of OpenAIRE to support the Open Access/Open Data mandates in Europe. By sustaining the current successful infrastructure, comprised of a human network and robust technical services, it consolidates its achievements while working to shift the momentum among its communities to Open Science, aiming to be a trusted e-Infrastructurewithin the realms of the European Open Science Cloud.In this next phase, OpenAIRE-Advance strives to empower its National Open Access Desks (NOADs) so they become a pivotal part within their own national data infrastructures, positioningOA and open science onto national agendas. The capacity building activities bring together experts ontopical task groups in thematic areas(open policies, RDM, legal issues, TDM), promoting a train the trainer approach, strengthening and expanding the pan-European Helpdesk with support and training toolkits, training resources and workshops.It examines key elements of scholarly communication, i.e., co-operative OA publishing and next generation repositories, to develop essential building blocks of the scholarly commons.On the technical level OpenAIRE-Advance focuses on the operation and maintenance of the OpenAIRE technical TRL8/9 services,and radically improvesthe OpenAIRE services on offer by: a) optimizing their performance and scalability, b) refining their functionality based on end-user feedback, c) repackagingthem into products, taking a professional marketing approach with well-defined KPIs, d)consolidating the range of services/products into a common e-Infra catalogue to enable a wider uptake.OpenAIRE-Advancesteps up its outreach activities with concrete pilots with three major RIs,citizen science initiatives, and innovators via a rigorous Open Innovation programme. Finally, viaits partnership with COAR, OpenAIRE-Advance consolidatesOpenAIRE’s global roleextending its collaborations with Latin America, US, Japan, Canada, and Africa."