Repository navigation
Hyperlink DOIs against preferred resolver - #11470
Merged
dstansby merged 1 commit intoJun 21, 2018
Merged
Conversation
Contributor
Author
|
You're welcome, and thanks for merging :-) |
This was referenced Jan 13, 2019
timhoffm
pushed a commit
that referenced
this pull request
Jan 13, 2019
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR Summary
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
dxsubdomain 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.
PR Checklist
Has Pytest style unit testsCode is PEP 8 compliantNew features are documented, with examples if plot relatedAdded an entry to doc/users/next_whats_new/ if major new feature (follow instructions in README.rst there)Documented in doc/api/api_changes.rst if API changed in a backward-incompatible way