Fill priority column in table scxa_dimension_reduction (related to SCXA migration V19)
#72
Conversation
This file contains 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.
This relates to the new
priorityfield on the table scxa_dimension_reduction added in the migration V19, which is the current one in staging.@ke4 @upendrakumbham @pmb59 have continued previous discussions and agreed possible best way forward is leave all priorities as 0 (default) and only one as non-zero, which will be the dimension reduction first picked by the UI. If all values are zero, then current policy applies. See issue in atlas-web-single-cell.
Possibly we could make this values boolean (TRUE/FALSE) or leave numeric to allow flexibility for future implementations.
Data Production Team is responsible of calculating the priority values, and adding them to the DB - this PR.