Document toolboxDocument toolbox

DOI Migration Document

Owned by Nick Grosenbacher
Last updated: Nov 02, 2018
1 min read

Things we need to do when we migrate from EZID to Datacite

Prep

When we are ready to migrate, we need to contact DataCite and set up an hour or so of time where we migrate from their service to our service. The most best time to do this would probably be mid-week, during working hours, with critical people actively taking part in the process. This way, if the new DOI service does not work/something is broken, we will be ready to quickly fix it.

Detailed Migration Plan

Prior to migration

  1. Set up a branch on web client that will put the new DOI service out of alpha mode.
    1. https://github.com/Sage-Bionetworks/SynapseWebClient/pull/3696
  2. Set up a branch (probably just need to pull into the release build) on stack builder that will change org.sagebionetworks.doi.prefix to be "10.7303" (elasticbeanstalk-template.json.vpt)
    1. https://github.com/Sage-Bionetworks/Synapse-Stack-Builder/pull/217
  3. Set up a '-1' build for the portal and repo that uses the artifacts from steps

During 1-hr migration window

  1. Confirm with DataCite that we are ready and they are ready to migrate
  2. Monitor/test the '-1' build to see if we can create a DOI with the new services
    1. This may not succeed until migration is complete
  3. Once a DOI is successfully created in '-1', change the CNAMES to make '-1' go live (Xa)

After migration

  1. Confirm that DOIs can be made on prod (using new system)
  2. Pull in changes that remove dead code.
    1. The above PRs remove dead code in the portal and stack builder 
    2. https://github.com/Sage-Bionetworks/Synapse-Repository-Services/pull/3431

That should conclude migration