-
Notifications
You must be signed in to change notification settings - Fork 228
How to Request a new DOI
-
The managing editor responsible for the Pull Request should send the following email to
[email protected]
cc-ingTim Haillay <[email protected]>
andAnnette 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)
- The Programming Historian em português (ISSN 2753-9296)
Sincerely,
[MANAGING EDITOR NAME]
-
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
-
Once all checks have passed and the PR has been approved by relevant reviewers, merge the PR.
-
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.
-
Respond to Sussex's email:
The article with DOI [NEW DOI HERE] is now published. Please resubmit our publication XML to CrossRef:
-
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!
- Copyediting
- Copyedit comments
- Typesetting
- Archival Hyperlinks
- Copyright
- DOI
- Gallery image
- Checklist comment
- Handover comment
- Closing comment
- Opening comment Phase 0
- Phase change comment 1 to 2
- Phase change comment 2 to 3
- Phase change comment 3 to 4
- Opening comment Phase 4
- Phase change comment 4 to 5
- Phase change comment 5 to 6
- Phase change comment 6 to 7
- Tracking lesson phase changes
- Organisational Structure
- Trustee Responsibilities
- Trustee and Staff Roles
- Services to Publications
- Funding
Training
- Onboarding-Process-for-New-Editors
- Leading-a-Shadowing-process
- Board-of-Director---Continuing-Development
The Ombudsperson Role
Technical Guidance
- Making Technical Contributions
- Creating Blog Posts
- Service Integrations
- Brand Guidelines
- French Translation Documentation
- Technical Tutorial on Translation Links
- Technical Tutorial on Setting Up a New Language
- Technical Tutorial on Search
- Twitter Bot
- Achieving-Accessibility-Alt-text-Colour-Contrast
- Achieving-Accessibility:-Training-Options
Editorial Guidance
- Achieving Sustainability: Copyediting, Typesetting, Archival Links, Copyright Agreements
- Achieving Sustainability: Lesson Maintenance Workflow
- Achieving Sustainability-Agreed-terminology-PH-em-português
- Training and Support for Editorial Work
- The-Programming-Historian-Digital-Object-Identifier-Policy-(April-2020)
- How to Request a New DOI
- Service-Agreement-Publisher-and-Publications
- ProgHist-services-to-Publications
- Technical Tutorial on Setting Up a New Language
- Editorial Recruitment
Social Guidance
Finances
- Project Costs
- Spending-Requests-and-Reimbursement
- Funding Opportunities
- Invoice Template
- Donations and Fundraising Policies
Human Resources
- Privileges-and-Responsibilities-of-Membership
- Admin-when-team-members-step-down
- Team-Leader-Selection-Process
- Managing-Editor-Handover
- Checklist-for-Sabbaticals
- New Publications Policy
- Parental-Leave-Policy
Project Management
Project Structure
Board of Trustees