Research: Identify problematic DOI suffixes / suffix formats

Background

Over the years, some members have registered DOIs with problematic suffixes. Examples include:

• 10.18052/www.scipress.com/JHPR.2
• 10.24191/doi.org/10.24191/ij.v8i2.81
• 10.31235/osf.io/jvzq7

More are compiled here: https://docs.google.com/spreadsheets/d/18xW79oR0kIkvS6x_r-tmH3heBMyxLTXOo81khLDnZzk/edit#gid=0

What options do we have for programmatically identifying more of these? We may have to iterate a few times.

Observed behavior

Expected behavior

How urgent

Definition of ready

• Product owner: @SaraBowman / @abartell
• Tech lead:
• Service:: label applied
• Definition of done updated
• Acceptance testing plan:
• Weight applied

Definition of done

• Unit tests identified, implemented, and passing
• Code reviewed
• Available for acceptance testing via a staging URL, or otherwise
• Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed
• Knowledge base reviewed and updated
• Public documentation reviewed and updated
• Acceptance criteria met
  • AC 1
  • AC 2
• Acceptance testing passed
• Deployed to production

Notes