Timeline for Standardizing Variant IDs best practise
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 31, 2023 at 14:46 | comment | added | user27815 | Thanks ill check that out. | |
| Oct 29, 2023 at 18:18 | comment | added | terdon♦ | Also, are you open to paid tools? The company I work for has an API that will, among other things, provide unique ids for arbitrary (human) variants. If you are open to non-free tools check out landing.varsome.com/varsome-api. | |
| Oct 29, 2023 at 17:08 | comment | added | terdon♦ | You need this to work on multiple species, right? And across different reference genome builds? Are you only interested 8n species with a sequenced genome or do you also need to handle variants defined with respect to a specific transcript or protein only, in the absence of a reference genome? | |
| Oct 29, 2023 at 16:30 | answer | added | BigMistake | timeline score: 1 | |
| Oct 29, 2023 at 16:23 | comment | added | BigMistake | I would not hash. Variant IDs should be static across builds, similarly to how rsIDs are handled between b37 and b38. I do not think hashing is worth it because there's not that much downside for a long ID | |
| Oct 4, 2023 at 12:45 | comment | added | user27815 | I have tried to clarify | |
| Oct 4, 2023 at 12:44 | history | edited | user27815 | CC BY-SA 4.0 |
try and clarify question
|
| Oct 4, 2023 at 11:37 | comment | added | CommunityBot | Please clarify your specific problem or provide additional details to highlight exactly what you need. As it's currently written, it's hard to tell exactly what you're asking. | |
| S Oct 4, 2023 at 8:28 | review | First questions | |||
| Oct 4, 2023 at 11:37 | |||||
| S Oct 4, 2023 at 8:28 | history | asked | user27815 | CC BY-SA 4.0 |