Hyperlink DOIs to preferred resolver #1881
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello :-)
The DOI foundation recommends this new resolver. Yes, a bit ironic that they would change the URL of their service, but it's now encrypted. Because the old links with the
dx
subdomain continue to work, there is no urgent need to do anything.However, I'd hereby like to suggest to follow the new recommendation and update all static DOI links.
Cheers!
PS: I think the below template doesn't really fit in this case, because no functionality at all is touched, and no text either.
Is any new functionality in tested? (This can be checked with
make clean diff-cover
or the CodeCov report that is automaticallygenerated following a successful CI build.)
Was a spellchecker run on the source code and documentation afterchanges were made?
Have any changes to the command-line interface been explicitly described?Only backwards-compatible additions are allowed without a major version
increment. Changing file formats also requires a major version number
increment.
Have any substantial changes been documented inCHANGELOG.md
? Seekeepachangelog for more details.
Do the changes respect streaming I/O? (Are they tested for streaming I/O?)