Verify new dois before adding

[GlazerMann]

No description provided.

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@290ea02). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master     #972   +/-   ##
=========================================
  Coverage          ?   78.31%           
  Complexity        ?     1627           
=========================================
  Files             ?       10           
  Lines             ?     3427           
  Branches          ?        0           
=========================================
  Hits              ?     2684           
  Misses            ?      743           
  Partials          ?        0

Impacted Files	Coverage Δ	Complexity Δ
Template.php	77.59% <100%> (ø)	1522 <0> (?)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 290ea02...6733f65. Read the comment docs.

[ms609]

Not sure I follow the motivation for this one?

[GlazerMann]

Some dois that we get do not resolved. I am not sure if this is worth doing either. Perhaps we should count on users using comments to block them.

[ms609]

Is it necessary for a DOI to resolve for it to be correct? I'd argue that converting the bad doi in the deleted example and adding a broken date is a positive change?