Principles


Best Effort Principles

Zenodo does not sign SLAs (service-level agreements). This is not a weakness, it is by design and marks a philosophy that we believe is most appropriate for Science. Instead, Zenodo is run by leading practitioners according to best practices.

What Science needs is inherent reliability, or more accurately demonstrated reliability based on open best practices. Furthermore the users should be able to influence these best practices. In the long-term, a service which is trusted is much more valuable than one for which assurances must be bought.

Service failure can never be undone. Enforcing an SLA means being prepared to litigate against the contract, which means compensation, frequently assessed on the basis of loss of revenue… but none of these concepts have any place or relevance in the free exchange of research results!

Living by these principles, Zenodo strives to make available architecture, implementation, practices and statistics. Please see for example the infrastructure page. We are also aiming to have these certified.


FAIR Principles

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).

To be Findable:

  • F1: (meta)data are assigned a globally unique and persistent identifier
    • A DOI is issued to every published record on Zenodo.
  • F2: data are described with rich metadata (defined by R1 below)
    • Zenodo's metadata is compliant with DataCite's Metadata Schema minimum and recommended terms, with a few additional enrichements.
  • F3: metadata clearly and explicitly include the identifier of the data it describes
    • The DOI is a top-level and a mandatory field in the metadata of each record.
  • F4: (meta)data are registered or indexed in a searchable resource
    • Metadata of each record is indexed and searchable directly in Zenodo's search engine immediately after publishing.
    • Metadata of each record is sent to DataCite servers during DOI registration and indexed there.

To be Accessible:

  • A1: (meta)data are retrievable by their identifier using a standardized communications protocol
    • Metadata for individual records as well as record collections are harvestable using the OAI-PMH protocol by the record identifier and the collection name.
    • Metadata is also retrievable through the public REST API.
  • A1.1: the protocol is open, free, and universally implementable
    • See point A1. OAI-PMH and REST are open, free and univesal protocols for information retrieval on the web.
  • A1.2: the protocol allows for an authentication and authorization procedure, where necessary
    • Metadata are publicly accessible and licensed under public domain. No authorization is ever necessary to retrieve it.
  • A2: metadata are accessible, even when the data are no longer available
    • Data and metadta will be retained for the lifetime of the repository. This is currently the lifetime of the host laboratory CERN, which currently has an experimental programme defined for the next 20 years at least.
    • Metadata are stored in high-availability database servers at CERN, which are separate to the data itself.

To be Interoperable:

  • I1: (meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation.
  • I2: (meta)data use vocabularies that follow FAIR principles
  • I3: (meta)data include qualified references to other (meta)data
    • Each referrenced external piece of metadata is qualified by a resolvable URL.

To be Reusable:

  • R1: (meta)data are richly described with a plurality of accurate and relevant attributes
    • Each record contains a minimum of DataCite's mandatory terms, with optionally additional DataCite recommended terms and Zenodo's enrichments.
  • R1.1: (meta)data are released with a clear and accessible data usage license
    • License is one of the mandatory terms in Zenodo'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 uploader.
  • R1.2: (meta)data are associated with detailed provenance
    • All data and metadata uploaded is tracable to a registered Zenodo user.
    • Metadata can optionally describe the original authors of the published work.
  • R1.3: (meta)data meet domain-relevant community standards
    • Zenodo is not a domain-specific repository, yet through compliance with DataCite's Metadata Schema, metadata meets one of the broadest cross-domain standards available.

Plan S - compliance self-assessment

The following is a self-assessment of Zenodo against the Plan S requirements for Open Access Repositories (as published October 2019).

See 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.
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.
  • Zenodo registers DOIs (via DataCite) for all deposited records. See DataCite.
  • Zenodo pioneered DOI versioning
  • Objects with pre-existing DOIs may be uploaded and the external DOI displayed.
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).
  • "High quality article level metadata"
    • Zenodo supports the DataCite Metadata Schema v4.
    • The following additional article level fields are supported: journal title/volume/issue/pages, conference title/acronym/dates/place/website, book publisher/place/ISBN/title/pages, alternate persistent identifiers (see all fields).
  • "in standard interoperable non-proprietary format"
    • The following metadata formats are provided by Zenodo: MARCXML, Dublin Core (according to OpenAIRE Guidelines), DataCite, DCAT, JSON-LD (Schema.org).
  • "under a CC0 public domain dedication"
    • All metadata in Zenodo may be freely used under the CC0 waiver. (see terms of use, bullet 7).
  • "[...] include information on the DOI (or other PIDs) both of the original publication and the deposited version"
    • Zenodo registers DOIs for all uploads.
    • Zenodo allows including information on alternate persistent identifiers, as well as linking to related persistent identifiers.
  • "include [..] the Open Access status and the license of the deposited version"
    • All Zenodo records include the Open Access status according to the COAR access right vocabulary (open, embargoed, restricted, closed).
    • All open access and embargoed records specify a license of the deposited material. Any license from the OpenDefinition and SPDX vocabularies are supported (including all Creative Commons licenses).
  • "including as a minimum the name of the funder and the grant number/identifier"
    • All records can be uniquely linked to grants in the OpenAIRE grant database. The database currently covers 11 funders and 2 million grants.
4. Machine readable information on the Open Access status and the license embedded in the article, in standard non-proprietary format.
  • The open access status and a license are embedded in all metadata formats (i.e. machine-readable). See our APIs below in the strongly recommended criteria response.
  • It is the responsibility of the uploader to ensure the open access status and a license is embedded in any digital file uploaded. Zenodo does not modify files uploaded by users in any way.
5. Continuous availability (uptime at least 99.7%, not taking into account scheduled downtime for maintenance or upgrades).
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.
  • Zenodo provides support via https://zenodo.org/support
  • The helpdesk is manned during CERN business hours (Mon-Fri 8:30-17:30 CET).
  • Zenodo's average response time is 22 hours (based on 1534 requests received in the period May-Oct 2019, and not accounting for out of business hours).

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.
  • Zenodo support users/machines uploading both AAM and VoR versions of manuscripts.
  • Zenodo supports both author uploads via a normal deposit user interface as well bulk uploads via our APIs.
8. Full text stored in a machine-readable community standard format such as JATS XML.
  • Zenodo supports all file formats, consistent with the goal of accommodating all research objects. XML files are stored alongside other representations like PDF as just another format.
9. Support for PIDs for authors (e.g., ORCID), funders, funding programmes and grants, institutions, and other relevant entities.
  • ORCID supported for authors and contributors.
  • Open Funder Registry supported for funders.
  • OpenAIRE grant database supported for grants.
  • Zenodo plans to support ROR for institutions.
10. Openly accessible data on citations according to the standards by the Initiative for Open Citations (I4OC).
  • Zenodo supports linking records with related persistent identifiers (both incoming and outgoing links - i.e. citations and references). The links are exported in the DataCite metadata registered with the DOI, and thus makes the links available in the CrossRef/DataCite Event Data.
  • Discovering citations to a record requires global knowledge of the entire world-wide corpus of journal articles which is out of scope for Zenodo. Zenodo, however, harvests openly available citation databases (Crossref/DataCite Event Data, NASA/SAO Astrophysics Data System and Europe PMC) for citations to Zenodo objects. All citation data is exported in Scholix-format. See https://help.zenodo.org/#citations for details.
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.
  • Zenodo 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.
  • Per community harvesting allows curation and indexing e.g., NASA ADS harvests specific communities which are curated by astronomy librarians; similarly by ZHB Luzern, BLR, etc.