[ENG-10328] fixed non-consistent COI#11633
Open
ihorsokhanexoft wants to merge 2 commits intoCenterForOpenScience:feature/pbs-26-2from
Open
[ENG-10328] fixed non-consistent COI#11633ihorsokhanexoft wants to merge 2 commits intoCenterForOpenScience:feature/pbs-26-2from
ihorsokhanexoft wants to merge 2 commits intoCenterForOpenScience:feature/pbs-26-2from
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
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.
Ticket
https://openscience.atlassian.net/browse/ENG-10328
Purpose
Some users with older preprints encounter an issue when
has_coi = Truebutconflict_of_interest_statement=''It may happen because of some bug on the legacy UI or we had some issues with validation COI that allowed user to bypass validation in the past on BE that was fixed after Preprint Affiliation Project but the older preprints still contain invalid data that makes it impossible to pass the current validation during creation of a new version of a preprint
Changes
Added button on a preprint admin page to fix this case