Support tracking libraryType in MHC results and ETLs - #1858
Open
bbimber wants to merge 1 commit into
Open
Conversation
Collaborator
|
@bbimber PRIMe is currently running on LabKey 26.3. We're planning to upgrade to LabKey 26.7 in the first half of November (and do the PostgreSQL migration sometime late Q1'27). |
Collaborator
Author
OK, perfect. This PR is mostly aimed at tracking additional detail on the raw MHC data. That field will be ETL'd to PRIMe, but it isnt really needed, nor will it be visible to normal users. |
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
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.
@brentlogan: these changes are an extension to the MHC typing storage and ETLs. They mostly impact the PRIMe-seq side, but will ultimately need to be deployed to PRIMe.
Can you confirm what LK version PRIMe is running? I would like to deploy the PRIMe-seq parts of this first, stage data, and then add the PRIMe pieces. Because I think you update less frequently, this might just happen naturally.