@rdmpage @adam42smith @bioone @tandfonline @WileyEcolEvol @JSTOR @CrossrefOrg @d_tkaczyk FTR- Since then we've worked with JSTOR to sort out a lot of issues having to do with the way they were (and weren't) registering DOIs. They were very responsive and fixed most of the issues we identified. If we built this table again now- I suspect you'd see a big improvement.

@rdmpage @adam42smith @bioone @tandfonline @WileyEcolEvol @JSTOR @CrossrefOrg @d_tkaczyk Weirdly- the issues stemmed from their tech stack's over-enthusiastic internal use of "DOI-like" identifiers throughout. Some of these ended up getting registered when they shouldn't. Others were exposed, but never registered & were widely scaped & interpreted as "broken DOIs."