Tip: See also the OpenAIRE FAQ for general information on Open Science and European Commission funded research.
Once the record has been published, you can no longer change the files in the record, nonetheless, there are several options:
All file update requests need to be submitted through our contact form.
Meeting above points ensures that we can resolve your case faster. Please note that we may reject your request if we deem that it is not a small change.
Zenodo is a strong supporter of open data in all its forms (meaning data that anyone is free to use, reuse, and redistribute) and takes an incentives approach to encourage depositing under an open license. We therefore only display Open Access uploads on the front-page. Your Closed Access upload is still discoverable through search queries, its DOI, and any communities where it is included.
Since there isn't a unique way of licensing openly and nor a consensus on the practice of adding attribution restrictions, we accept data under a variety of licenses in order to be inclusive. We will, however, take an active lead in signaling the extra benefits of the most open licenses, in terms of visibility and credit, and offer additional services and upload quotas on such data to encourage using them. This follows naturally from the publications policy of the OpenAIRE initiative, which has been supporting Open Access throughout, but since it aims to gather all European Commission/European Research Area research results, it allows submission of material that is not yet Open Access.
OpenAIRE Orphan Record Repository got a make-over and was re-branded as Zenodo. If you deposited your article in OpenAIRE Orphan Record Repository, it is also available in Zenodo. However, your user account was not transferred to Zenodo, so you will have to register again. If you register with the same email address in Zenodo as you used in OpenAIRE Orphan Record Repository, you will still have access to your publications. Don't hesitate to contact us for further information.
Zenodo is derived from Zenodotus, the first librarian of the Ancient Library of Alexandria and father of the first recorded use of metadata, a landmark in library history.
Zenodo is currently a drop in the ocean. CERN stores more than 100PB (petabytes) of physics data from the Large Hadron Collider (LHC), and produces roughly 25PB per year when the LHC is running.
Yes you can! On the upload page under Basic Information and Digital Object Identifier click the Reserve DOI button. The text field above will display the DOI that your record will have once it is published. This will not register the DOI yet, nor will it publish your record (so you can still update the files). This DOI can be safely used in the record's own content as well as any other separate datasets or papers you might be planning to publish.
We have two primary methods in place for dealing with spam submissions (e.g. advertisements, scams):
Submissions are reviewed at least once a day during business days.
Currently there is no visual inidicator on search results or record pages to tell if a user is safelisted or not. If you connected to Zenodo with your ORCiD or GitHub account, or had one of your uploads accepted in a community before the July 1st 2022, you were automatically added to the safelist.
If you see your own or other users' uploads being listed at the very end of your search results, you can contact us via our support form so that we can review the affected users and be manually added to the safelist.
On the record page and click the orange Edit button in the top-right corner. You will be taken to a form similar to the upload form, where you will be able to edit almost all of the record's metadata. Once you are done modifying it, click "Save" and then "Publish".
The error may occur due to some network issues or instability. You can try to upload from another network/machine (wired connections are also more stable).
If you are familiar with the command line and/or scripting, we have some snippets available that are a bit more resilient compared to browser-based uploads:
Finally, another option is to split the file(s) into smaller parts (if possible) which might also ease the process of distributing the dataset after publishing.
We also provide a testing instance of Zenodo, where you can freely try things out.
We currently accept up to 50GB per dataset (you can have multiple datasets); there is no size limit on the number of records in communities. However, we don't want to turn away use cases for larger datasets. If you would like to upload larger files, please contact us, and we will do our best to help you. Please be aware that we cannot offer infinite space for free, so donations towards sustainability are encouraged.
Where data that was originally sensitive personal data is being uploaded for open dissemination through Zenodo, the uploader shall ensure that such data is either anonymised to an appropriate degree or fully consent cleared. There are several tools that can help uploaders to anonymise their data, being one of them OpenAIRE Amnesia.
No. We are open to all research outputs from all fields of science regardless of funding source. Given that Zenodo was launched within an EU funded project, the knowledge bases were first filled with EU grants codes, but we are extending this to other funders.
Yes, your data is stored in CERN Data Center. Both data files and metadata are kept in multiple online and independent replicas. CERN has considerable knowledge and experience in building and operating large scale digital repositories and a commitment to maintain this data centre to collect and store 100s of PBs of LHC data as it grows over the next 20 years. In the highly unlikely event that Zenodo will have to close operations, we guarantee that we will migrate all content to other suitable repositories, and since all uploads have DOIs, all citations and links to Zenodo resources (such as your data) will not be affected.
Zenodo and the underlying Invenio Framework for digital repositories were designed according to the OAIS reference model. Full OAIS compliance can only be proven through ISO 16363 certification which is a recent standard with very few repositories worldwide certified to date. See our infrastructure page for further details on Zenodo’s organizational and technical infrastructure.
Not yet since CoreTrustSeal at the moment only certifies repositories that serve a specifically designated community and therefore not generalist repositories like Zenodo. CoreTrustSeal is considering including generalist repositories in CoreTrustSeal 2022, at which point we would apply for certification. We have provided our input to CoreTrustSeal’s request for community feedback on this issue.
No, we do not perform virus checks on user-uploaded files. We however serve user-uploaded files in the most secure manner possible to protect users from various types of malicious attacks.
Zenodo is hosted at CERN, which is an Intergovernmental Organization (IGO), with its seat in Switzerland and therefore not subject to the EU's General Data Protection Regulation (GDPR). Data protection at CERN, which Zenodo complies with, is governed by CERN’s Operational Circular 11 (OC11) that offers data protection at the same high standards and comparable to GDPR. You can read more about this in our relevant blog post.
Zenodo is an open dissemination research data repository, and the uploader of content responsible to ensure that the content is suitable for open dissemination and that it complies with applicable laws, including, but not limited to, privacy, data protection, and intellectual property rights. Thus, an uploader shall ensure that sensitive personal data is either anonymized to an appropriate degree or fully consent cleared. Uploaders considering Zenodo for the storage of non anonymized or encrypted/unencrypted sensitive personal data are therefore advised to use bespoke platforms rather than open dissemination services like Zenodo for sharing their data.
DOI versioning allows you to:
When you publish an upload on Zenodo for the first time, we register two DOIs:
Afterwards, we register a DOI for every new version of your upload.
This is best illustrated by an example of a software package. If the software has been released in two versions (v1.0 and v1.1) on Zenodo, then the following DOIs would have been registered:
The first two DOIs for versions v1.0 and v.1.1 represent the specific versions of the software. The last DOI represents all the versions of the given software package, i.e. the concept of the software package and the ensemble of versions. We therefore also call the them Version DOIs and Concept DOIs (note, technically both are just normal DOIs).
You may notice that the version DOIs do not include a “.v1”-suffix. Read below to find out why.
You should normally always use the DOI for the specific version of your record in citations. This is to ensure that other researchers can access the exact research artefact you used for reproducibility. By default, Zenodo uses the specific version to generate citations.
You can use the Concept DOI representing all versions in citations when it is desirable to cite an evolving research artifact, without being specific about the version.
Currently the Concept DOI resolves to the landing page of the latest version of your record. This is not fully correct, and in the future we will change this to create a landing page specifically representing the concept behind the record and all of its versions.
Yes. However, for uploads published before the 30th of May 2017, you have to first upgrade your record to support versioning. This is done by clicking the “Upgrade to versioned record” button on the record page.
IMPORTANT If you have previously uploaded multiple versions of an upload as individual records on Zenodo, then DO NOT click the button to upgrade your record with versioning support. Please contact us so we can link the records under one versioning scheme.
Clicking the “Upgrade to versioned record” button on any of the records you would like to link, will irreversibly register them as individually-versioned records.
If you used the GitHub integration to archive your software on Zenodo, then we have already migrated and linked your records to support versioning.
No, we only support DOI versioning for records with Zenodo DOIs (i.e. DOIs starting with the prefix 10.5281).
No, as before you can continue to edit the metadata of your upload without creating a new version of a record. You should only create a new version if you want to update the files of your record.
Including semantic information such as the version number in a DOI is bad practice, because this information may change over time, while DOIs must remain persistent and should not change.
Moreover, Zenodo DOI versioning is linear, which means that the Zenodo version number may in fact not be the real version number of the resource. Take for instance software, where it is common practice to have dot versions and make new releases in a non-linear order (e.g. first v1.0, then v1.1, then v2.0, then v1.2).
The versioning suffix is also not a functionality of the DOI system, i.e. adding .v2 to DOI will not resolve to version 2 of a resource for any DOI from any provider. Different providers also use different patterns such as e.g. .v2, .2, /2.
Most importantly, version suffixes are not machine readable. A discovery system that understands DOIs, will not know that .v1 and .v2 of a DOI are in fact two versions of the same resource.
A better solution to this problem is to semantically link two DOIs in the metadata of a DOI. This ensures that discovery systems have a machine-readable way to discover that two DOIs are versions of the same resource.
See also Cool DOIs blog post by Martin Fenner, DataCite Technical Director.
Currently DOIs registered by Zenodo follows the pattern “10.5281/zenodo.
No, if you change a 10kb README file in 50GB dataset we do not duplicate the entire 50GB dataset. Invenio v3, the underlying digital repository platform that powers Zenodo, efficiently handles the file storage so we only store the new extra 10kb.
OpenAIRE is an acronym for “Open Access Infrastructure for Research in Europe”. OpenAIRE helps Horizon 2020 researchers report their publications to the EC Participant Portal and comply with the European Commission Open Access Policy and Research Data Pilot.
OpenAIRE does this by aggregating European funded research output from nearly 1000 repositories from all over the world and makes them available via the OpenAIRE portal.
OpenAIRE further provides a European-wide helpdesk for Open Access, research analytics services, payment of Article Processing Charges (APCs) for Gold Open Access FP7 publications.
Zenodo is part of OpenAIRE and provides a repository for those researchers who do not have an existing institutional or thematic repository they can deposit their publications and data in.
Read more about OpenAIRE.
From June 2017, records are indexed immediately in OpenAIRE (i.e. you should be able to see the record within some few minutes in OpenAIRE). Note, that not all content in Zenodo is indexed by OpenAIRE (records display an OpenAIRE logo if they are indexed by OpenAIRE).
Records are available immediately as soon as they are indexed in OpenAIRE (see above).
The following content is indexed in OpenAIRE:
For more information see the OpenAIRE Content Acquisition Policy.
You can link records in Zenodo to grants from the following funders:
End-June 2017 we are also launching grants for the following funders:
OpenAIRE furthermore has the following funders in the pipeline which will be made available in Zenodo once they launched in OpenAIRE:
First check on above list if your funder is supported by Zenodo. If the funder is supported it can be that your grant is too new to appear in the database:
We track two types of events:
For both types of events, we track:
A user (human or machine) visiting a record, excluding double-clicks and robots.
A unique view is defined as one or more visits by a user within a 1-hour time-window. This means that if the same record was accessed multiple times by the same user within the same time-window, we consider it as one unique view.
A user (human or machine) downloading a file from a record, excluding double-clicks and robots. If a record has multiple files and you download all files, each file counts as one download.
A unique download is defined as one or more file downloads from files of a single record by a user within a 1-hour time-window. This means that if one or more files of the same record were downloaded multiple times by the same user within the same time-window, we consider it as one unique download.
The total data volume that has been downloaded for all files in a record by a user (human or machine), excluding double-clicks and robots. In case a user cancels a file download mid-way, we still count the total file size as fully downloaded.
By default, for a record, we display the aggregated counts of views, downloads and data volume for all versions of a record. You can further expand the usage statistics box on a record page to see the counts for the specific version.
Once a day.
Any search on Zenodo allows you to sort the search results by "most viewed".
A machine request is an automated request initiated by a human user, e.g. a script downloading data from Zenodo and running an analysis on the data. A robot request is an automated request made by e.g. a search engine crawler.
For each view/download event, we track an anonymized visitor ID. This anonymized visitor ID changes for a user every 24 hours, hence a user viewing the same record on two different days will have two different anonymized visitor IDs. The reason we track an anonymized visitor ID is in order to count unique views and downloads.
For security purposes, we also keep a web server access log which includes your IP address and your browser’s user agent string. This web server access log is automatically deleted after maximum 1 year and is also strictly separated from the usage statistics collection.
The anonymized visitor ID is generated from a personal identifier such as:
We combine the personal identifier with a random text value (a salt) and apply a one-way cryptographic hash function to scramble the data. The salt (random text value) is thrown away and regenerated every 24 hours. Using and afterwards throwing away the random salt, ensures that the anonymized visitor ID is fully random.
No, it is not possible to opt-out. The usage statistics tracking is fully anonymized and is done on the server-side.
We share only aggregated usage statistics with third-parties. We never share the raw usage statistics events, even though these usage statistics events are fully anonymized.
From 2013, we have been using a self-hosted Piwik instance to track usage statistics for zenodo.org. We were able to extract record views and downloads from this Piwik instance. Studies have however shown that Piwik fails at counting as much as 50-60% of the actual visits to a site.
Not yet, but we will be adding aggregated usage statistics for your communities.
In order to see and archive your organizational repositories on Zenodo you will need to have "Admin" permissions on said repository, either as an Admin of the organization or an Admin of one of your organization's repositories. Additionally, please make sure that the OAuth application on GitHub is granting permissions not only to your personal repositories but also to your organizational ones - to verify that go to your GitHub OAuth settings in your profile, and click on the Zenodo application to see more details. Make sure that Zenodo is given access (green tick) to your organization under "Organization access".
After that, navigate to your Zenodo GitHub settings page and click the "Sync now" button at the top.
Make sure the repository was enabled before the release was made, otherwise feel free to contact us.
Only the repositories which were enabled before a release was made will be archived automatically. If you want to archive some of your old releases, you can always download a release ZIP from GitHub and upload it to Zenodo using our web interface as a regular upload.
You can include metadata in a
.zenodo.json file at the root of your GitHub repository. This file's contents should be in line with the Zenodo deposit metadata schema and will be used to update the metadata from future GitHub releases. For more information on how to create a
.zenodo.json file, you can have a look at our GitHub integration documenation.
Part of our plans and ongoing work is to take into account or improve our integration of other software metadata schemas such as the Citation File Format (CFF) and CodeMeta. We are working closely with our users and scholarly software and citation communities to figure out exactly when, in what form, and how all these different metadata schemas and their files will be integrated into Zenodo.
When we find a
CITATION.cff file in your GitHub repository's root folder, we make a best-effort attempt at parsing Zenodo-compatible metadata from it.
For backwards-compatibility, if you have a
.zenodo.json file in the repository, only the
.zenodo.json's metadata will be taken into account. Of course, any existing valid
CITATION.cff file will still be used to display the citation box on the GitHub repository page, but will not affect in any way the metadata we extract for your published release Zenodo record.
No, however we do plan to make this possible.
We by default roll-up citations to all versions of your record in order to show its full impact.
You can however use the filter "Citations to this version" to show only citations to the specific version of a record you are viewing.
We display citations if available for all records in Zenodo.
Your record might not show any citations because:
Currently (January 2019) we primarily cover:
We also receive citation data from cross-domain citation data sources, however often the coverage is not good as it relies on publishers to make the citation data freely available (which some big publishers do not do).
We are currently receving citation data from:
We plan to expand this list with further data sources. Do not hesitate to get in contact with us, if you are interested in becoming a citation data source.
At launch (January 2019), around 2500 records have a minimum of one citation with a total of around 3500 total citations (about half from ADS and half from Crossref/DataCite Event Data). Only around 250 out of the 3500 citations are known by both systems.
Currently our infrastructure is feature complete, however we are still expanding our citation data sources in order to have better coverage. We will remove the beta label as soon as we reached a better coverage.
Working with citation data sources and checking the data quality takes time and thus we expect that we may stay in beta until first-half of 2020.
New citations from our citation data sources are made available minimum once a day.
Each citation shows a small question mark icon to the right, which if you hover the mouse over will display the tooltip containing the list of all data sources which provided the link.
Yes. We may receive the same citation from multiple data sources. The deduplication is purely based on synonymous persistent identifiers.
No, this is unfortunately not possible. We may allow this in the future but quality checking and spam detection make this non-trivial.
If you run a discovery system with citation data you can however become a data source. Contact us for further information.
We usually receive citation data as a link between two persistent identifiers (e.g. "DOI A cites DOI B") without any metadata. We therefore have to automatically retrieve metadata such as title, authors and publication year from other services. This automatic fetching of metadata however is sometimes not able to find any available metadata, in which case we only display the persistent identifier.
Asclepias is an Alfred P. Sloan Foundation funded project to improve software citation across Astronomy.
The goal is to promote scientific software into an identifiable, citable, and preservable object. The focus is on the needs of 1) authors of scholarly manuscripts and 2) developers of scientific software.
The project partners include: