Data sources

A Data source is a service where published material (metadata and files) are stored, preserved, and made discoverable and accessible. A data source is described by the EOSC Profile for data sources.

Example:: Episciences is an overlay platform supporting the management of open-access journals on top of the Open Access repository HAL. In this context, episciences.org is a publishing Venue (journal, open access, open peer review), while HAL is a Data source. Articles published via episciences.org will be therefore linked to the respective journal (publishing Venue) and the data source HAL. However, HAL is also a publishing Venue for researchers that are directly uploading their Research product. More specifically, a publishing Venue with peer-review and some support for metadata curation. In this case, a Research product will be linked to HAL both as a publishing Venue and as a Data source.

Note

Each Research product must be associated with its publishing Venue and its Data source.

Properties

This section describes the metadata fields for a Data source.

Local identifier

Description:: Unique code identifiying a Data source in the SKG (if any, otherwise “stateless identifier”).
Type:: String
Use:: Mandatory (1)

 "local_identifier": "123"

Identifiers

Description:: Identifier for the entity outside of the SKG (e.g., PID).
Type:: List
Use:: Optional (0..1)

Scheme

Description:: The scheme for the external identifier.
Type:: String
Use:: Mandatory (1)

Value

Description:: The external identifier.
Type:: String
Use:: Mandatory (1)

 "identifiers": [
     {
         "scheme": "doi"
         "value": "https://doi.org/..."
     }
 ]

Name

Description:: Name of the Data source.
Type:: String
Use:: Mandatory (1)

 "name": "Zenodo"

Submission policy URL

Description:: This policy provides a comprehensive framework for the contribution of research products. Criteria for submitting content to the repository as well as product preparation guidelines can be stated. Concepts for quality assurance may be provided.
Type:: URL
Use:: Recommended (0..1)

 "submission_policy_url": "https://..."

Preservation policy URL

Description:: This policy provides a comprehensive framework for the long-term preservation of the research products. Principles aims and responsibilities must be clarified. An important aspect is the description of preservation concepts to ensure the technical and conceptual utility of the content.
Type:: URL
Use:: Recommended (0..1)

 "preservation_policy_url": "https://..."

Version control

Description:: If data versioning is supported: the Data source explicitly allows the deposition of different versions of the same object
Type:: Boolean
Use:: Optional (0..1)

 "version_control": true

Persistent Identity Systems

Description:: The persistent identifier systems that are used by the Data source to identify the ProductType it supports.
Type:: List
Use:: Recommended (0..1)

Persistent Identity Product Type

Description:: Specify the ProductType to which the persistent identifier is referring to.
Type:: Vocabulary: Research Product Type
Use:: Mandatory (1)

Persistent Identity Product Type Scheme

Description:: Specify the list of persistent identifier schemes used to refer to ProductTypes
Type:: List of terms following the vocabulary: Persistent Identity Scheme
Use:: Mandatory (1)

 "persistent_identity_systems": [
     {
         "product_type": "Research Literature",
         "pid_scheme": ["DOI", "Handle"]
     }
 ]

Jurisdiction

Description:: The property defines the jurisdiction of the users of the Data source, based on the vocabulary for this property
Type:: Vocabulary: Jurisdiction
Use:: Mandatory (1)

 "jurisdiction": "National"

Data Source Classification

Description:: The specific type of the Data source based on the vocabulary defined for this property.
Type:: Vocabulary: Data Source Classification
Use:: Mandatory (1)

 "data_source_classification": "Journal Archive"

Research Product Types

Description:: The types of OpenAIRE entities managed by the Data source, based on the vocabulary for this property
Type:: List of vocabulary terms: Research Product Type
Use:: Mandatory (1)

 "research_product_type": []

Thematic

Description:: Boolean value specifying if the Data source is dedicated to a given discipline or is instead discipline agnostic
Type:: Boolean
Use:: Mandatory (1)

 "thematic": false

Research Product Licensing

Description:: Licenses under which the research products contained within the Data source can be made available. Repositories can allow a license to be defined for each research product, while for scientific databases the database is typically provided under a single license.
Type:: List
Use:: Recommended (0..1)

Research Product License Name

Description:
Type:: String
Use:: Mandatory (1)

Research Product License URL

Description:
Type:: URL
Use:: Mandatory (1)

 "research_product_license": [
     {
         "name": "..."
         "url": "https://..."
     }
 ]

Research Product Access Policy

Description:
Type:: List of terms following vocabulary: COAR Access Rights 1.0
Use:: Recommended (0..1)

 "research_product_access_policy": ["open access"]

Research Product Metadata Licensing

Description:: Metadata Policy for information describing items in the repository: Access and re-use of metadata.
Type:: List
Use:: Recommended (0..1)

Research Product Metadata License Name

Description:
Type:: String
Use:: Mandatory (1)

Research Product Metadata License URL

Description:
Type:: URL
Use:: Mandatory (1)

 "research_product_metadata_license": [
     {
         "name": "..."
         "url": "https://..."
     }
 ]

Research Product Metadata Access Policy

Description:
Type:: List of terms following vocabulary: COAR Access Rights 1.0
Use:: Recommended (0..1)

 "research_product_metadata_access_policy": ["open access"]