DOI: Investigate making DOI format support more generic, don't assume a specific shoulder or separation character. #898
Description
Author Name: Kevin Condon (@kcondon)
Original Redmine Issue: 3400, https://redmine.hmdc.harvard.edu/issues/3400
Original Date: 2013-12-05
Original Assignee: Gustavo Durand
This ticket came about as a result of a user ticket, RT #171102
EZId demo creates a DOI that has not / after the shoulder. Freeman in the above ticket has existing DOIs that do not have a / after the shoulder and wants to import them. Since we assume a / after the shoulder, this would not work. So, this request is to remove any assumptions about shoulder and separators after the shoulder.
Merce felt we should adopt this general approach to improve future interoperability.
Update by @pdurbin on 2018-05-21
connects to #3583