BCR data updates #683
Merged
BCR data updates #683
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
7 tasks
labkey-bpatel
approved these changes
Jan 29, 2025
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.
Rationale
pab_sequencetable tobcr_sequencepab_sequence.pab_idtobcr_study_seq_idpab_sequence_studytable, the dataspace team needs row level security. To achieve this behavior we map the incoming data to a new dataset namedBCR_Sequenceusing a similar workflow as the other existing dataset. When the application gets populated, rows from the data import are copied to the appropriate study folder using the value in theprotfield. This is why they dataset metadata needs to be modified so the new dataset can be initialized during folder import.