How to Request a new DOI

1. Ensure that the only remaining Travis CI error is the missing DOI. All author, editor, reviewer, and translator information MUST be complete before requesting the DOI.

2. The managing editor responsible for the Pull Request should send the following email to [email protected] cc-ing Tim Haillay <[email protected]> and Annette Moore <[email protected]>

   Using the subject line Programming Historian DOI request:

   To Sussex Library Cataloging,

   We would like to request a new DOI for a forthcoming article in:

   • [SELECT APPROPRIATE LINE]
   • The Programming Historian (ISSN 2397-2068)
   • The Programming Historian en español (ISSN 2517-5769)
   • The Programming Historian en français (ISSN 2631-9462)

   Sincerely,

   [MANAGING EDITOR NAME]

3. Sussex will respond with a DOI string that will look something like 10.46430/phen0089. Add a new YAML header field to the lesson PR and paste in the DOI precisely:

   doi: 10.46430/phen0089
   

4. Once all checks have passed and the PR has been approved by relevant reviewers, merge the PR.

5. VERY IMPORTANT: Wait 5-10 minutes until you are able to load the new lesson at its public URL. The XML is generated and published at the same time, and we need to make sure it's been updated publicly before moving on to the next step.

6. Respond to Sussex's email:

   The article with DOI 10.46430/phen0089 is now published. Please resubmit our publication XML to CrossRef:

   • [PICK APPROPRIATE LANGUAGE LINK]
   • https://programminghistorian.org/en/crossref.xml
   • https://programminghistorian.org/es/crossref.xml
   • https://programminghistorian.org/fr/crossref.xml

7. Sussex will reply once the upload has completed.

   • In the unlikely event there are validation errors, they will email you as well as our shared [email protected] account. Please alert the technical team if this occurs.
   • If they reply that the upload was successful, confirm that the DOI correctly redirects to the published lesson. Then celebrate!