Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downloaded results use internal sample identifiers, not pedigree identifiers #154

Open
mathob opened this issue Sep 5, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@mathob
Copy link

mathob commented Sep 5, 2022

Describe the bug
When a user downloads the results of a search in a spreadsheet format the sample identifers used are apparently internal CPG identifiers but should be same identifiers used in the pedigree

Link to page(s) where bug is occurring
After any variant search in CIRCA project click "Download", save in spreadsheet format

E.g. https://seqr.populationgenomics.org.au/api/search/9923b6381576183e21edaf034cca20ac/download?file_format=xls

In family C21SO329 the results spreadsheet has sample identifiers like CPG243881 which are unknown to the user

Scope of the bug
Occurs in CIRCA project, but not in NA12878 trio project

Screenshots

image

@mathob mathob added the bug Something isn't working label Sep 5, 2022
@illusional
Copy link

IMO this is an issue with seqr not exporting the participant ID within this report. Seqr only allows one external sample identifier, and we have to use the internal CPG ID as they must match the joint-call, and we can't guarantee external identifiers are unique across projects.

@cassimons
Copy link
Collaborator

But there is still no reason for seqr not to use the Display ID in this report is there? Should it not just use the same logic as is used in the genotype UI and use the expected display ID?

@illusional
Copy link

I think they're being extra granular with what sample because that's what's actually in the ES index. The DisplayID is the individual's ID, so I think if any change should be made, we should include that in addition.

@cassimons
Copy link
Collaborator

Yes... but the internal ID is not presented via the UI at all. The user is only ever expected to see the display ID, I am not sure why that should be different just because they are getting a csv version of the same results presented in the UI?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants