Data sources are EOSC Resources and a subclass of EOSC Services whose specific purpose is to offer deposition, preservation, curation, discovery, access, and usage statistics functionalities to collections of EOSC Research Products from a thematic or cross-discipline perspective.
EOSC Data Sources include Repositories, Scientific Databases, Aggregators, Journal sites, Publisher sites, and CRIS Systems. Data sources store, preserve, and support discovery and access to metadata, files, and data relative to publications, research data, research software, and other research products. Data sources can be “hybrid” in terms of content, as they may offer access to a variety of research products, and in terms of intended users and jurisdiction (i.e. target audience). Similarly to the EOSC Service Catalogue, the Research Product Catalogue can interoperate with thematic RI data source aggregators. Data source onboarding ensures that the quality of the metadata records of the given data sources respect EOSC research product profiles.
The EOSC Portal Data Source Profile, obtained from an analysis of known data source registries FAIRSharing.org, re3data.org, and OpenDOAR, is detailed in the following table.
Code | Attribute Name | Description | Type | Multiplicity | Required |
Data Source Policies | |||||
DS1.1 | Submission policy URL | 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. | URL | 0..1 | R |
DS1.2 | Preservation policy URL | 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 | URL | 0..1 | R |
DS1.3 | Version control | If data versioning is supported: the data source explicitly allows the deposition of different versions of the same object | Boolean | 1 | O |
DS1.4 | Persistent Identity Systems | The persistent identifier systems that are used by the Data Source to identify the ProductType it supports | 0..n | R | |
DS1.4.1 | Persistent Identity ProductType | Specify the ProductType to which the persistent identifier is referring to. | Vocabulary: Research Product Type | 1 | M |
DS1.4.2 | Persistent Identity ProductType Scheme | Specify the list of persistent identifier schemes used to refer to other research-related entities (e.g., authors, organizations, etc.) | Vocabulary: Persistent Identity Scheme | 1..n | M |
Data Source Content | |||||
DS2.1 | Jurisdiction | The property defines the jurisdiction of the users of the data source, based on the vocabulary for this property | Vocabulary: Jurisdiction | 1 | M |
DS2.2 | Data Source Classification | The specific type of the data source based on the vocabulary defined for this property | Vocabulary: Data Source Classification | 1 | M |
DS2.3 | Research Product Types | The types of OpenAIRE products managed by the data source, based on the vocabulary for this property | Vocabulary: Research Product Type | 1..n | M |
DS2.4 | Thematic | Boolean value specifying if the data source is dedicated to a given discipline or is instead discipline agnostic | Boolean | 1 | M |
Research Product Policies | |||||
DS3.1 | Research Product Licensing | Licenses under which the research products contained within the data sources 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. | 0..n | R | |
DS3.1.1 | Research Product License Name | String | 1 | M | |
DS3.1.2 | Research Product License URL | URL | 1 | M | |
DS3.2 | Research Product Access Policy | Vocabulary: COAR Access Rights 1.0 | 0..n | R | |
Research Product Metadata | |||||
DS4.1 | Research Product Metadata Licensing | Metadata Policy for information describing items in the repository: | 0..1 | R | |
DS4.1.1 | Research Product Metadata License Name | String | 1 | M | |
DS4.1.2 | Research Product Metadata License URL | URL | 1 | M | |
DS4.2 | Research Product Metadata Access Policy | Vocabulary: COAR Access Rights 1.0 | 0..n | R |
Data Source Classification
No. | Data Source Classification | Examples |
---|---|---|
Repository | Services for the deposition, preservation, discovery, and access of research products metadata and files, e.g. PANGAEA, Zenodo, B2SHARE, EGI AppDB, BioTools | |
Aggregator | Services for the aggregation of metadata about research products (and other entities) that are mainly collected (aka harvested) from data sources via APIs and then possibly curated/enriched by end-users, e.g. BASE, NARCIS, GESIS, B2FIND, OpenAIRE Research Graph | |
Scientific Database | Scientific Databases intended to store structured information about scientific entities, e.g. PROTDB, ENA, ECRIN Studies Database | |
Journal Archive | Data sources for the deposition (submission), preservation, discovery, and access of scientific journal articles (metadata and files), e.g. publishers sites, journal sites, etc. | |
Publisher Archive | Scientific literature publisher, e.g. Elsevier, Copernicus, Frontiers, Springer, providing metadata and files of scientific publications relative to journals and conferences | |
CRIS system | A current research information system (CRIS) is an information system to store, manage and exchange contextual metadata for the research products funded by a research funder or conducted at a research-performing organisation |
Research Product Type
No. | Research Product Type | |
---|---|---|
Research Data | product intended to encode information to be processed by machines (human readability is an option) | |
Research Software | software code intended for interpretation or compilation by a machine to become a process | |
Research Literature | product primarily intended for human reading (e.g., articles, thesis, reports, slides, books, etc.) | |
Other research products | products that cannot be classified as a publication, a dataset, or a software |
Persistent Identity Scheme
We should refer to an existing PID scheme listing/registry.
No. | Persistent Identity Scheme | Example |
---|---|---|
DOI | doi:10.2777/492370; https://dx.doi.org/10.2777/492370 | |
Handle | hdl:11304/a0557c56-92af-4b87-9be2-6c289043370e; https://hdl.handle.net/11304/a0557c56-92af-4b87-9be2-6c289043370e | |
RoR | ror:04wxnsj81; https://ror.org/04wxnsj81 | |
ORCID | orcid:0000-0002-2718-8918; https://orcid.org/0000-0002-2718-8918 | |
ISNI | isni:0000000114559647; http://www.isni.org/isni/0000000114559647 | |
ArXiv | arXiv:2203.03637; https://arxiv.org/abs/2203.03637 | |
PMCID | PMC8901419; https://europepmc.org/article/PMC/PMC8901419 | |
ARK | ark:53355/cl010066723; https://n2t.net/ark:/53355/cl010066723 |
8 Jurisdiction
No. | Jurisdiction | Description |
---|---|---|
Global | intended for all users | |
National | intended for users of a country, e.g. national data repository | |
Regional | intended for users of a region (e.g. Europe) | |
Institution | intended for users of an institution, e.g. university publication repository | |
Research Infrastructure | intended for users of RIs and Clusters communities | |
e-Infrastructure | intended for users of horizontal e-infra services (e.g. EGI, GEANT, OpenAIRE, EUDAT, Fenix, gaia-x) |