Zenodo.org will be unavailable for 2 hours on September 29th from 06:00-08:00 UTC.
We're excited to finally announce the launch date for migrating Zenodo to our next-generation platform. On September 29th, Zenodo's underlying technical platform will be migrated to InvenioRDM, a digital repository platform born out of Zenodo and developed together with 25 partners. See also our earlier announcement.
You can see a demo of the new Zenodo at https://zenodo-rdm-qa.web.cern.ch. The demo site has a snapshot of Zenodo production data from end-August.
Logging in
If you have an account on Zenodo.org, you can login on the demo site by resetting your password using the same email address as you registered with on Zenodo.org.
We are setting up an entirely new production system, and thus once the intervention is over you will be required to login again. This means that any page you had open on Zenodo.org prior to the intervention starting, will no longer be able to interact with Zenodo after the intervention is over, and thus the changes you made will be lost. To avoid losing changes, you must simply ensure that you save any changes prior to the intervention starting on Sep 29 at 06:00 UTC.
We're launching several new features together with the release as well. A full announcement is going out two weeks in advance of the release, thus following is a quick overview of some of the new features:
Yes, we provide backward compatibility for all existing features. We will be launching a series of new and improved features which will be announced 2 weeks before the migration.
Yes, we do our outmost to ensure backward compatibility of our APIs, and that your integration will continue to work on the new platform as well.
After Zenodo on InvenioRDM has been launched, we will deprecate some of our existing APIs. We will provide a migration period of 1-year for the transition. New features will only be available on the new API. The new API is similar to the existing API to ease the transition.
If your record has been accepted into a community which you're not the owner of, you will receive a request to grant community curators access to edit the metadata of your record. If you decline the request, your record will be removed from the community. If you neither accept or decline the request within 6 months, the community curators will be granted access to edit the metadata.
If your record has been accepted into a community which you're not the owner of and your record is either closed access or restricted access, you will receive a request to grant community curators access to view the files of your closed/restricted record. If you decline the request, or you do not accept the request within 6 months, your record will be automatically removed from the community.
Yes. We have ensured that all old links have been redirected to their new location. This include e.g. also a translation layer that ensure search queries still work.
Yes. The migration process starts already on Monday Sep 25th and will last throughout the week. In addition we have senior staff on duty during the full weekend in case of any problems.