Closed joneubank closed 2 years ago
Unexpected behavior observed with this query in qa:
query { sampleMatchedAnalysesForDonor(
req: {
donorId: "DO262418",
analysisType: "sequencing_experiment"
}
) {
normalSampleAnalysis{
analysisId
studyId
analysisType
analysisState
donors {
donorId
submitterDonorId
}
}
tumourSampleAnalysis{
studyId
analysisId
analysisType
analysisState
donors {
donorId
submitterDonorId
}
}
}
}
Query matched samples across studies and with different donorIds:
There is bad data here, but the query should filter the pairs to match the sampleId and donorIds. Also add optional studyId to filter pairs matched across studies.
Add sampleType to request and add constraint to check sampleTypes are equal for matching samples. https://github.com/icgc-argo/song-search/pull/75
some legacy analyses use library_strategy instead of experimental_strategy. Need to check the values match for both of these fields.
Released to prod, closing
Add a query that takes donorId as input and returns an array of matched tumour/normal pairs for that Donor.