Remove author normalizations#233
Merged
bklaing2 merged 3 commits intoMay 13, 2026
Merged
Conversation
bklaing2
commented
May 11, 2026
| if a["affiliationIdentifier"].present? | ||
| affiliation_identifier = a["affiliationIdentifier"] | ||
| if a["schemeURI"].present? | ||
| schemeURI = a["schemeURI"].end_with?("/") ? a["schemeURI"] : a["schemeURI"] + "/" |
Member
Author
There was a problem hiding this comment.
In regards to datacite/product-backlog#792, I think this isn't required. Here schemeURI is appended with a "/" when necessary, but is only used to build affiliation_identifier. The returned schemeUri is the value from affiliation, set in scheme_uri (not schemeURI)
KellyStathis
approved these changes
May 12, 2026
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
3 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.
Purpose
closes: Add github issue that originated this PR
Approach
Open Questions and Pre-Merge TODOs
Learning
Types of changes
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Reviewer, please remember our guidelines: