Update definition of _audit_support.funding_organization_doi #573
Conversation
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
The content type was changed from 'Text' to 'Word' and a note on escaping special characters was added based on https://www.crossref.org/documentation/member-setup/constructing-your-dois/suffixes-containing-special-characters/.
jamesrhester
approved these changes
Dec 10, 2025
Contributor
jamesrhester
left a comment
jamesrhester
left a comment
There was a problem hiding this comment.
I note the unfortunate need to include the resolver in this particular DOI data name for historical reasons (definition already published) as discussed in #275 .
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Resolves issue #275.
The note was added based on the current version of https://www.crossref.org/documentation/member-setup/constructing-your-dois/suffixes-containing-special-characters/. The linked advice could be summarised as "Encode
#as%23and do NOT encode some other specific symbols, but in practice it seems that URL-encoding any symbol still results in the URI being resolved. As such, I left the note slightly less specific since symbols like%will also always need to be escaped (although they probably do not appear in DOIs as often as#).The content type was changed from
TexttoWorddo disallow space characters (and thus force them to be URL-encoded).