Principles
![Work in progress](http://for.unipi.it/stefano_garzarella/files/2014/11/Work-in-progress-1024x603.png)
FAIR Priciples
FAIR Principles definition as referenced from:
Wilkinson, M. D. et al. The FAIR Guiding Principles for scientific data management and stewardship. Sci. Data 3:160018 doi: 10.1038/sdata.2016.18 (2016).
Findability:
- F1: (meta)data are assigned a globally unique and persistent identifier
- A DOI is allocated to every published dataset in RDSpace@UBT.
- F2: data are described with rich metadata (defined by R1 below)
- RDSpace@UBT's metadata is compliant with DataCite's Metadata Schema minimum, recommended and optional terms, with additional enrichements.
- F3: metadata clearly and explicitly include the identifier of the data it describes
- The DOI is a top-level and mandatory field in the metadata of each dataset.
- F4: (meta)data are registered or indexed in a searchable resource
- Metadata of each dataset is indexed and searchable directly in RDSpace@UBT's search engine immediately after submission.
- Metadata of each dataset to be archived and published is sent to DataCite servers during DOI registration and indexed at DataCite Commons.
Accessibility:
- A1: (meta)data are retrievable by their identifier using a standardized communications protocol
- Metadata for individual datasets as well as dataset collections are harvestable using the OAI-PMH protocol by the record identifier and the collection name / ID.
- Metadata is also retrievable through the public REST API (https://api-rdspace.uni-bayreuth.de).
- A1.1: the protocol is open, free, and universally implementable
- See A1: OAI-PMH and REST API are open, free and universal protocols
- A1.2: the protocol allows for an authentication and authorization procedure, where necessary
- Metadata are publicly accessible and licensed under public domain (CC0). No authorization is ever necessary to retrieve it.
- A2: metadata are accessible, even when the data are no longer available
- Bitstreams and metadata will be retained for the lifetime of the repository (See Policies).
- Metadata are stored in high-availability database servers at University of Bayreuth's IT Service Center, which are separate to the bitstreams themselves.
Interoperability:
- I1: (meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation
- RDSpace@UBT uses an XML schema as internal representation of metadata and offers export to other popular formats such as Dublin Core, DataCite or MARCXML.
- I2: (meta)data use vocabularies that follow FAIR principles
- For certain terms RDSpace@UBT refers to open, external vocabularies, e.g.: subjects (), license (Open Definition) and funders (FundRef).
- I3: (meta)data include qualified references to other (meta)data
- Each referrenced external metadata is qualified by a resolvable URL.
Reusability:
- R1: (meta)data are richly described with a plurality of accurate and relevant attributes
- Each dataset contains a minimum of DataCite's mandatory terms, with additional DataCite recommended and optional terms and RDSpace@UBT's enrichments.
- R1.1: (meta)data are released with a clear and accessible data usage license
- License is one of the mandatory terms in RDSpace@UBT's metadata, and is referring to an Open Definition license.
- Data downloaded by the users is subject to the license specified in the metadata by the depositor.
- R1.2: (meta)data are associated with detailed provenance
- All bitstreams and metadata uploaded are tracable to a registered user / University of Bayreuth member.
- Metadata can optionally describe the original authors / creators of a published object.
- R1.3: (meta)data meet domain-relevant community standards
- RDSpace@UBT is not a domain-specific repository.
However, through compliance with DataCite's Metadata Schema, metadata meets one of the broadest cross-domain standards available.
- RDSpace@UBT is not a domain-specific repository.
Plan S - compliance self-assessment
As RDSpace@UBT is conceptualized as an Open Access Repository, the University of Bayreuth aims at fullfilling the criteria mentioned in the Plan S requirements for Open Access Repositories (as published October 2019).
See our actual status concerning the Plan S Principles and Implementation (under Part III: Technical Guidance and Requirements / 2. Requirements for Open Access Repositories).
Mandatory Criteria for Repositories
1 - The repository must be registered in the Directory of Open Access Repositories (OpenDOAR) or in the process of being registered. | ✖ | We are working on it! |
2 - Use of PIDs for the deposited versions of the publications (with versioning, for example in case of revisions), such as DOI (preferable), URN, or Handle. | ✔ |
|
3 - High quality article level metadata in standard interoperable non-proprietary format, under a CC0 public domain dedication. This must include information on the DOI (or other PIDs) both of the original publication and the deposited version, on the version deposited (AAM/VoR), and on the Open Access status and the license of the deposited version. Metadata must include complete and reliable information on funding provided by cOAlition S funders (including as a minimum the name of the funder and the grant number/identifier). | ✔ |
|
4 - Machine readable information on the Open Access status and the license embedded in the article, in standard non-proprietary format. | ✔ |
|
5 - Continuous availability (uptime at least 99.7%, not taking into account scheduled downtime for maintenance or upgrades). | ✖ | We are working on it! |
6 - Helpdesk: as a minimum, an email address (functional mailbox) has to be provided; a response time of no more than one business day must be ensured. | ✔ |
|
Strongly Recommended Additional Criteria for Repositories
7 - Manuscript submission system that supports both individual author uploads and bulk uploads of manuscripts (AAM or VoR) by publishers. | ✔ |
|
8 - Full text stored in a machine-readable community standard format such as JATS XML. | ✔ | RDSpace@UBT supports all file formats, consistent with the goal of accommodating all research objects. |
9 - Support for PIDs for authors (e.g., ORCID), funders, funding programmes and grants, institutions, and other relevant entities. | ✖ |
|
10 - Openly accessible data on citations according to the standards by the Initiative for Open Citations (I4OC). | ✔ |
|
11 - Open API to allow others (including machines) to access the content. A compliant API must be free to access without any barrier. A light authentication mechanism such as a token for ‘power users’ – e.g., high-traffic collaborators – is acceptable as long as there is a totally open/anonymous route too. | ✖ |
|
12 - OpenAIRE compliance of the metadata. | ✔ | RDSpace@UBT is compliant with the OpenAIRE Guidelines v3.0. |
13 - Quality assurance processes to link full-text deposits with authoritative bibliographic metadata from third-party systems, e.g., PubMed, Crossref, or SCOPUS where feasible. | ? | Needs checking! |